> 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/introducing-the-user-health-matrix-identity-status-across-your-applications-early-access.md).

# Introducing the User Health Matrix: Identity Status Across Your Applications (Early Access)

The **User Health Matrix** gives administrators one view of every user against every connected application, with the status of the identities each user has in each application. Teams no longer need to export identities from each application and compare them in a spreadsheet to find users who have active, inactive or suspended identities. The User Health Matrix is available as an Early Access capability; contact BalkanID Support to have it turned on for your tenant.

### [**User Health Matrix**](https://docs.balkan.id/getting-started/entitlement-data-discovery/user-health-matrix-early-access.md)

The matrix lists your users as rows and your connected applications as columns, ordered by the number of identities mapped to users.

**What’s new:**

* **Status at a glance:** In the Comfortable density, each cell shows the most serious status among the user's identities in that application (**Suspended**, **Inactive** or **Active**), with the counts when there is more than one identity. Hover over a cell for the breakdown, or click it to open the user's identities in that application.
* **Find users by identity status:** **Any active**, **Any inactive** and **Any suspended** show only users who have at least one identity with that status in any application.
* **Totals per user:** The **All apps** column shows how many applications each user has identities in, and how many of those identities are suspended or inactive.
* **Two densities:** Switch between **Comfortable** and **Compact** to fit more users and applications on the screen.
* **User details and offboarding:** Click a user's name to see their details, or select users and choose **Actions** > **Offboard User** when offboarding is enabled for your tenant.
* **Works with your filters:** Search, the filter menu and saved filters from the **Users** page work in the matrix too.

### [**User Health Matrix on the Dashboard**](https://docs.balkan.id/getting-started/dashboard.md#user-health-matrix)

Administrators can see the size of the matrix and open it straight from the Dashboard.

**What’s new:**

* **Dashboard card:** Administrators see a User Health Matrix card on the Dashboard with the number of identities mapped to users and the number of applications they span, and a link to open the matrix.


---

# 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/introducing-the-user-health-matrix-identity-status-across-your-applications-early-access.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.
