> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/end-user-guide-for-selfservice/your-profile/your-identities.md).

# Your accounts in other systems

Understand the accounts you hold in managed systems and how they relate to you.

You are one person, but you hold several **accounts** — one in the network directory, one in email, perhaps others in business applications. In OpenIAM each of these is called an **identity**, and each belongs to one **managed system** (a connected application or directory).

Your profile can show these identities so you can see, in one place, what exists in your name.

## Why they look different

Your user name is not always the same everywhere:

* the network directory might know you as `j.smith`
* email might use `john.smith@company.com`
* an older business application might use an employee number like `E10432`

They are all you. OpenIAM keeps them linked so that when something changes — you get married and change surname, you move department, you leave — every linked account can be updated or closed together, instead of one being forgotten.

That last point is the whole reason identities are tracked: forgotten accounts are how people keep access they should have lost.

## What you can do here

For most people this page is **read-only** — useful for answering "what account do I have in that system?" when a colleague or the help desk asks.

If your organization has given you the ability to manage identities, you may also be able to add or remove one. Messages you might see:

| Message                                                  | What it means                                             |
| -------------------------------------------------------- | --------------------------------------------------------- |
| *"User login updated successfully"*                      | The change was saved.                                     |
| *"Login already exists"*                                 | That user name is already in use — choose another.        |
| *"User already has an identity for this managed system"* | You cannot hold two accounts in the same system this way. |
| *"Login was deleted successfully"*                       | The identity was removed.                                 |
| *"Unable to save login"* / *"Unable to delete login"*    | The change did not go through — contact your help desk.   |

{% hint style="warning" %}
Removing an identity does not just tidy a list — it can remove your access to that system. Don't delete one to "clean up" unless you are certain it is no longer needed.
{% endhint %}

## If an account is missing

If you expect an account in a system and it is not listed, the usual reasons are:

* **It was never created** — you may need to request access. See [Requesting access](/end-user-guide-for-selfservice/requests.md).
* **It exists but was never linked** to your OpenIAM record. This happens with accounts created manually before OpenIAM was introduced. Your help desk can connect them.

Either way, this is a request or a support question rather than something you can resolve on this 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.openiam.com/end-user-guide-for-selfservice/your-profile/your-identities.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.