> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/guides/requests.md).

# Requests and approvals

How to find, approve, reject, and track Requests on Ledger Enterprise, and how to chase one that is not progressing.

**Role: Operators and Administrators.**

**Requests** lists every Request in the Workspace that you have visibility on, at any status. That includes the ones waiting on you, and the ones you initiated yourself.

For the underlying model, read [**How governance works**](/help-center-v2/concepts/how-governance-works.md).

## Finding what needs you

The list shows every Request you have visibility on. Each row carries the type, the Account, the amount where relevant, the approval progress, and the status. Requests you can act on are marked as needing your review.

Filter by Request type, status and Account, and sort the list. Filters are held in the page address, so a filtered view can be shared or kept for audit.

## Approving

An approval is a signature made with your own key. The platform cannot produce one for you.

**In the interface**, open the Request and read it. Then start the approval. Your Personal Security Device (PSD) displays the operation, and you confirm it on the device. The device reads the operation from the secure hardware, not from the browser.

**Over the API**, an API user signs the same approval challenge with its own key. Which path applies to you depends on how the Administrators created your user.

Approval is possible only while the Request is Pending, and only at a step you belong to. If you belong to a later step, you cannot act until the earlier steps complete.

The Request's **History** records each approval under **Approved by**.

## Rejecting

One rejection ends the Request. It cannot be revived, and the operation has to be created again.

There is no state between approve and reject. A Request cannot be returned to its Creator for changes.

| Who rejects          | What it takes                   |
| -------------------- | ------------------------------- |
| A user with a device | No device confirmation          |
| An API user          | A signature, as for an approval |

## Tracking a Request

A Request shows its approvals granted against those required, and its full **History**. Anyone involved can copy a link to it.

<table><thead><tr><th width="288.78515625">What you see</th><th>What it means</th></tr></thead><tbody><tr><td>Pending, no approvals</td><td>Waiting on the first step</td></tr><tr><td>Pending, part approved</td><td>A step is still short of its quorum</td></tr><tr><td>Executing</td><td>Fully approved, being carried out</td></tr><tr><td>Executed</td><td>Complete</td></tr><tr><td>Rejected, Expired, Failed, Stuck</td><td>See <a href="/help-center-v2/reference/statuses-and-errors.md">Statuses and errors</a></td></tr></tbody></table>

### Expiry

A Request expires 7 days after it is created. The Request shows the time remaining.

An expired Request does nothing. The operation has to be created again.

### If a Request is not moving

* Check which step is current, and how many approvals it still needs.
* Check the note. It is the only context an Approver has on the Request.
* Share the Request link with the Approvers you need.

Each step needs its own Approvers. A multi-step Request takes as long as its slowest step.

> **Note:** Approver names are not visible to everybody. An Administrator sees every name. An Operator sees their own name, and **Anonymized** in place of the others.

## Related

* [**How governance works**](/help-center-v2/concepts/how-governance-works.md)
* [**Statuses and errors**](/help-center-v2/reference/statuses-and-errors.md)
* [**Sending assets**](/help-center-v2/guides/transactions/sending-assets.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://help.enterprise.ledger.com/help-center-v2/guides/requests.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.