Feature Flag Audit Log
Featureflip records every change to your flags and configuration automatically — who made it, what changed, and when. There is nothing to enable: the audit log captures changes across your organization from the moment you start using Featureflip, so when something breaks you can answer “what changed, and who changed it?” without guesswork.
What gets recorded
Section titled “What gets recorded”Every create, update, and delete is captured across the entities that drive flag behavior:
- Feature flags — created, deleted, toggled on or off, renamed, retargeted
- Variations — added, edited, or removed
- Targeting rules — created, reordered, or changed
- Per-environment flag configuration — the on/off state and rollout for each environment
- Environments — created, renamed, or deleted
- User segments — created, edited, or deleted
- SDK keys — created, rotated, or revoked
- Projects and the organization itself
For an update, each changed property is recorded on its own, with the previous value and the new value, so you can see exactly what moved — for example, a rollout going from 25% to 100%, or a flag flipping from enabled to disabled.
Every entry also stores:
- Who — the actor’s name and email (preserved on the entry even if the member later leaves)
- When — a precise timestamp
- Request metadata — IP address and user agent of the request that made the change
Where to find it
Section titled “Where to find it”There are two views, both in the Featureflip dashboard.
Organization-wide audit log
Section titled “Organization-wide audit log”The Audit Log page shows every recorded change across your organization, newest first. Filter the list to narrow an investigation:
- by project
- by entity (a specific flag, segment, environment, and so on) or entity type
- by action (created, updated, deleted)
- by user
- by date range
Results are paginated, so a high-traffic project stays navigable.
Per-flag history
Section titled “Per-flag history”Every flag has a History tab on its detail page. It shows a complete timeline for that one flag — including changes to everything beneath it: its variations, its per-environment configuration, and its targeting rules. During an incident this is usually the fastest path to “who changed this flag, and when,” without scrolling the organization-wide log. The flag history can be filtered by action and date range as well.
Retention by plan
Section titled “Retention by plan”Audit log history is retained based on your plan, and entries older than your retention window are removed automatically:
| Plan | Audit log retention |
|---|---|
| Solo | 7 days |
| Pro | 30 days |
| Business | 90 days |
| Enterprise | 365 days (custom policies available) |
If you need to keep records beyond your plan window — for a compliance review or a post-incident archive — move to a plan with a longer retention period. See pricing for the current plans.
Using the audit log for incident review
Section titled “Using the audit log for incident review”When a release goes wrong, the audit log turns “something changed” into a specific, attributable fact:
- Open the affected flag and switch to its History tab.
- Find the change that lines up with when behavior shifted — a toggle, a rollout bump, a rule edit.
- Read the before and after values to confirm what actually changed, and who changed it.
Because a disabled flag deterministically serves its off variation, pairing the audit log with the kill switch pattern gives you both halves of incident response: turn the feature off in seconds, then have the record of who turned it off and when for the post-incident review.
Next steps
Section titled “Next steps”- Team Management — invite members and manage roles
- Reliability & Resilience — how flags fail safe when the service is unavailable
- Stale Flag Detection — find flags that no longer make a real decision
- Creating Flags — create and configure flags in the dashboard
Frequently Asked Questions
Section titled “Frequently Asked Questions”Does Featureflip log who changed a feature flag?
Section titled “Does Featureflip log who changed a feature flag?”Yes. Featureflip records every change automatically, with no configuration required. Each audit entry captures who made the change (name and email), what changed (the entity and, for edits, the specific property with its before and after values), and when it happened. Toggling a flag, editing a targeting rule, changing an environment configuration, creating or deleting a segment, and rotating an SDK key are all recorded. You can review the log organization-wide or scoped to a single flag from the Featureflip dashboard.
How long does Featureflip keep audit logs?
Section titled “How long does Featureflip keep audit logs?”Audit log retention depends on your plan: 7 days on Solo, 30 days on Pro, 90 days on Business, and 365 days on Enterprise. Entries older than your retention window are removed automatically. If you need to keep records longer, move to a plan with a longer window.
Can I see the full history of a single feature flag?
Section titled “Can I see the full history of a single feature flag?”Yes. Every flag has a History tab that shows a complete timeline for that flag, including changes to the flag itself and to everything beneath it — its variations, its per-environment configuration, and its targeting rules. This is the fastest way to answer who changed this flag, and when, during an incident review, without scrolling the organization-wide log.
What changes are recorded in the Featureflip audit log?
Section titled “What changes are recorded in the Featureflip audit log?”Featureflip records create, update, and delete actions across feature flags, variations, targeting rules, per-environment flag configurations, environments, user segments, SDK keys, projects, and the organization itself. For updates, each changed property is recorded individually with its previous and new value. Each entry also stores the actor, a timestamp, and request metadata such as IP address and user agent.