> 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/cregis-wallet-guide/zh-cn/accountmanagement/teamwork/approval.md).
# 审批流
当交易触发策略，且当前账号被指定为审批人并拥有审批操作权限时，该交易会进入协作 > 待审批，审批人可以对交易进行审批或驳回。Cregis 支持单笔审批和批量审批，帮助团队高效处理待审批交易。审批完成后，可以在协作 > 已审批中查看已经处理的审批记录。
**单笔审批**
进入协作 > 待审批，找到需要处理的交易，点击交易右侧的「处理」。
进入审批详情后，可以查看该笔交易的详细信息，确认交易信息后，可以根据实际情况选择：
**审批**：同意该交易继续执行。\
**驳回**：拒绝该交易，交易将终止。
点击「审批/驳回」 后，系统会要求进行身份验证，输入交易密码并点击「确定」。身份验证通过后，系统会提示操作成功。
**审批通过后**：交易进入后续流程。\
**审批驳回后**：交易终止。
**批量审批**
当待审批交易较多时，可以使用批量审批一次处理多笔交易，提高审批效率。进入协作 > 待审批，点击右上角的「批处理」。
勾选需要处理的交易，选择交易后，可以根据实际情况选择：
**审批**：同意该交易继续执行。\
**驳回**：拒绝该交易，交易将终止。
如需对本次操作进行备注说明，可在备注弹窗输入备注信息（非必填），点击「确定」。
系统会要求进行身份验证，输入交易密码并点击「确定」。身份验证通过后，系统会提示操作成功。
**审批通过后**：交易进入后续流程。\
**审批驳回后**：交易终止。
---
# 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/cregis-wallet-guide/zh-cn/accountmanagement/teamwork/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.
