> 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/updates/release-notes/quickly-find-what-youre-looking-for-with-the-new-people-applications-and-identities-pages.md).

# Quickly find what you’re looking for with the new People, Applications, and Identities pages

Exploring data associated with People, Applications, and Identities is now easier than ever before. The newly added People, Applications, and Identities pages provide a streamlined interface for Risk Managers and Administrators to quickly search for and access data within BalkanID. Additionally, with the new Detail Pages, each Person, Application, and Identity has a dedicated page that offers an overview of their respective entitlements. This also includes any related people, applications, and identities that may be associated with them.

BalkanID discovery pages enable our customers to better understand their current entitlement posture down to the granularity of individual entitlements.

You can start exploring the new pages now: [People](https://app.balkan.id/people), [Applications](https://app.balkan.id/applications), [Identities](https://app.balkan.id/identities).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/updates/release-notes/quickly-find-what-youre-looking-for-with-the-new-people-applications-and-identities-pages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
