Product Guides•stable•Updated 2026-05-15

Guardrails — Audit

Explore audit events, verify integrity, seal anchors, and export audit logs.

What this page is for

Audit is the compliance and traceability surface for governance operations. It supports event exploration, detailed inspection, export, integrity verification, and anchor sealing.

Who uses it

  • Security reviewers
  • Admins
  • Compliance teams
  • Support teams

What you see

  • Paginated or infinite audit log list with date, action, actor, resource, result, severity, source, and failure reason.
  • Filters for date, action, actor, resource, and result.
  • Actor types such as user, api, and scim.
  • Detail sheet with payload, actor details, resource details, technical context, metadata JSON, before/after, and changed fields.
  • Integrity panel with verified, fullySealed, anchorCount, coveredItemCount, unsealedItemCount, hashes, sealing dates, and issues.
  • Proof state when available, including S3 export metadata and checksum.

What you can do

  • Open event details.
  • Export CSV or NDJSON.
  • Verify integrity.
  • Seal the next anchor.
  • Inspect proof/export state.

Permissions and safety

  • Audit access should be restricted to authorized users.
  • Integrity and sealing actions are sensitive and should be audited themselves.
  • Exports may be inline, persisted, or automatically resolved by the backend.

Operational notes

  • Export, verification, and sealing operations should create audit events.
  • Auto export can return a direct download for small exports or persisted storage for large exports.

What this page is not for

  • Replacing operational case timelines in Alerts.
  • Replacing usage traces in Developers.
  • Editing governance records.

Recommended workflow

  1. Confirm that you are in the right workspace and environment.
  2. Use filters before changing configuration or interpreting results.
  3. Open the detail drawer when available.
  4. Check related objects such as alerts, approvals, costs, policies, runs, deliveries, or audit entries.
  5. Apply changes only when the impact is clear.
  6. Re-check the page after the backend refreshes.
  7. Export or copy IDs when you need to escalate.

Related product areas