Audit log
Every sensitive action, from access granted to invoice raised, is written to an audit log your studio can review.
A record of what happened
Every sensitive action is recorded: authentication events, document views and downloads, access grants and revocations, invoices, and admin actions, each with who, when, and why.
Tamper-evident and append-only
Logs are append-only and access-restricted. Corrections are made through new entries, not edits, so the history can be trusted.
Cause on every change
Access grants and revocations are logged with their cause (the payment ID, the event, or the admin who made the call) so nothing about who can see what is a mystery.
A record you can stand behind
Every sensitive action (a sign-in, a download, a grant, an invoice) lands in an append-only log with who, when, and why. Corrections are made through new entries, never edits, so the history stays trustworthy.
- Who, when, and why on every line
- Append-only and tamper-evident
- Every grant logged with its cause
Off the ledger, onto the workspace
Who granted access, and why? Nobody's quite sure.
Every grant and revoke logged with its cause.
A record edited after the fact, with no way to tell.
Append-only entries; corrections are new lines, never edits.
Sensitive actions leave no trace behind them.
Auth, views, downloads, invoices and admin actions all recorded.
Built to carry the weight
Nothing goes unrecorded
Sign-ins, views, downloads, grants, revocations, invoices, admin actions, each one lands in the log as it happens.
Append-only by design
Entries can't be edited away. Corrections are new entries, so the history stays trustworthy and tamper-evident.
The cause, every time
Each grant or revoke carries its reason (the payment ID, the event, the admin) so access is never a mystery.
Everything, in the file
What gets recorded
- Authentication events
- Document views and downloads
- Grants, revocations, invoices, admin actions
How it holds
- Append-only
- Access-restricted
- Tamper-evident by design
On every line
- Who
- When
- Why, the payment ID, event, or admin
Corrections are made through new entries, not edits, so the history can be trusted.
Every sensitive action (authentication events, document views and downloads, access grants and revocations, invoices, and admin actions) each with who, when, and why.
No. The log is append-only and access-restricted. Corrections are made through new entries rather than edits, which keeps the history tamper-evident.
Yes. Every grant and revocation is logged with its cause, the payment ID, the event, or the admin who made the call.