> 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/resources/faq/team_account/ru-he-she-zhi-shen-pi-liu-cheng.md).

# 如何设置审批流程？

目前审批流程需要通过策略中心进行设置，用户可配置在特定条件下，出款必须经过审批流程后才能进行签名。

此功能为收费功能，仅对商业版和企业版团队开放。如需开通此功能，请参考[这里](/cregis-wallet-guide/zh-cn/accountmanagement/bill_and_payment/feature_activation.md)。如已开通功能，可参考[策略中心](/cregis-wallet-guide/zh-cn/transaction-riskcontrol/policy_engine.md)进行相关设置。

<figure><img src="https://2287475285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSdMhazXkh30OBfLly0nW%2Fuploads%2F7C46tu2b10zgL2K4F4EQ%2Fimage.png?alt=media&amp;token=4efe1e4b-c69b-4004-951d-b85cb92704c1" alt=""><figcaption></figcaption></figure>


---

# 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/resources/faq/team_account/ru-he-she-zhi-shen-pi-liu-cheng.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.