Security Audit
Audit log
Every administrative and marketplace mutation, with correlation IDs.
| When | Actor | Action | Target | Correlation |
|---|---|---|---|---|
| 2 min ago | Maya Ruiz | team.role.update | usr_8f2a…c41 | cor_91af |
| 1 hr ago | George W. Scott III | billing.plan.change | sub_44c1… | cor_77bd |
| 3 hr ago | Dan Kowalski | template.publish | tpl.invoice.layout | cor_2e5c |
| 5 hr ago | System | backup.completed | Ledgerly | cor_0aa4 |
Showing 4 of 1,284 entries
About this page
Who did what, and when — every meaningful action in the account, searchable and filterable, kept for 24 months. Each entry carries a reference ID you can hand to support so they see exactly the event you’re looking at.
Behind this page/audit · CanViewAuditLog
Retrieve
sp_Builder_ListAuditLog reads BuilderAccountAuditLog with actor/action/target/correlation, filtered and paginated.Save
Read-only. Entries are written before commit by services viasp_Internal_WriteBuilderAudit.Success
- Every mutation produces an entry before commit.
- Correlation IDs are searchable.
- Metadata preview is safe/redacted.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Page IDaudit-log
Route/audit
AccessCanViewAuditLog
Statusschema-backed-scaffold
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.