> 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/insights-and-rules/entitlement-rules-and-labels/setup-privileged-identities.md).
# Setup privileged identities
Privileged Identities is an insight designating entitlements and identities that are privileged. This insight highlights risky entitlements and identities worth additional attention and is configured by an Administrator. Identities are considered to be privileged based on the connections/permissions that they are entitled to.
Privileged Identities are configured for each application integration individually from the [Integrations page](https://app.balkan.id/configure/integrations/apps).
Follow the following steps to setup privileged identities:
1\. Select an application integration and select the **Setup Privileged Identities** action from the Actions menu.
Some application integrations may not have the Setup Privileged Identities action available, which will be indicated by the action being disabled.
This may happen when there is no data available for the integration. Once the application integration has Status of *Connected* and the message of *Data available*, the Setup Privileged Identities action will become available.
2\. You will see the below tab on opening. The *Setup Privileged Identities* page has six sections.
1. The **Title section** shows the type of the application integration for which privileged identities are being setup.
2. The **Selected Filters dropdown** is where Administrator selects Saved Filters to use for designated Privileged Identities.
If there are no Saved Filters available, the Selected Filters dropdown will indicate so:
If Saved Filters are available, they can be selected from the dropdown:
.png)
Once selected, they’ll appear in the selection window and the Update Criteria button will become available indicating that there are changes that can be saved:
Administrators can select multiple filters as part of the Privileged Identities criteria.
To see a list of all previously saved Privileged Filters, go to Settings > Saved Filters.
3. The **Add Filter** button enables the Administrator to create a new Saved Filter without leaving the Setup Privileged Identities page.Clicking the Add Filter button opens the Filter menu and populates the Privileged Identities Preview with currently filtered identity results:
Here, the Administrator can create a new Saved Filter and then include it in the Selected Filters dropdown to designate desired Privileged Identities.
Privileged Identities are normally identities with administrative roles (connections) or administrative permissions . For example, in some companies, for AWS, the identities with system administrator roles (connection) can be considered privileged . Setting up privileged is completely company specific.\
\
**Note:** The filter of type "Privileged" has some restrictions. A filter for Privileged can have only "Connections" or "Permissions" in one filter. You can apply multiple filters for an application to set the Privileged Identities (the filters will follow an **OR** condition). We recommend the following convention while naming your filters for setting up Privileged identities - "Privileged <*app-name*> \ \".
4. The **Update Criteria button** saves the Privileged Identities configuration for the application integration. Otherwise, exiting the Setup Privileged Identities page results in abandoning any changes.
5. The **Privileged Identities Preview** is a live preview showing the identities that will be designated as privileged based on the Selected Filters.
6. The **Exit** button exits the Setup Privileged Identities page without updating privileged criteria.
3\. The privileged identities saved filters also show up on the saved filters page as type *Privileged*. In addition to following the steps above to setup privileged identities for each application, you can always modify the privileged settings by editing the respective saved privileged filter for the application on the Privileged page.
---
# 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/insights-and-rules/entitlement-rules-and-labels/setup-privileged-identities.md?ask=&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.
