> 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/escalate.md).

# Escalate for additional approval

Ask your production's escalated approvers for extra sign-off on transactions, track their answers, and re-escalate after a rejection.

Escalating asks one or more of your production's escalated approvers to sign off on a transaction on top of its normal approval chain. You can escalate from the Review page (**Approvals > Review** in the sidebar, or **Approvals** if that's your only approvals link) or from a transaction's side panel, if you're an approver in the approval flow for that type of transaction.

{% hint style="info" %}
If your company uses escalated approvers, an Owner or Super Admin picks the escalated approvers on the **Escalated Approvers** tab of [Approvals > Configure](/approvals/configure.md). The **Escalate** buttons appear only once your production has at least one.
{% endhint %}

## Escalate one transaction

1. Start in one of these places:
   * On the **Needs Approval** tab, select the eye button at the end of a row, then select **Escalate** next to **Submit** in the action bar.
   * [Open the transaction](/transactions/transactions/edit-a-transaction.md) on **Transactions**, or with the eye button on the Review page, and select **Escalate** on the side panel's **Approvals** tab. It's there even when the transaction isn't waiting on you.
2. In **Escalate for Additional Approval**, select each escalated approver you want to ask. A lone escalated approver is already selected.
3. If you want, type a message in **Notes (optional)**.
4. Select **Escalate to N**, where N is the number of people you picked.

## Escalate several transactions at once

1. On the **Needs Approval** tab, tick the transactions. If you see the **Envelopes** / **Transactions** toggle, select **Transactions** first.
2. In the bar above the table, select **Escalate N…**.
3. In **Escalate N transactions for additional approval**, pick approvers, add a note if you want, and select **Escalate to N**.

The bar leaves out transactions whose chain you aren't in and ones an escalated approver is still reviewing or has approved, and says how many, as in **· 2 can't be escalated**. If none can be escalated, the button doesn't appear.

## Escalate from an envelope

{% hint style="info" %}
You can also escalate while you [review an envelope](/approvals/review/review-envelopes.md), on a screen at least 768px wide.
{% endhint %}

* Each receipt you haven't approved yet has an escalate button. With several escalated approvers, **Escalate** opens the window. With only one, it reads **Escalate to** and their name, and sends the request right away, without a note. While it waits on them, it shows **Escalated to** and their name, greyed out.
* **Escalate Entire Envelope** opens the window for every undecided receipt waiting on you, except ones an escalated approver is reviewing or has approved. It's greyed out when none are left.

## What escalated approvers receive

* **One transaction:** an email naming you, the production, vendor, amount, date and your note, with a link that opens the transaction.
* **Several at once:** one summary email with the number of transactions and a link to the Review page. If they're all in one envelope, the link opens that envelope's review. This email doesn't include your note.

You get a copy of each email. Your note is also saved in the transaction's **Approval History**.

## Track an escalation

* **Side panel:** the **Approvals** tab has an **Escalated Approvals** panel, with a row for each escalated approver marked **Approved**, **Rejected** or **Pending**.
* **Next Approval Step:** **Needs escalated approval** means the chain is done and only escalated approvers are left.
* **Envelope review:** each escalated receipt shows a shield icon with **Escalated to**, the name, and **pending**, **approved** or **rejected**. Point at it to see who escalated it and when.

{% hint style="warning" %}
**Undo Send** doesn't take back an escalation: the escalation stays, and the transaction comes back to you to send again.
{% endhint %}

## Approve or reject as an escalated approver

1. Select the link in the email, or open the **Needs Approval** tab on the Review page. Transactions escalated to you are under **Sent to you**.
2. Approve or reject them as usual. See [Review and approve transactions](/approvals/review.md).

You see **Approve**, not **Approve & Send**: your approval doesn't send the transaction on.

{% hint style="info" %}
On a phone, a summary email that opens an envelope's review shows **Envelope review needs a screen at least 768px wide.** Select **Back to Approvals** and use **Needs Approval** instead.
{% endhint %}

The chain keeps moving while escalated approvers review. A transaction is fully approved only when the chain's highest level and every escalated approver who was asked have approved it.

## Re-escalate after a rejection

When an escalated approver rejects a transaction, its **Next Approval Step** shows **Rejected, needs re-escalation**, and it can't be fully approved. Sending it again or approving it doesn't clear the rejection. An approver in the chain has to escalate it again to the person who rejected it.

1. Find the transaction. If your company reviews approvals by envelope, **Re-escalate N** on an envelope's row in the Envelopes view opens the **Needs Submission** tab, filtered to that envelope.
2. Open the transaction and, on its **Approvals** tab, select **Escalate**.
3. Select the escalated approver who rejected it, then select **Escalate to N**.

In envelope review, a receipt held up this way shows **Re-escalate**, or **Re-escalate to** and the name, instead of an approve button. If it shows **Re-escalate in full view**, you can't re-escalate it yourself. Ask an approver in its chain to do it.

{% hint style="warning" %}
You can escalate only to people on the **Escalated Approvers** tab. If the person who rejected it was taken off, ask an Owner or Super Admin to add them back.
{% endhint %}


---

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