> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/approvals/review.md).

# Review and approve transactions

Work through the transactions waiting on you on the Approvals page: approve or reject several at once or one at a time, and see what you still need to send.

The Review page, headed **Approvals**, lists the transactions waiting on you so you can approve, reject or send them on. Owners, Super Admins, Managers, Department Heads, Cast and Crew and Card Holders open it from **Approvals > Review** or **Approvals** in the sidebar, and what you can do on it depends on your place in the production's approval flow, not your role.

{% hint style="info" %}
Some parts depend on what your company or production uses: the **Envelopes** view and daily approval reminders.
{% endhint %}

## Find the page

Where the page sits in the sidebar depends on your role:

* Owners, Super Admins and Managers: **Approvals > Review**.
* Department Heads, Cast and Crew and Card Holders: the **Approvals** link.

## What's on the page

The page has two tabs. The number after each name is how many transactions it lists right now.

* **Needs Approval** lists transactions you can approve or reject. Only people who are approvers on the production see it, and the page opens on it for them.
* **Needs Submission** is for everyone. It lists transactions waiting for you to send for approval. See [Submit transactions for approval](/approvals/review/submit-for-approval.md).

Each table has the same columns as the Transactions page. See [Find and edit transactions in the table](/transactions/transactions/find-and-edit.md).

{% hint style="info" %}
If your company reviews approvals by envelope, an **Envelopes** / **Transactions** toggle appears above the tabs when the production has envelopes holding transactions you can see, and the page opens on **Envelopes**. Select **Transactions** to see the tabs. See [Review an envelope](/approvals/review/review-envelopes.md).
{% endhint %}

## In this section

* [Submit transactions for approval](/approvals/review/submit-for-approval.md): the **Needs Submission** tab, for sending transactions to an approver.
* [Review an envelope](/approvals/review/review-envelopes.md): the **Envelopes** view, and reviewing every receipt in an envelope in one scroll.
* [Escalate for additional approval](/approvals/review/escalate.md): asking the production's escalated approvers for extra sign-off.
* [Send and answer urgent approval requests](/approvals/review/urgent-approvals.md): urgent requests by text and email, and answering them by text.

## Choose what to review

On **Needs Approval**, a toggle above the table picks the list:

* **Sent to you** shows transactions sent to you by name. The tab opens on this list.
* **You can approve** adds everything else you're allowed to approve, such as transactions waiting on someone at your level or below.

Each shows its count, and its question mark explains what it includes. Switching clears any rows you've ticked.

Filters at the top of the tab narrow the list: **Envelope** (**All Envelopes**), **Created By** and **Last Action By** (both **All Users**). Each one offers only the envelopes or people on the current list.

{% hint style="info" %}
An **AI flagged only** checkbox appears next to the filters while any transaction you can see on the production is flagged, even one that isn't on this list. Tick it to see only flagged transactions. See [Write AI approval rules](/approvals/rules.md).

A **Review envelope** button below the filters opens the envelope chosen in **Envelope** in one scroll. See [Review an envelope](/approvals/review/review-envelopes.md).
{% endhint %}

## Approve or reject several at once

1. On **Needs Approval**, tick the box on each row you want. The box in the header ticks every row in the filtered list.
2. In the bar that appears, choose an action. The list offers **Approve & Send** when there's a level above yours, or **Approve** when yours is the last level, and **Reject**.
3. For **Approve & Send**, choose who reviews them next in **Submit to**. It lists the approvers at the next level of the flow.
4. If you want, select **Add a note...** and type a note. It goes with every transaction you ticked.
5. Select **Submit**.

The bar counts your ticks, for example **3 selected**. Approved transactions leave the list. A rejected one leaves **Sent to you** but stays under **You can approve** if you're at a higher level than the person it went back to.

* Rejected transactions go back to the person who uploaded them. You can return one to an earlier approver by rejecting it one at a time.
* You can't send an urgent request from this bar. Review the transaction one at a time instead.
* If you tick different kinds of transactions, such as receipts and invoices, **Submit to** lists only next-level approvers they share. If they share none, the list offers **Approve** instead, and any that still need a higher level wait under **Needs Submission** for you to send on. To send each kind to its own approver, tick one kind at a time.
* If some transactions can't be changed, for example because someone else already approved them, RollCredits skips them. A warning starting **Skipped** says how many and why, and the list refreshes.
* A highest-level approver can't reject a transaction they created, here or one at a time. The message includes **Transactions created by highest level approvers cannot be rejected**.

If your production has escalated approvers, the bar can also show an escalate button, such as **Escalate 3…**. See [Escalate for additional approval](/approvals/review/escalate.md).

## Review one at a time

1. On **Needs Approval**, select the eye button at the end of a row. On a computer, the document opens on the left, the side panel on the right and an action bar across the top.
2. Check the document and the details. To move through the list, use the arrows in the action bar. The count between them shows where you are, such as **2 of 12**.
3. Choose **Approve & Send** or **Approve**, or **Reject**.
4. For **Approve & Send**, choose the next approver in **Submit to**. To have them texted and emailed, tick **Send text/email for urgent approval?**. See [Send and answer urgent approval requests](/approvals/review/urgent-approvals.md).
5. If you want, select **Add a note...** and type a note.
6. Select **Submit**. The next transaction in the list opens. If it was the last one, the one before it opens, and when the list is empty the panel closes.
7. To stop, select the X at the top of the side panel.

A rejected transaction goes back to the person who uploaded it. Changes you make to the details in the side panel save on their own. See [Review and edit a transaction](/transactions/transactions/edit-a-transaction.md).

{% hint style="info" %}
A rejection can go back to an earlier approver instead. When you choose **Reject** and someone below you has already approved the transaction, a **Return to** list appears. Choose the uploader, shown with **(uploader)** after their name, or an earlier approver, shown with their level, such as **(level 1)**. An approver you return it to must approve it again.
{% endhint %}

If you're in the transaction's flow and the production has escalated approvers, the action bar also has **Escalate**. See [Escalate for additional approval](/approvals/review/escalate.md).

## Use the side panel's Approvals tab

The side panel's **Approvals** tab works here just as on the Transactions page: **Send to**, **Notes**, the approve and reject buttons (including **Reject and return to** a name), **Undo Send**, **Undo Approve** and **Approval History**. It also says **You are not able to take action on approvals for this transaction.** when someone else has to act, or **This transaction does not require any more action to be taken.** when nothing more is needed. The steps are in [Send and approve transactions](/transactions/transactions/approve-transactions.md).

Acting from this tab doesn't move you to the next transaction. Once the transaction leaves the list, the panel shows **No transaction to display.** Select the X to close it, then open the next one.

**Flagged by AI review (N)** at the top of the tab lists the rules the transaction failed. See [Write AI approval rules](/approvals/rules.md).

## Get a daily reminder

{% hint style="info" %}
Reminder emails go out only if your production uses daily approval reminders.
{% endhint %}

Once a day, RollCredits emails each approver who has transactions waiting on them to approve, reject or send on. The email says how many items are waiting on that production and links to this page.

You get it only when at least one of those transactions has gone more than a day since its last approval step, and at least one had an approval step in the last four days. Wrapped productions don't send reminders.

## On a phone

The page works on a phone, with these differences:

* The filters stack above the table.
* The eye button opens the transaction full screen, with its document inside the side panel. The X to close it is at the top.
* The action bar sits at the bottom of the screen. The arrows and count are at the top of the bar, with the action list, **Submit** and the other controls below them.
* **Review envelope** appears only on wider screens, not on most phones.


---

# 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://knowledge.rollcredits.io/approvals/review.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.