> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/entitlement-data-discovery/entity-discovery.md). # Entity Discovery ## Overview BalkanID allows you to quickly view entitlement data across multiple systems mapped to the employees or service accounts owners. You can view the information about the following: * [Applications](https://app.balkan.id/applications) - You can view a list of all applications that you have integrated with your BalkanID tenant. Refer to [Application page for entitlement discovery](/getting-started/entitlement-discovery/applications-entitlements-discovery.md) to understand its usage for entitlement discovery. * [Connections](https://app.balkan.id/connections) - You can view a list of all connections extracted from various applications. Refer to [Connection page for entitlement discovery](/getting-started/entitlement-discovery/connection-entitlement-discovery.md) to understand its usage for entitlement discovery. * [Identities](https://app.balkan.id/identities) - You can use this page to see a list of all application identities that have been extracted from various applications that was integrated into your BalkanID tenant. Refer to [Identities page for entitlement discovery](/getting-started/entitlement-discovery/identities-entitlements-discovery.md) to understand its usage for entitlement discovery. * [Resources](https://app.balkan.id/resources) - You can use this page to see a list of all application resources that have been extracted from various applications that was integrated into your BalkanID tenant. Refer to [Resources page for entitlement discovery](/getting-started/entitlement-discovery/resource-entitlement-discovery.md) to understand its usage for entitlement discovery. {% embed url="" %} ## Filters You can also use filters to easily view select data. This is a powerful tool to partition and isolate entitlement information to narrow down data based on specific attributes. Each page has its own set of attributes to filter data. Refer to [Working with Filters](/getting-started/entitlement-discovery/working-with-filters.md) to get a better understanding of how you can use filters to maximise your entitlement discovery capabilities. {% embed url="" %} ## Glossary for entity extraction 1. **Identity**: This represents a **user** or **service** **account** in your system. Identities are extracted directly from your application integrations. They could be individual users, customer profiles, or different types of accounts, each with specific access rights. 2. **Resource**: Resources are the **assets or services** that users can access. These are also extracted from your application integrations. Resources can include anything from documents, databases, or reports to specific features in your app. For instance, a resource could be a premium feature, a cloud storage space, or an API service that users have permission to use. 3. **Connection**: A **connection** represents the **access provider** for a user (identity) to a resource. These connections are derived from the entitlements granted through the application integrations. For example, a user gains access to admin resources as a virtue of being in an admin role. Here the "admin" role serves the purpose of a connection. 4. **Insight**: Unlike identities, resources, and connections—which are directly extracted from your application integrations—**insights** are generated based on our **analysis** of your data. Insights provide valuable, actionable information about how resources are being accessed. These insights are not directly pulled from your integrations but are created through analysis of the relationships and data captured by the other entities. **Entities description:** In our system, the **Entities** are used to represent identities, resources, connections, etc. The data extracted from your application integrations are organized into **entity types** such as **identity**, **resource**, **connection**, **insight**. Entities are flexible and can be extended in the future as new requirements and use cases emerge (for instance: even logs can be entities).
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.balkan.id/getting-started/entitlement-data-discovery/entity-discovery.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.