> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/2.-transaction-and-account/tasks/approval-process.md).
# Approval Process
When a transaction triggers a Policy, and the current account is assigned as an approver with approval permissions, the transaction will be routed to Tasks > Approvals. Approvers can choose to approve or reject the transaction. Cregis supports both single and batch approvals to help teams process pending transactions efficiently. Once processed, you can view the approval history under Tasks > Approved.
**Single Approval**
Navigate to Tasks > Approval, find the target transaction, and click Revie on the right side.
On the approval details page, review the transaction details. Based on your review, select:
* **Approve**: Authorize the transaction to proceed.
* **Reject**: Decline the transaction, terminating it immediately.
Click Approve or Reject. The system will prompt you for identity verification—enter your Transaction Password and click Confirm.
Upon successful verification, a confirmation message will appear.
* **If approved**: The transaction moves to the next stage in the process.
* **If rejected**: The transaction is terminated.
**Batch Approval**
When handling multiple pending transactions, use batch approval to streamline the process.
Navigate to Tasks > Approvals and click **Batch Process** in the top right corner.
Select the transactions you wish to process and choose an action:
* **Approve**: Authorize the selected transactions to proceed.
* **Reject**: Decline the selected transactions, terminating them immediately.
*(Optional)* Enter any operational notes in the remarks pop-up window, then click Confirm.
Complete the identity verification by entering your Transaction Password and clicking Confirm. A success notification will appear once verified.
* If **approved**: The transactions move to the next stage.
* If **rejected**: The transactions are terminated.
---
# 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://support.cregis.com/2.-transaction-and-account/tasks/approval-process.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.
