Four-eyes principle: organisational mandates with signing rules
Last updated: · Leutrim Miftaraj
Organisations grant authority differently from individuals: above a defined threshold an organisational mandate needs two signatures from authorised signatories — and that rule must be enforced, not recommended.
Enforced means: the database
The four-eyes check lives as a database trigger, not as a checkbox in the frontend: 0/2 signatures block activation, 1/2 block, duplicate signatures by the same person are impossible (unique constraint), 2/2 activate. No admin click bypasses it.
Role model
Owner, admin, issuer, auditor, developer — signing authority is a separate attribute, independent of the role. A developer can manage keys without ever being able to sign a mandate.
Audit readiness
Every signature is part of the evidence chain; the audit export shows internal audit that the organisation's signing rules were technically enforced — not merely documented.
Key takeaway
Compliance that lives in the frontend is decoration. Four eyes belongs in the trigger.
Try it yourself
Issue your first agent mandate and check your first decision with its receipt — free, in a few minutes.