Verifying platform access

Checking your signed-in admin role.

Platform administration

Audit trail

Start with exceptions. Open raw receipt history only when an investigation needs it.

What needs investigation

Blocked, denied, high-risk, critical, or malformed events surface here first.

Advanced investigationScope, event class, decision, risk, and dates

Needs attention

Recent exceptions are shown before routine activity.

Waiting for verified data

Audit receipt

How to read the audit trail

  1. 1Search a receipt. Use an event name, resource ID, trace ID, or event hash. The search itself is recorded.
  2. 2Review the decision. Allowed, blocked, and denied events explain what the product permitted without showing the private payload.
  3. 3Open the receipt. Inspect scope, refs, retention class, and the cryptographic chain position.
  4. 4Verify the ledger. Recompute every stored hash and link. A broken result requires an immediate security incident.

Why this matters

Every sensitive action should leave a reference-only receipt: who acted, which scope was used, what policy decided, and which immutable record proves it. Customer documents, messages, prompts, and portfolio rows are deliberately excluded.

Date filters use your current local timezone and are converted to exact UTC boundaries for the ledger search.