Set transaction approval rules

Summary

In Reah, all transactions are processed through an approval flow.

Instead of configuring isolated rules, you define how transactions are routed based on conditions (such as amount) — and which groups must approve before execution.

This allows you to:

• Automatically approve low-risk transactions
• Require additional approvals for higher-value actions
• Enforce structured, multi-level controls across your team

How approval flow works

Each transaction goes through three stages:

1. Initiate — A user submits a transaction
2. Approve — The system routes the request to the appropriate approval group(s)
3. Execute — The transaction is executed once approval requirements are met

The system evaluates conditions from top to bottom and executes the first matching branch.

Configure approval conditions

You can define multiple branches based on transaction amount (USD value), for example:

• Small amounts → Auto approve
• Medium amounts → Admin approval
• Large amounts → Admin + Owner approval

Each branch can be configured with:

• Condition (e.g. amount range)
• Whether the branch is active
• Approval groups
• Approval mode:
  • Any one
  • Threshold (e.g. 2-of-3)
  • All approvers
• Approval timeout

Approval behavior by role

Approval behavior depends on who initiates the transaction.

Owner-initiated transactions

• Only require approval within the Owner group
• Do not go through lower-level approval groups

Admin-initiated transactions

• Do not bypass existing approval steps
• First trigger approval within the Admin group
• If the required approval threshold is not met, the request escalates to the Owner group

Member-initiated transactions

• Follow the configured approval flow as defined
• May require Admin and/or Owner approval depending on the amount

Timeouts and fallback

Each approval step can include a timeout.

If approvals are not completed within the defined time:

• The request can be automatically rejected, or
• Escalated to the Owner group for further review

Example

Here’s an example of a tiered approval flow:

• $50 transfer → Auto approved
• $500 transfer → Requires 2 Finance Admin approvals
• $10,000 transfer → Requires 2 Finance Admin approvals + 1 Owner approval

This setup ensures:

• Small transactions move quickly
• Larger transactions receive additional oversight

Best practices

• Use tiered conditions to separate low, medium, and high-risk transactions
• Keep small transactions frictionless with auto-approval
• Require multi-level approvals for high-value transactions
• Set reasonable timeouts to avoid blocking operations

What to do next

• Submit and approve transactions
• Set up permission groups
• Manage treasury deposits and withdrawals