Audit Logs
Audit Logs answer the question every finance process eventually faces: who changed this, and what exactly did they change? Every create, update, and delete on sensitive records is recorded with the actor, the target, and a field-level diff.
Open it at Settings → Audit Logs.
When should I read this?
- An invoice total changed and nobody remembers why.
- Compliance asks for evidence of access controls in practice.
- You suspect a settings change broke billing and want the timeline.
Use cases
| Scenario | What you do |
|---|---|
| "The price was different yesterday" | Filter to the record's target type and find the UPDATE with the diff — old and new values side by side. |
| Monthly compliance review | Filter Action = DELETE and Target Type = Users; export the narrative from the visible log. |
| Debugging a billing regression | Walk the timeline around the incident: the request ID ties log entries to backend traces. |
Reading the log
Each row shows:
| Column | Meaning |
|---|---|
| Actor | Who made the change (user with avatar, or the system account). |
| Action | CREATE (green), UPDATE (blue), or DELETE (red). |
| Target | What was touched — record type plus ID. |
| Fields changed | Count of modified fields. |
| When | Relative timestamp. |
Click a row to expand it: the request ID and a field-level diff viewer showing before/after values for every changed field. That diff is the difference between "someone changed the invoice" and "someone changed the invoice total from $1,200.00 to $1,050.00 at 14:32".
Find the entry you need
- Search: match by target ID or actor (debounced as you type).
- Target Type: Users, Organization, Subscription, Invoice, or All.
- Action: CREATE, UPDATE, DELETE, or All.
Combined, these answer targeted questions like "all updates to this subscription" or "everything this user deleted" in seconds.
Scope and retention
Audit logging covers the sensitive console objects — users, organization settings, subscriptions, and invoices among them — and records system actions (such as automated billing outcomes) under the system actor alongside human ones. Logs are retained in the workspace and count toward your record-keeping posture; they are append-only — corrections appear as new entries, never edits to old ones.