Settings

Audit log

Append-only record of every significant action taken in your workspace. Member added, role changed, integration saved, workspace setting updated, data exported, API key created, subscription event. Owner+admin can view; owners can export to CSV.

Quick answers

How long is the log kept?

Seven years by default (2555 days). A retention sweep runs nightly and drops rows older than that. Per-workspace overrides exist at the database level — contact support if you need a different window.

Can I delete a log row?

No. The log is append-only by design. The only way rows leave is through the retention sweep or via workspace deletion (cascade). This is what makes it useful for forensics.

Why doesn't every action show up?

Operational actions (creating a lead, sending an email, completing a task) aren't captured — they'd flood the log. Only governance-relevant events are: membership changes, role changes, workspace setting changes, integration credential changes, exports, key issuance, subscription state changes.

How do I export the log?

Owners only. Add ?export=csv to the URL or use the Export button when available. The CSV mirrors the page's filters — useful for compliance reviews and access audits.

What gets captured

Members: invited, accepted, role changed, removed, self-removed, invitation revoked or resent
Workspace: settings updated, ownership transferred, soft-deleted, restored
Integrations: saved, enabled, disabled, deleted
Exports: data export downloaded
API keys: created, revoked
Billing: subscription started, changed, canceled, payment failed, payment succeeded, plan upgraded or downgraded, dunning email sent, trial reminder sent
Field layout: saved or reset
Calendar (Phase 14): connected, disconnected, settings updated, strategy changed, bookable changed, sharing changed
Lead/client assignment (Team plan): assigned
Cancellation feedback submitted
Workspace signup
Booking form updated
Audit log exported

The filter bar

Event type select (all the types listed above), actor select (workspace members + "System" for engine-driven rows), Apply and Clear. The list pages 50 rows at a time.

Row shape

Each row shows the event type with a pill, the actor (who did it; "System" for engine-driven rows), a timestamp, the IP and user-agent (when known), and an event-data JSON blob with the specifics. Strings in event_data are capped at 1024 chars per field.

Hard-delete actions

Workspace and user hard-deletes from the admin console are intentionally NOT in the audit log — the cascade would immediately delete the audit row along with the workspace itself, making the entry useless. Those events get logged to the server's stdout instead.