Multi-Party Approval — Overview
Route decisions to multiple approvers with configurable consensus strategies. Three approval strategies — Any, All, and Quorum — handle everything from first-response approval to unanimous consent requirements.
When to Use Multi-Party Approval
Single-approver approval nodes suffice for simple cases. Use multi-party when:
- Multiple stakeholders must independently agree (e.g., budget approval requires Finance + Manager sign-off).
- You need a quorum — e.g., 3 of 5 committee members must vote approve.
- You want the first available approver in a pool to respond, reducing wait time.
- Your compliance process requires an audit trail of individual decisions.
Three Strategies at a Glance
Any
First actor to approve wins — approval completes immediately. Rejection by one actor does not abort; only all-reject aborts.
All
Every actor must approve. A single rejection immediately fails the approval. Use for strict sign-off requirements.
Quorum (N of M)
N approvals out of M actors are required. Configure threshold as a count or percentage. Remaining actors can still vote after quorum is reached.
Decision Lifecycle
ApprovalNode executes
Engine suspends execution. HIL tasks created — one per approver in the list.
Actors decide
Each actor sees the task in their approval inbox. They approve or reject with an optional comment.
Consensus check
After each decision, the ApprovalStateTracker evaluates the strategy. If consensus is reached, the execution resumes.
Resume
Execution resumes from the approved or rejected output port with the aggregate decision.