Overview#
An Approval Node defines who reviews a transaction that has matched a policy, and how many approvals are required. Policies reference Approval Nodes when their action is to require approval — the policy decides when approval is needed, the Approval Node decides who reviews it and how many must agree.Approval Nodes are not the same as Decision Mode. An Approval Node governs the release of an individual transaction, and its participants are members and API Keys holding the Approve transactions permission. Decision Mode governs changes to Team configuration, and its participants are always all Admins.What a node contains#
Approvers can be set to all members or to specific members. Choosing all members includes members added in future who hold the Approve transactions permission — new members are covered automatically, with no need to revisit the node.Approving API Keys work the same way: all API Keys or specific ones, with "all" likewise covering API Keys added in future that hold the approval permission.The approval threshold is the number of approvals required, up to 20. It is displayed as "approvals required / total eligible approvers."Managing Approval Nodes#
The node list shows each node's approver scope, threshold, status, and the policies that reference it.Creating or editing a node takes effect only after approval under your Team's Decision Mode. Until then, transactions that have already matched the node continue to follow its previous configuration.Things to note#
Editing an Approval Node affects every policy that references it. Check the node details for the list of affected policies before making changes.The approval threshold should not exceed the number of people who can actually approve. If the number of members holding the Approve transactions permission falls below the threshold, transactions matching that node cannot collect enough approvals. When adjusting member permissions, review your Approval Node thresholds at the same time.Modified at 2026-08-26 02:51:05
