> 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/privileged-identity-insights-help-to-quickly-identify-privileged-identities.md).

# Privileged Identity insights help to quickly identify privileged identities

BalkanID customers can now quickly identify privileged identities and entitlements at a glance, filter specifically for privileged identities and entitlements, and create access reviews to target privileged identities and entitlements specifically. Additionally, customers in Reviewer roles can easily identify access reviews for privileged identities and entitlements. It is now easier to focus specifically on privileged access so it does not get overlooked.

Privileged Identities insights designate entitlements and identities that are privileged. This insight highlights risky entitlements and identities worth additional attention as determined by an Administrator and reduces the chance they will be overlooked.

You can start using Privileged Identity insights today by contacting Customer Support to enable Insights for your tenant. To learn how to setup Privileged Identities and learn more, see the [Privileged Identities Setup](https://docs.balkan.id/insights-and-rules/entitlement-rules-and-labels/setup-privileged-identities.md).

<br>


---

# 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/privileged-identity-insights-help-to-quickly-identify-privileged-identities.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.
