// wiki / audit-logs

Audit log

When something changes in production, "who did this, and what exactly did they change" shouldn't depend on anyone's memory.

Why this matters more than it seems

A flag flips, a customer complains, and now three people are in a chat thread trying to reconstruct what happened from memory and a handful of screenshots. Or an auditor asks who had the ability to change pricing logic in production last quarter, and the honest answer is "we're not sure." Both situations are avoidable if every change is already written down the moment it happens.

Under Change Log in the dashboard, recorded organization activity appears in a searchable timeline. Available entries can include changes to flags, applications, environments, members, webhooks, streaming, approvals, and segments.

Narrowing down what you're looking for

A busy organization produces a lot of history. Five filters combine to get you to the entry you actually need:

Change type

Narrow to one category — flags, flag configuration, segments, applications, environments, user management, approvals, webhooks, streaming, or caching — so an incident review of flag changes isn't buried under member invites.

Flag, action, environment, and user

Pin it down to one flag, one action (create, update, promote, enable/disable, delete, and more), one environment, or one person — and combine all four at once. A flag that's since been deleted still shows up in its history with a clear "deleted" marker.

Reading an entry: before and after, side by side

The table shows who, what, and when at a glance — timestamp, user, action, the resource touched, and which environment. Click a row to expand it, and every field that changed lays out its previous value in red next to its new value in green, so you're reading exactly what moved instead of decoding a raw diff.

Undoing a mistake without guesswork

For a flag configuration update, the expanded entry offers Revert to this version — it restores the rules, enabled state, default variant, and rollout percentage to exactly what they were right before that change. The revert itself becomes a new entry in the log rather than erasing what came before it, so the history stays a complete, honest record even after you've undone something.

Where it earns its keep

During an incident, it's the first place to check what changed right before things went wrong — and the fastest way to put things back. During a compliance review, export the filtered results to CSV or JSON straight from the toolbar and hand over exactly the slice you were asked for. Paired with an approval workflow, it's the record of not just what changed, but who signed off on it and why.