> 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/agents/mapping-identities-and-credentials-to-agents.md).

# Mapping Identities and Credentials to Agents

### Overview

Mapping identities and credentials to an agent records which identities and credentials the agent **has access to**.

This is an **access association**, not an ownership mapping.

| Mapping in BalkanID                                        | What it means                                                                                    |
| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Identity → Employee** (Identities page, Map to employee) | Ownership / accountability — which person the identity belongs to or is owned by                 |
| **Identity or Credential → Agent** (this page)             | Access — which identities and credentials the agent can use or is associated with for governance |

Use agent mapping when you need to answer: *Which identities and credentials does this agent have access to?*

{% hint style="info" %}
Mapping identities to agents is available when Agents (Early Access) is enabled for your tenant. The Identity Mapping drawer then includes **Map to employee** and **Map to agent**.
{% endhint %}

### Map identities to an agent

1. Login to the BalkanID application and switch to the tenant you want to update.
2. Head to **Identities**.
3. Select one or more identities the agent has access to.
4. Click **Map identities**.<br>

   <figure><img src="/files/GNrDiB4JdZiKLX4fTOKA" alt=""><figcaption></figcaption></figure>
5. In the **Identity Mapping** drawer, select **Map to agent** (not **Map to employee**).
6. Choose the target **Agent**.
7. Confirm the mapping.<br>

   <figure><img src="/files/jUFnCvMBzN0n4r8rgexN" alt=""><figcaption></figcaption></figure>

#### Result

BalkanID processes the mapping asynchronously. When complete:

* The identities appear on the agent’s **Identities** tab
* The agent appears under **Accessible by agents** on those identity detail pages
* Identity counts on the Agents page update accordingly

<figure><img src="/files/TKojijfA2va1jNMwixPL" alt=""><figcaption></figcaption></figure>

### Map credentials to an agent

1. Login to the BalkanID application and switch to the tenant you want to update.
2. Head to **Credentials**.
3. Select one or more credentials the agent has access to.
4. Click **Map credentials**.\ <br>

   <figure><img src="/files/S40RxltqHZ8dmHkh3ssK" alt=""><figcaption></figcaption></figure>
5. Choose the target **Agent**.
6. Confirm the mapping.<br>

   <figure><img src="/files/JVBqIQBn8aVIPj8xJm9c" alt=""><figcaption></figcaption></figure>

#### Result

BalkanID processes the mapping asynchronously. When complete:

* The credentials appear on the agent’s **Credentials** tab
* The agent appears under **Accessible by agents** on those credential detail pages

<figure><img src="/files/Y4sLZxkPbTxMxvgAqyJ6" alt=""><figcaption></figcaption></figure>

### When to map

Use mapping when:

* An agent uses a human or non-human identity to act in an application
* An agent uses or is bound to a credential (for example, an API key or vault secret)
* You need a clear access inventory for blast-radius analysis

For extracted agents, some access associations may already be discovered from the source integration. Manual mapping fills gaps and covers agents that were registered or uploaded in BalkanID.

To remove an access association, see [Unmapping Identities and Credentials from Agents](/agents/unmapping-identities-and-credentials-from-agents.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.balkan.id/agents/mapping-identities-and-credentials-to-agents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
