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

How to open "Rollback" (Audit & Governance) and read it

Rollbacks that really happened: change requests rolled back, feature rollbacks and ledger entries naming a rollback.

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 "Rollback" (address /admin/audit/rollback). Under the title the line "Data: ..." names where the figures come from: Live: i8_configuration_change_requests, i8_feature_audit_log, i8_audit_ledger. Read-only and immutable..

2

Read the KPI tiles

Tiles: "Ledger entries (all time)", "Ledger entries, last 24 h", "Shown here". A tile that says "unavailable" means its source could not be read; it is never shown as zero.

3

Read the table

Columns: When, Source, Action, Actor, Target, Severity, Hash, Integrity. Each row is one audit entry, newest first (up to 300 per source). Actors are masked (first and last characters only). Integrity says VERIFIED or TAMPERED only for entries that belong to the Security OS hash chain, HASHED for entries that carry a stored hash, and NOT_CHAINED for plain ledger appends, which no chain attests.

4

Know the limits

This screen records rollbacks; it cannot perform one. Roll back an item in the console that owns it. 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/rollback: 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