Help Center/Governance, RBAC & Security Desk/How to open "Four-Eyes Control" (Audit & Governance) and read it
Governance, RBAC & Security Desk•Last updated: 2026-10-20•3 min read

How to open "Four-Eyes Control" (Audit & Governance) and read it

Configuration change requests with proposer, reviewer and approver, a computed check that a second person approved, and every approval the Super Administrator gave to their own submission anywhere on the platform.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the screen

In the admin sidebar open the "Audit & Governance" group and click "Four-Eyes Control" (address /admin/audit/four-eyes). Under the title the line "Data: ..." names where the figures come from: Live: i8_configuration_change_requests and the SELF_APPROVED_BY_SUPER_ADMIN entries of i8_audit_ledger. Read-only and immutable..

2

Read the KPI tiles

Tiles: "Change requests", "Approved by a second person", "Approver is the proposer", "Self-approved by the Super Administrator", "Awaiting an approver". A tile that says "unavailable" means its source could not be read; it is never shown as zero.

3

Read the table

Columns: Updated, Change, Target, Request status, Proposer, Reviewer, Approver, Four-eyes. Each row is one change request. "Four-eyes" is TWO_PEOPLE when the approver differs from the proposer, SAME_PERSON when they are the same DID with no self-approval record, SELF_APPROVED_BY_SUPER_ADMIN when the Super Administrator approved their own request (the audit ledger holds the matching entry), AWAITING_APPROVER when nobody has approved. Self-approvals in other areas (wallet adjustments, refunds, rule versions, payouts and more) are listed as extra rows with the area in the Change column. It is computed from the data, not entered by anyone.

4

Know the limits

It is read-only and immutable: no button edits, hides or removes an audit entry, and a source that cannot be read is named in the description instead of being shown as empty. No New Record, edit or delete controls appear on this screen.

Expected Operational Outcome

You can read live, definition-backed figures and records for this area and know what the screen does not do.

Troubleshooting & Failure Modes

Symptom: Failed to load audit/four-eyes: HTTP 403
Likely Cause: The operations API requires an administrator principal.
Resolution: Sign in with an administrator account and click "Retry".
Symptom: A tile or the description says a table "has not been created in this database"
Likely Cause: A database section (918 or 919) has not been applied yet.
Resolution: Ask the platform owner to run npm run db:apply:insight-security. Until then the screen reports it and offers no write buttons.

Was this guide helpful?

Help us refine our platform documentation