> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-console/approvals-and-policies/managing-approvals-in-the-approvals-page.md).

# Managing Approvals in the Approvals Page

The **Approvals page** is where approvers and requesters can monitor and act on approval requests. It provides full visibility into pending reviews, completed actions, and the history of who approved what and when.

***

### Accessing the Approvals Page

* Navigate to **Approvals < Requests** in the console.
* The page has two main views:
  * **To Review:** Requests waiting for your decision.
  * **Sent:** Requests you initiated that are currently in progress or completed.

***

### Reviewing Requests

#### 1. Filtering and Searching

* Use filters to narrow down requests by:
  * **Status** (Pending, Approved, Rejected, Terminated).
  * **Service** (e.g., Product configuration).
  * **Date range** (when the request was created).
* Use the search bar to find requests by entity or policy name.

#### 2. Viewing Request Details

Click a request row to open the details page:

* **Summary:** What change is being requested (e.g., *Product version Draft > Active*).
* **Approvers:** List of designated approvers, with indicators showing who has approved, rejected, or is still pending.
* **Requester:** The person who initiated the change.
* **Activity log:** Timestamped record of all actions taken (request created, approvals, rejections, termination).
* **Change details:** Side-by-side view of old and new values.

***

### Approving or Rejecting

#### Approving

* Click **Approve**, add a short note, and confirm.
* Once the minimum required approvals are collected, the request status changes to **Approved** and the action is executed.

#### Rejecting

* Click **Reject**, provide a reason, and confirm.
* If any approver rejects, the request status changes to **Rejected**, and the action is blocked.

**Note:** If you are the requester, you cannot approve your own request.

***

### Understanding Request Statuses

* **Pending:** Waiting for approvals.
* **Approved:** Enough approvals collected; action has been carried out.
* **Rejected:** One or more approvers rejected; action is blocked.
* **Terminated:** Request ended manually or automatically (e.g., if the related policy was retired or action canceled).

***

### Tracking Approvers

* Each approver’s decision is shown in the request details.
* Approvers who have acted display as **Approved** or **Rejected** with a timestamp.
* Approvers who haven’t acted yet remain in **Pending**.
* If the requester is also listed as an approver, they are marked as **Requester** and cannot approve.

***

The Approvals page gives you full control and transparency into every approval request, ensuring sensitive actions only proceed once they have been properly reviewed.


---

# 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.xyb.co/xyb-console/approvals-and-policies/managing-approvals-in-the-approvals-page.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.