Access and credential audit
Screen 8.2 — filter and export authorized identity, access, credential-lifecycle and policy audit events.
PEEK Technical Reviewer · PEEK Platform Administrator
/peek/customers/tenant-a/8-2Every screen action emits an audit event named admin.screen.<id>.action (for example admin.screen.1.4.action). 8.2 lets operators with audit.read filter those events by actor, issuer subject, action, tenant and reason; audit.export (Technical Reviewers) produces a controlled export with access control and expiry.
Audit event fields
- Actor / issuer subject
- Who acted, with the identity issuer.
- Action
- The command or screen action.
- Tenant
- The customer context (or global for catalogs).
- Vault reference metadata
- Credential lifecycle metadata only — never a secret value.
- Reason
- Safe reason code; results include provenance and correlation.
8.2 · Access & Credential Audit
Audit administrative and credential lifecycle events. Open it at /peek/customers/tenant-a/8-2 (any tenant ID you can access works in place of tenant-a). The primary action is Review or export authorized audit, which requires audit.read or audit.export.
How 8.2 works
1. Filter authorized identity, access, credential lifecycle and policy events
2. Export permitted evidence
Screen 8.2 contract
- Fields shown
- Actor, issuer subject, action, tenant, vault reference metadata, reason
- Primary action
- Review or export authorized audit
- Required capability
audit.readoraudit.export- Validation
- No secret values, protected prompts or unauthorized agency content. Query and export use current audit-scope rights.
- Successful outcome
- Result includes event provenance, correlation and safe reason codes; export has controlled access and expiry.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.8.2.action(acceptance testAT-UI-8.2)- Requirements
- R02, R06, R14, R21, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-8.2