> 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.md). # Tasks ## **What is Tasks?** Tasks is Cregis's transaction management and multi-person co-handling capability designed for enterprise teams. Through mechanisms such as approval and signing, enterprises can segregate transaction initiation, business approval, and transaction signing. Different roles participate together to complete transaction processing, thereby reducing single-point operational risks and establishing a more standardized, secure fund management workflow. For example, an enterprise can configure the following workflow: Employee initiates transaction → Finance approves → Department Head approves → Signer signs → Transaction broadcast to the blockchain. Through Tasks, enterprises can assign different members to different business stages based on their internal fund management policies, achieving segregation of duties, multi-person re-checking, and audit logging. Tasks is suitable for the following scenarios: * **High-Value Transaction Approval:** Large transfers require manager approval before execution. * **Multi-Person Joint Fund Management:** Transactions require multiple members to participate in confirmation or signing. * **Segregation of Duties:** Business operators initiate transactions, finance personnel handle approvals, and signers perform signing. * **Transaction Risk Control:** Initiated transactions trigger manual approval when specific conditions are met. * **Enterprise Fund Management:** Establish standardized fund operation workflows through approval and signing mechanisms. ## Task Workflow Cregis Tasks primarily revolves around transaction initiation, policy matching, approval, signing, and broadcasting to the blockchain. Typical Transaction Workflow: Initiate Transaction → Policy Matching → Approval → Signing → Broadcast to Blockchain **1. Initiate Transaction** Team members or business systems can initiate transactions based on their assigned permissions. Transactions can originate from different operational entry points, such as: * Wallet / Sub-address * WaaS API * Marketplace Once a transaction is initiated, Cregis determines whether it needs to enter the approval process based on the team's configured policies. **2. Policy Matching** The system matches enabled [policies](/3.-wallet-and-risk-control/policy-engine.md) based on transaction conditions. * *Example:* When a single transfer amount is $$ $\ge 100,000\text{ USDT}$ $$, approval is required. If a transaction meets the policy conditions, it enters the corresponding approval workflow. If no policy is triggered, it proceeds directly to the signing stage. Whether approval is required depends entirely on the matched policy. **3. Approval** If a transaction triggers a policy, it undergoes approval sequentially according to the configured workflow: * *Example:* Employee initiates → Finance approves → Department Head approves Approvers can view detailed transaction information and select either: * Approve * Reject Once all approval nodes complete their review, the transaction proceeds to the signing stage. If any approval node rejects the transaction, execution stops immediately. **4. Signing** Upon approval, the transaction enters the signing stage. Members with signing permissions can sign the transaction. The specific members required to sign depend on the triggered policy or the wallet's signing rules. Once the signing criteria are met, Cregis submits the transaction to be broadcast onto the blockchain. * Single-Sig: The transaction proceeds as soon as any single member specified by the policy completes the signature. * Multi-Sig: Specified members participate in signing. The transaction proceeds only after the number of signatures reaches the threshold set for the wallet. **5. Broadcast to Blockchain** After signing is completed, the transaction is broadcast to the blockchain. The final outcome is determined by the on-chain execution result. ## **Roles in Workflow** In team tasks, different members can perform distinct duties:
RolePrimary Responsibilities
InitiatorInitiates transaction requests
ApproverReviews transactions against business requirements and approves or rejects them
SignerSigns transactions to authorize broadcasting to the blockchain
ViewerViews collaboration requests and transaction processing statuses
--- # 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.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.