Activity log
Every configuration change, money movement and lead decision in your workspace, with who made it and what the value was before.
Activity is your workspace's audit trail: who changed what, when, and what the setting was before they touched it. Open it from the sidebar.
Every row names the person who acted (or System, for webhooks and scheduled jobs) and the time in your organization's timezone. Rows with a chevron expand into a Field / Before / After table.
What the log contains
- Configuration — pipelines, routing rules, buyers, delivery methods, sources, and organization settings. Created, updated, archived, API keys regenerated.
- Money — wallet top-ups and adjustments, compensation credits granted and used, subscription payments.
- Lead review — leads approved, rejected or auto-released from the review queue, fields edited by hand, disputes opened and resolved.
- People & access — invitations, members removed, sign-ins, buyer portal sign-ins.
- Lead operations — CSV imports, exports, canceled deliveries.
What it doesn't
The per-lead machine traffic — every lead ingested, every duplicate rejected, every lead flagged as spam or forwarded — is hidden by default. One row per lead would bury the decisions you actually want to audit, and that history already lives on each lead's own page, where it belongs.
Tick Show system lead events to fold it back into the feed.
Filtering
- Category narrows the feed to configuration, money, lead review, people, or lead operations.
- Event type picks a single kind of change, such as "Routing rule updated".
- Date range defaults to the last 30 days.
- Member (owners only) shows one person's actions, or everything done by the system.
Before / after values
An expandable row records exactly which fields the change touched. A field the request didn't send never appears, so a rule where only the price moved shows one line, not forty.
Secrets are never written to the log. When an API key, a source key, a portal password or a webhook authentication header changes, the row shows the field and marks both values redacted — enough to prove the change happened, never enough to reveal the value. A secret that didn't change leaves no trace at all.
Long values are shortened, and deeply nested settings show as changed rather than dumping their contents into the table.
Events recorded before this detail existed still appear, but have nothing to expand.
Timezone
Times, and the Today / Yesterday grouping, follow your organization's timezone — not your browser's. Set it in Settings → General → Timezone. A workspace operating in Sydney sees its own day boundaries even when someone reads the log from Europe.
How long it's kept
- Two years for the audit trail: configuration changes, money movements, lead review decisions, and people and access events.
- 180 days for the rest, including the system lead traffic.