Docs / Platform & security / The audit log

The audit log

Every mutation is logged. How to read the audit log and what it captures.

Every settings change, client edit, template update, commission plan adjustment — every action that mutates data — writes a row to the audit log. The log is owner-visible and permanent.

Where to find it

Owner → Admin dropdown → Audit log. Or directly at /audit-log.

What a log row contains

  • Timestamp — to the second.
  • Actor — user who made the change (or "system" for automated actions).
  • Action — e.g., tenant.settings.update, client.update, commission.attribution.change.
  • Entity — the record that changed (e.g., "Client #142").
  • Before / after diff — only the fields that actually changed, with old and new values.

What is logged today

  • Tenant settings changes (full coverage)
  • Client record updates (coverage growing)
  • Visit lifecycle transitions (full coverage)
  • Invoice state changes + refunds + write-offs
  • Commission plan changes and payout state transitions
  • Super-admin impersonation events

What is NOT logged (yet)

  • Read-only access patterns (who viewed what)
  • Template edits (coming Q3)
  • Employee record changes (coming Q3)
💡
When you have a dispute with an employee about who changed a client's pricing or a commission plan, the audit log is the record of truth. It is also useful for training: "here is what I did last Thursday, you asked why" kind of conversations.
The audit log is append-only from your side — you cannot edit or delete rows. This is intentional. If you think a log entry is wrong, contact support; we can annotate but not modify.

Was this article helpful?

Contact support