> 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/terminated-insights-help-to-quickly-identify-and-remediate-entitlements-held-by-terminated-employees.md).

# Terminated insights help to quickly identify and remediate entitlements held by terminated employees

BalkanID customers can now quickly identify terminated employees and any entitlements still assigned to them. Customers can identify terminated employees at a glance, filter specifically for terminated employees, and create access reviews to confirm removal of their entitlements. Additionally, customers in Reviewer roles can now easily identify access reviews for terminated employees. Entitlements belonging to terminated employees will no longer linger in customer systems and can be quickly addressed.

Terminated insights are a convenient way to quickly identify terminated employees and any entitlements still assigned to them. Terminated insights also focus reviewer efforts by highlighting access reviews for terminated employees. Terminated insights are available once Administrators connect their employee system of record with BalkanID.

You can start using Terminated insights today by connecting your employee system of record with BalkanID and contacting Customer Support to enable Insights for your tenant. Once enabled, you will be able to filter for Terminated insights and they will be visible in the Insights column on [Entitlements](https://app.balkan.id/entitlements), [Access Reviews](https://app.balkan.id/access-reviews), and [My Tasks](https://app.balkan.id/my-tasks) pages.


---

# 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/terminated-insights-help-to-quickly-identify-and-remediate-entitlements-held-by-terminated-employees.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.
