> 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/requests/request-history.md).

# Request history

Track what you have asked for, where each request has reached, and why it was decided.

**Request History** lists the requests you have raised, and the requests raised for you by someone else. It is where you go to answer "what happened to that?"

Open it from **Requests → Request History**.

## What the list shows

| Column                  | What it tells you                                               |
| ----------------------- | --------------------------------------------------------------- |
| **Request ID**          | The reference number. Quote it whenever you ask about a request |
| **Requestor Name**      | Who raised it — you, or someone acting for you                  |
| **Request created for** | Who the access is for                                           |
| **Short description**   | What was asked for                                              |
| **Request Create Date** | When it was raised                                              |
| **Status**              | Where it has reached                                            |

Open any request to see its full detail, including the approval trail.

## Reading the status

Statuses vary a little between organizations, but they mean one of four things:

| Status meaning           | What it tells you                                                         |
| ------------------------ | ------------------------------------------------------------------------- |
| **Waiting**              | Sitting with an approver. Nothing for you to do                           |
| **Approved / completed** | Agreed, and the access has been granted                                   |
| **Rejected**             | Someone declined it. The reason is recorded — open the request to read it |
| **Cancelled**            | Withdrawn before a decision                                               |

## The approval trail

Open a request and you can see who has looked at it, what they decided, when, and any comment they left. This is the most useful part of the page.

It answers the two questions people actually have:

* **"Who is it waiting on?"** — so you know whom to nudge, and whether nudging is even reasonable yet.
* **"Why was it rejected?"** — so your next request addresses the objection instead of repeating it.

In the new SelfService, the request opens on a single page. The summary at the top tells you where it stands — for example *"Waiting on Alex Kim · step 2 of 3"* — and the **Approval path** below it shows every step, decision, and comment in one timeline. You can add a comment or an attachment to answer an approver's question. If you no longer need the access while the request is still in progress, click **Cancel request** in the header and confirm. The approvers are told, and nothing is granted.

## If a request seems stuck

{% stepper %}
{% step %}
**Check who it is waiting on.**

Open the request and look at the trail. If it hasn't reached your approver yet, an earlier step is still open.
{% endstep %}

{% step %}
**Give it reasonable time.**

Approvers have other jobs. A day or two is normal; approvals often also have automatic reminders configured.
{% endstep %}

{% step %}
**Ask the person directly.**

A short message referencing the request number is usually all it takes.
{% endstep %}

{% step %}
**If the approver is away**, contact your manager or help desk. Approvals can be reassigned or delegated — see [Approvals and tasks](/end-user-guide-for-selfservice/approvals.md).
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Approved but the access still isn't working? Give it a short while — the grant has to reach the application itself — then check [Your access](/end-user-guide-for-selfservice/your-access.md). If it is listed there but the application still refuses you, that is one for the help desk.
{% endhint %}

## Request statistics

Some portals also show **Request Statistics** — volumes, how long approvals are taking, and where things queue up. It is aimed at people who manage the process rather than at individual requesters, but it is a quick way to see whether a delay is just you or a general backlog.


---

# 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/requests/request-history.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.