Set up four-eyes approval

Four-eyes — a second person approving what the first proposed — is the control regulators ask about first. This guide configures it on a high-impact gate.

1. Add approver roles#

Open Settings → Roles. Create ops_lead and compliance. Assign members. SSO groups map automatically if you use SAML / OIDC.

2. Configure the gate#

In your graph, on the step that needs approval:

gate:
  type: gate.hitl
  quorum: 2
  roles: [ops_lead, compliance]
  sla: 4h
  escalate: vp_ops

3. Enable conflict-of-interest blocks#

On the same gate, enable:

• Self-approval block — the run initiator cannot approve their own request
• Same-team block — approvers from the initiator’s team are excluded (if your policy requires it)

4. Test the flow#

Run the graph with an input that reaches the gate:

1. The gate opens; the ledger records gate.opened with the initiator.
2. Try approving as the initiator — blocked, with the block message visible.
3. Approve from two different approver accounts (one on mobile via WebAuthn / TOTP).
4. The gate closes; the run advances; the ledger records both signatures with timestamps and justifications.

5. Verify the record#

Export an evidence bundle for the run and verify offline. The approvals are part of the hash chain.