> 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-access.md).

# Your access

See everything you have access to, and understand where each item came from.

This page answers a question people ask surprisingly often: *what do I actually have access to?*

Open it from **Access Management → Access Profile**. The page is headed **Access Profile**, with *View current entitlements and access rights* beneath it.

## What's on the page

At the top is a card with your **name**, **title**, **email**, and **supervisor** — useful context when you are looking at someone else's access rather than your own.

Below that is **Entitlements**: everything you hold, as an expandable tree.

## Reading the tree

<figure><img src="https://2965242200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uHWHRgcad6P03ehqgmX%2Fuploads%2Fgit-blob-01924a6588dff20d094edbd46d09c43a1b62085c%2Fselfservice-your-access-01-tree.png?alt=media" alt="The Access Profile page with an application expanded to show its account and roles, and the entitlement columns beside them"><figcaption></figcaption></figure>

Your access is grouped by **application**, not by type. Expand an application and you see what you hold inside it:

* **Account** — your identity in that system, with the user name you hold there
* **Roles** — the roles you have been granted in it

So a line reads top to bottom as *this application → this account → these roles*, which answers "what can I reach in that system?" in one place.

Each row shows:

| Column                        | What it tells you                                                                                      |
| ----------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Name**                      | The application, account, or role                                                                      |
| **Status**                    | Where it stands — for example **ACTIVE**, or **PENDING\_UPDATE** while a change is still being applied |
| **Description**               | What the item is for                                                                                   |
| **Entitlement Type**          | What kind of grant it is — for example *Provision Role*                                                |
| **Access Rights**             | Any specific rights attached to it                                                                     |
| **Start Date** / **End Date** | When it began, and when it expires if it is time-limited                                               |

A dash (**—**) simply means that column is empty for that row.

{% hint style="info" %}
A status of **PENDING\_UPDATE** means a change is in flight — a grant or removal has been approved and is on its way to the application. It normally clears on its own; if it sits there for days, mention it to your help desk.
{% endhint %}

## Requesting more from here

**Create Access Request**, at the top right of the Entitlements panel, starts a request without going back to the sidebar. It is the quickest route when you have just looked at what you hold and realised something is missing — see [Requesting access](/end-user-guide-for-selfservice/requests/request-access.md).

## Identity information

**Identity Information** shows the accounts you hold in managed systems — which system, and what your user name is there. See [Your accounts in other systems](/end-user-guide-for-selfservice/your-profile/your-identities.md) for what these are and why they are tracked.

## Where your access came from

Nothing here appears at random. Each item arrived one of three ways:

* **Automatically**, because of who you are — your department, job title, or location. This is called **birthright access**, and it is granted without anyone asking. It also goes away automatically when the underlying fact changes.
* **By request** — you asked for it, someone approved it, and it was granted. See [Requests](/end-user-guide-for-selfservice/requests.md).
* **By assignment** — an administrator or your manager gave it to you directly.

## Using this page well

* **Before requesting something, look here first.** People regularly request access they already hold.
* **Check it after you change job.** A move should add new access and remove the old; if the old is still listed weeks later, mention it.
* **Give up what you don't use.** Access you no longer need is a risk to you and to your organization. See [Giving up access](/end-user-guide-for-selfservice/requests/revoke-access.md).

{% hint style="info" %}
If you need access to something and don't have it, this page is where you confirm that — then go to [Requesting access](/end-user-guide-for-selfservice/requests/request-access.md) to ask for it.
{% endhint %}

## Related pages

* [My groups](/end-user-guide-for-selfservice/your-access/my-groups.md) — the groups you belong to
* [Access profiles](/end-user-guide-for-selfservice/your-access/access-profiles.md) — ready-made bundles of access


---

# 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-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.
