> 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-application-mappings-idp-discovered-apps-to-connected-applications-early-access.md).

# Introducing Application Mappings: IdP-Discovered Apps to Connected Applications (Early Access)

**Application mappings** link each application BalkanID discovers from your identity provider (IdP) to the matching connected application in BalkanID, so administrators can see which IdP apps are governed and which still need a connection. Teams no longer need to compare their IdP's app list with their connected applications by hand. Application mappings is available as an Early Access capability; contact BalkanID Support to have it turned on for your tenant.

### [**Application mappings**](https://docs.balkan.id/getting-started/entitlement-data-discovery/application-mappings-early-access.md)

Open **Mappings** under **Applications** in the **Entities** section of the navigation menu to see every IdP app for your primary IdP and the connected application it is mapped to.

**What’s new:**

* **Coverage at a glance:** Each IdP app shows as **Governed**, **Gap**, **Unmapped** or **Orphaned**, with the source **Inferred** when BalkanID mapped it automatically, or **Manual** when an administrator did.
* **Automatic mapping:** When an IdP app and a connected application share the same tenant identifiers after a sync, BalkanID maps them for you.
* **Map and unmap by hand:** Use **Map to application** or **Add mapping** to create a mapping, and **Unmap**, **Restore auto-mapping**, **Remap** or **Remove** to change one. Manual mappings are kept across syncs.
* **Primary IdP:** When more than one IdP is connected, choose a primary IdP so the same application is not counted twice.
* **Works with your filters:** The coverage chips, search, the filter menu and saved filters all work on the table.
* **Coverage on related pages:** A connected application's **Overview** tab lists the IdP apps mapped to it, and the **Resources** page shows an **App mapping** column for IdP application resources.

### [**Application Coverage on the Dashboard**](https://docs.balkan.id/getting-started/dashboard.md#application-coverage)

Administrators can see application coverage for the primary IdP and open the mappings straight from the Dashboard.

**What’s new:**

* **Dashboard card:** Administrators see an Application Coverage card on the Dashboard with the number of **Discovered**, **Connected**, **Governed** and **Gap** applications for the primary IdP, a link to change the primary IdP, and a link to open Application mappings.


---

# 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-application-mappings-idp-discovered-apps-to-connected-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.
