> 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/submit-for-approval.md).
# Submit transactions for approval
Send your transactions to an approver from the Needs Submission list on the Approvals page, several at once or one at a time.
Use the **Needs Submission** list on the Approvals page to send transactions to the next approver. Select **Approvals** in the sidebar, or **Approvals > Review** if Approvals is a section in your sidebar. Owners, Super Admins, Managers, Department Heads, Cast and Crew and Card Holders can use it.
{% hint style="info" %}
If you're not an approver, the page shows only this list, with no tabs. Approvers select the **Needs Submission** tab. If your company reviews approvals by envelope and the page opens on **Envelopes**, select **Transactions**.
{% endhint %}
## What's on the list
**Needs Submission** lists the transactions waiting for you to send, oldest first:
* Ones you added and haven't sent, or took back with **Undo Send**.
* Ones rejected and returned to you.
* If you're an approver, ones you approved without sending on. Ones you add count as approved at your level, so they land here too, unless you're a highest-level approver.
* Ones in an envelope you created that are waiting for someone to send. You can send them for that person.
Submitted transactions leave the list, and you can't edit them until they come back to you.
If an escalated approver rejected a transaction, sending it again doesn't clear that rejection. See [Escalate for additional approval](/approvals/review/escalate.md).
## Filter the list
The filters sit above the table, stacked on a phone. Each offers only what's on the current list.
* **Envelope** (**All Envelopes**): one envelope's transactions.
* **Created By** (**All Users**): transactions one person added.
* **Last Action By** (**All Users**).
{% hint style="info" %}
An **AI flagged only** checkbox appears while any transaction you can see on the production is flagged. Tick it to see only flagged ones. See [Write AI approval rules](/approvals/rules.md).
{% endhint %}
## Submit several at once
1. 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 above the table, choose the approver in **Submit to**. It starts on the first one. If it shows **--**, choose someone before you submit.
3. If you want, select **Add a note...** and type a note. It goes with every transaction you ticked.
4. Select **Submit**.
The bar counts your ticks, for example **3 selected**.
* You can't send an urgent request from this bar. Submit that transaction one at a time.
* If you tick different kinds of transactions, such as receipts and invoices, **Submit to** lists only approvers at the next level for all of them. If it's empty, tick one kind at a time.
* If some can't be sent, for example because someone else sent them first, the rest still go. A warning starting **Skipped** says why, and the list refreshes.
## Submit one at a time
1. Select the eye button at the end of a row. On a phone, it opens full screen with the document below the details and an action bar at the bottom. On a computer, the document is on the left and the action bar on top.
2. Check the document and the details. See [Review and edit a transaction](/transactions/transactions/edit-a-transaction.md).
3. To move through the list, use the arrows. The count between them shows where you are, such as **2 of 12**.
4. Choose the approver in **Submit to**. **Submit** stays greyed out until you do.
5. If you want, select **Add a note...** and type a note.
6. To have the approver texted and emailed, tick **Send text/email for urgent approval?**. See [Send and answer urgent approval requests](/approvals/review/urgent-approvals.md).
7. Select **Submit**.
The next transaction opens. After the last one, the one before it opens, and when the list is empty the panel closes. To stop, select the X at the top of the side panel.
Your **Submit to** choice carries over to the next transaction, but the note and urgent box clear. If **Submit to** shows **--**, choose someone again.
## Who's in Submit to
**Submit to** lists the approvers at the next level of your production's approval flow for that kind of transaction. If you're not an approver, that's the first level. See [Set up approval flows](/approvals/configure.md).
{% hint style="info" %}
If **Department-based approvals** is turned on for your production in **Approvals > Configure**, the list shows only next-level approvers who are Department Heads, Managers or Super Admins in your department on [Project > Team](/project/team.md). If none is, or you have no department there, it shows them all. The side panel's **Approver** list works the same way.
{% endhint %}
## Submit from an envelope
{% hint style="info" %}
If your company reviews approvals by envelope, you can start from the **Envelopes** view.
{% endhint %}
1. On the **Envelopes** view, select the envelope's **Submit** button in the **Action needed** column. It shows how many you can submit, such as **Submit 3**.
2. **Needs Submission** opens, filtered to that envelope. Submit them as above.
If you created the envelope and they're all waiting on one other person, the button adds their first name, such as **Submit 2 ยท for Sam**. See [Review an envelope](/approvals/review/review-envelopes.md).
## Send or take back from the side panel
The side panel's **Approvals** tab can also send a transaction, with **Approver**, **Notes**, **Send text/email for urgent approval?** and **Send for Approval**. To take one back, open it on the Transactions page and select **Undo Send** on its **Approvals** tab. It shows until someone acts on it, and the transaction comes back here. The steps are in [Send and approve transactions](/transactions/transactions/approve-transactions.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 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/submit-for-approval.md?ask=&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.
