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.

Who acted

Five kinds of actor appear on the second line of a row:

a person — their name, or their email when they haven't set one;
an API key — API key "Billing automation", when the change came through the public API. The key is named rather than the person who created it: the action was your system's, not theirs;
a buyer — their name, for what they did in their portal;
an assistant — the connection's name, for a change a connected assistant made. Like an API key, the connection is named rather than the person who set it up — though unlike a key, somebody on your team approved that exact change before it was applied;
System — webhooks, scheduled jobs, and everything else nobody clicked.

When the change carried a reason — an API pause sends one — it shows under the row as Reason: …, in the words that were sent.

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.

A change a connected assistant made gets its own row, named after the connection it came through: Claude via "Ops laptop". When you clicked Apply or Undo on the preview card in Claude rather than saying yes, the row adds from the card in Claude. It carries the one-line summary you approved, and it sits alongside the ordinary row for the change itself, so a paused buyer reads the same way whoever paused it.

Pick Assistants in the actor filter to read a session end to end.

Undoing one

A row an assistant wrote carries a Revert button for 7 days. Click it and you are shown what the undo restores before it happens.

A change is put back to its previous values, and money is compensated by an opposite entry. Something it created is archived or switched off, except a routing rule, which is deleted like the Delete button on the pipeline's rules.

If somebody edited the same thing after the assistant did, the revert stops and tells you what they changed. You can then put back only the fields the assistant moved and leave their edits alone. Something the assistant created and somebody changed since is never removed by a revert: remove it by hand if you no longer want it.

Past 7 days the row stays with its full diff and the button is gone. The only route then is making the opposite change, which the assistant will happily do.

Reverting needs the Admin role, like the change itself. Members see every row and are offered no button.

A whole session at once

When an assistant makes several changes in one go — setting up a buyer with its endpoint and its rules, say — the rows fold into one line: Claude via "Ops laptop" made 14 changes in one session. Show opens them; Revert all puts back everything that still can be, newest first, and tells you plainly what could not.

A session currently means everything one connection changed within the same clock hour, so it can hold two conversations. The confirmation lists what it is about to undo before you approve it.

Where else it shows

A buyer, pipeline or routing rule an assistant changed in the last 7 days says so on its own page, above the settings it moved, with the same View and Revert. Past 7 days the banner goes quiet and the change stays here.

Assistant changes are kept for two years, like every other configuration change.

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.
Actor narrows to assistants, to people, or to the system (webhooks and scheduled jobs). People is only what someone did in the app: a change an assistant or an API key made is not counted as theirs. Owners also get one entry per member, to read a single person's actions.

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.