Basic Transaction Policy

What are policies?

Policies govern how Transactions are submitted to approval nodes. Each policy consists of two parts:

  • Triggering Condition: A collection of rules based on multiple parameters of a transaction that correspond to a specific type of transaction.

  • Approval Process: A process for approving a transaction that matches trigger conditions.

In Safeheron, we have 2 kinds of transaction policies:

The policies supported by various types of transactions are listed in the table below:

Basic policies can be viewed in the Safeheron Mobile App, while advanced policies can be viewed in the Safeheron Web Console.

What is the basic transaction policy?

When you create a team for the first time using the Safeheron Mobile App, default basic policies are automatically configured for you. The admin of the team can view and modify the basic policies, allowing you to configure the appropriate Approval Process based on the needs of your organization.

The basic policy allows team members with Create Transaction permission to initiate a transfer transaction or a Web3 Sign task, but it does not support inputting custom parameters such as initiator, triggering conditions, source wallet, and so on.

Simply put, the triggering condition of the basic policy is not customizable and is the same for all transfer tasks and Web3 Sign tasks in the team. The approval process can be configured by the team administrator in the Safeheron mobile app.

All team members with Create Transaction permission can create the transaction, and the sending and receiving addresses, asset types and amount won't be restrained.

Change basic transaction policies

Navigate to Me ➡ Transaction Approval, you can see the option Change Approval Process.

Here, you can change node's name, who to be approvers (choose from members with Approve Transaction permission), how many nodes in the Approval Process.

Last updated