Policy Engine

What is a Policy Engine?

The Policy Engine is a comprehensive risk management tool in Cregis, offering flexible solutions for withdrawal management. It allows users to set detailed rules and automate actions to regulate withdrawal requests from team members, with future plans to support automatic signing and withdrawals for improved efficiency and reduced manual risks. Currently, it supports policy customization for transaction, payment request initiation, and API withdrawals, enabling users to tailor policies to their needs, such as limiting withdrawals to specific tokens or setting time restrictions. The Policy Engine also includes a daily log feature for monitoring and reviewing policy execution, ensuring transparency, tracking, and auditing of all actions to enhance risk management and safeguard assets.

Creation Policy

Accessing the Policy Engine Page

Navigate to the Policy Engine page by selecting "Manage" > "Policy." To begin setting up a process, click "Start Creation"

Action Creation

Click the "+" to create a policy. First, name the policy and then select the corresponding type. The types are Manual Transfer and API Transfer:

Manual Transfer: Transactions transferred via Cregis, including manual transfers from the wallet and manual transfers from addresses within the WaaS project.

API Transfer: Transactions transferred via API, including all wallet withdrawals or project address withdrawals initiated for the WaaS project.

After selecting the type, you can add rules. Please note: Users can set more than one rule for a wallet, and the relationship between the rules is "OR". You can configure trigger rules and actions based on your actual scenario. Finally, submit and verify to successfully create the policy.

Edit and Delete Policies

You can find the options to edit and delete in the following location.

Viewing Policy Logs

You can find the logs in the following location, where you can see the time and operator for each action.

Trigger Rule Explanation

Operation Initiation Configuration

The trigger conditions for rules vary depending on the policy type. Manual Transfer requires configuring members and withdrawal wallets, while API Transfer requires configuring the WaaS project and the withdrawal operation.

Operation Time

Operation Time is used to restrict operations (Manual Transfer, API Transfer) for this policy type. Users can choose "All Day" or "Specified Time" as a condition. If specifying a time, start and end times must be set, and multiple time periods are supported. Please note: This time is based on UTC+8.

Token

In this field, users can select the token for the initiation, choosing either any token or a specific token.

Amount Condition Explanation: Users can set limits for the selected sending currency based on a single transaction, daily, or monthly amount.

Execution Action Explanation We provide three types of execution actions for configuration. The following are the configurable execution actions:

Reject: The system automatically rejects the withdrawal.

Approval: Requires setting up an approval workflow, including defining approval nodes and signers.

Signature: Requires setting up signers.

Practical Usage Scenarios

Actual settings should be based on the user's own needs. The following are some policy engine configuration scenarios.

Scenario 1: I want to restrict Bitcoin withdrawals. All Bitcoin-related withdrawals must undergo approval, and the API service is not used. The trigger conditions and execution actions are as follows.

Trigger Condition Settings

Select the specified token, Bitcoin, and set all transfer limits to trigger the condition when the amount is greater than or equal to 0.