Create custom approval workflows

Summary

Approval workflows in Reah are automated controls that require designated team members to authorize actions before they are executed. In addition to Money Movement approvals, Reah also applies approval workflows to governance actions — such as managing users, permissions, accounts, and approval policies themselves.

Set up an approval workflow

1. Click the Settings gear icon at the bottom of the left-hand navigation bar.
2. Under Entity, select Approval Flow to view all available triggers.
3. Toggle the switch On for the category you want to require approval for (e.g., Money Movement).
4. Click into a workflow to configure:
   • Approval groups
   • Approval mode (Any one / Threshold / All)
   • Required approvers
   • Timeout rules
5. Click Publish

What you can require approval for

Reah lets you enable or disable approval requirements by category. When a category is toggled off, actions in that category execute without waiting for approval.

• Money Movement — Transfers, accounts used, and who initiates.
• Approval & Policy Changes — Creating, editing, or deleting approval flows themselves.
• Ownership Changes — Covers sensitive ownership-level operations, including ownership transfers and recovery access updates.
• User & Permission Changes — Adding or removing users, updating permission groups.
• Entity & Account Management — Updating entity-level settings.

How non-transaction approval flows work

Unlike Transaction Management, these categories are generally not based on amount conditions.

Instead, approval is typically determined by:

• The action category
• The initiator group, in some cases
• The configured approval group and approval mode

Depending on the category, workflows may either:

• Route directly to an approval group
• Be auto-approved by default

Default workflow examples

Here are the default approval patterns for the non-transaction categories:

• Approval & Policy Changes → Owner approval
• Entity & Account Management → Auto-approved
• User & Permission Changes → Owner approval
• Ownership Changes → Owner approval

These defaults can be adjusted to match your internal governance requirements.

Best practices

• Require approval for actions that affect governance, access, or ownership
• Keep low-risk operational changes lightweight where appropriate
• Use stricter approval modes, such as Threshold or All, for sensitive categories
• Review approval workflows regularly as your team structure evolves

What to do next

• Set up permission groups in Reah
• Configure transaction approval flows
• Submit, approve, and execute requests