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.

How to use the Policy Engine?

1. Accessing the Policy Engine Page

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

1. Action Creation

Before creating rules in the Policy Engine, a policy must first be established. We offer configurations for three types of withdrawals, which users can customize based on their business needs. Once the settings are configured, they must be submitted and will require identity verification before they take effect.

We offer configurations for three types of withdrawals and their corresponding execution actions. Below are the execution actions available for each type:

Withdrawals Type	Transaction	Payment Inititation	API Withdrawal
Configure Withdrawal Wallet	No need	Yes	Yes
Action	Reject Initiate approval request	Sign Directly Initiate approval request	Sign Directly Initiate approval request

• Action：Reject No advanced settings are required, you can submit directly.

• Action：Initiate approval request Approval workflow configuration is required, including setting up approval nodes and assigning signatories.

• Action: Payment Signing You need to designate signatories. Since direct signing is only applicable to payment requests and API withdrawals, it is generally necessary to configure the withdrawal wallet first. Once this is completed, you can proceed with the submission.

Once successfully created, the screen will automatically redirect to the policy logs, where you can see a record of the policy you just established.

You can also go to the "Action" page to view your previously created action.

1. Policy Creation

To create a policy, go to the Policy page and click on the "+" button.

• General Setting

  Set the name, type, and relevant settings for this policy, and assign a priority level. When multiple policies are triggered simultaneously, the one with the highest weight will be executed first. For example, if policy A has a priority level of 10 and policy B has a priority level of 5, policy A will be prioritized.

  • If the type is "Transaction", select the source wallet.

  • If the type is "Payment Initiation," no additional settings are required.

  • If the type is "API Withdrawal," select the project.

  
• Conditions

  After completing the basic settings, define the rules for the policy. Conditions can be based on the token amount or operation time. Users can choose to set one or both.

• Token

  In this section, users can select the token. If specific tokens are required, each token must be individually configured with a set amount. Limits can be placed on single transactions, daily, or monthly amounts.

  

• Operation Time This limits the operation time for the policy type (Transaction, Payment Initiation, API Withdrawal). Users can select "All Day" or specify a time range. If a specific time is chosen, start and end times must be set. It also allows you to add multiple time periods. Please note: Time is based on UTC+8.

  
• Triggered conditions Users can choose "All Conditions" or "Any Condition." Any Condition means the policy will trigger if either the operation time or the token condition is met.

• Action triggered After setting the trigger conditions, users can select the execution decision from the list of previously created policies of the same type.

Withdrawals Type	Transfer	Payment Inititation	API Withdrawal
Configure Withdrawal Wallet	No need	Yes	Yes
Action	Reject Initiate approval request	Sign Directly Initiate approval request	Sign Directly Initiate approval request

• Please note: Users can set multiple rules for a single wallet, with each rule being in an "OR" relationship.

• After configuration, identity verification is required.

• After configuration, identity verification is required. Then the system will redirect you to the Policy page, where you must activate the policy.

• Before activation, identity verification and Google two-factor authentication are required.

• Once this is completed, the Policy Engine setup is finalized.

1. Editing and Deleting Policies

• Editing a Policy Policies can be edited on the Policy page. Before editing, the policy must be disabled, which also requires identity verification. Then you can find the edit icon as below to start you editing.
• Deleting a Policy Policies can be deleted from the policy page. Before deletion, the strategy must be disabled, which also requires identity verification. Then you can find the delete icon as below.

  

1. Viewing Policy Logs

In the Policy Logs, you can see the actions of each policy, including date, time, operator, and actions performed. This page allows filtering by operation date, operator, or policy type.

The search bar also supports searching by action/policy name or ID.

Additionally, if an action triggers a policy, you can view the hit log, which provides detailed information about the triggered policy.

Triggered Actions

There are currently three types of actions that can be triggered, each with a corresponding screen display:

• Reject If the action triggers a rejection, a window will pop up indicating the operation failed and notifying the user of the triggered policy.

• Initiate Approval Workflow

If the approval workflow is triggered, a notification will appear, informing the user of the triggered policy.

• Payment Signature No window will pop up for payment signature action, but you can view the hit policy when checking the details of the request.

Expanding the Number of Policies

The basic version only allows the creation of two policies and two actions, and each policy can only be applied to one wallet only. To increase the number of policies, users can upgrade or expand services on the account page.

1. Upgrade Team Package

Users can choose to upgrade to the Business or Enterprise edition based on their business needs.

1. Expand Policies

In addition to upgrading the team package, users can choose to increase the number of policies by clicking "Expand" and selecting the desired number. Each additional policy costs $19 USD.