Review the audit log and event feed
Find out who changed what and when, narrow the list down and take a copy for your own records.
- Time
- About 10 min
- Who can do it
- Anyone with audit.read; audit.export to export
- Where
- Events and Audit Logs, in the console
- You finish with
- The exact record of a change, or an export for your files
What and why#
Every change made in FlagSwift, by a person, an API key or the system, is written to an append-only audit log with the actor, the time, the request ID and the values before and after. When something breaks or someone asks “who turned that on?”, the audit log is where you get the exact answer.
Two views of the same record#
The Events page is the readable story: flag changes, releases, keys and team changes in plain words, grouped into categories, with the ones that deserve attention marked. The Audit Logs page is the exact record: every field, filterable and exportable. Events are the audit trail seen as typed events, so both show the same entries to the same people.
What is recorded#
Flag creation, toggles, rollouts, targeting, kill switch use, releases and their steps, projects, environments, segments, alerts, members and invitations, roles, API keys (including each time one is copied), configuration exports and imports, audit exports and organization changes. Passwords, tokens, secrets and key material are redacted before values are stored.
Before you start#
- Reading takes the
audit.readpermission. Exporting takesaudit.export, which auditors and admins hold. - A developer sees only the entries for their own actions, and so does a custom role based on Developer. Everyone else with
audit.readsees everyone's. Viewers have no access to the audit log.
Walk through it#
Read the event feed first
Open Events. Use the tabs for All, Flags, Releases, Security or Configuration, search by person or item, or pick one event type. Events marked needs a look are the ones to read first, such as a failed release, a revoked key, a removed member, a deleted flag or an activated kill switch.
The Events feed. Each row is the event type in monospace, the audit action as the summary, the actor, the environment and a short request ID. Warning events carry a needs a look badge and an amber dot. Event categories Tab Description Flags Flag creation and every kind of change ( flag.changed), archive and restore, deletes, kill switch activated and lifted.Releases Proposed, approved, rejected, cancelled, step applied, completed, failed, and rollbacks. Security API keys, members and invitations, passwords, roles, and exports of the audit log and configuration. Configuration Projects, environments, segments, alert rules and the organization itself. Open the audit log for the exact record
Open Audit Logs. Filter by type (the kind of thing changed, such as flag, member or API key), by action (grouped in a list) or by time range (Any time, Last 24 hours, Last 7 days, Last 30 days or Custom range), or search by person or item. Open an entry to see the Before and After values, the event ID, the request ID, the IP address and the client.
Several audit actions can be one event type. Every kind of flag edit is a
flag.changedevent, and the audit entry says what changed exactly:flag.toggled,rollout.updated,targeting.updatedand so on.The Audit Logs page with its three filters and one entry opened. Export CSV and JSON appear only for roles that hold audit.export. You should see. The list shows newest first with the time, actor, action and item, and expands to show the before and after values.Follow one change across systems
Every Dashboard API response carries an
X-Request-Idheader. The same ID is on the audit entry and in the server logs, so you can go from an error report to the exact entry, or from an entry to the logs.Export a copy
On the audit log page, choose Export CSV or JSON. The export uses your current filters, newest first, and is named
audit-log-YYYY-MM-DD. It stops at 10,000 rows, and the console tells you when the limit cut it short, so narrow the time range for long periods. Each export is itself recorded asaudit.exported.The columns are
createdAt,action,resourceType,resourceId,resourceName,projectId,environment,actorType,actorEmail,ipAddress,requestId,previousValueandnewValue. In the CSV, a cell that starts with=,+,-or@gets a leading apostrophe so a spreadsheet does not run it as a formula.
What the log promises
Do it with the API
Filters are resourceType, action, search (up to 100 characters), from, to, page and limit (default 25, maximum 100). GET /api/events takes category (flags, releases, security or configuration) and type instead of action and needs audit.read. The export response carries X-Export-Rows and X-Export-Truncated headers. See the Audit, events and metrics API.
# The Dashboard API acts as a signed-in person: POST /api/auth/login first (keep the cookie).
# Needs audit.read. Entries for one action in a time window ("to" is not included).
curl -s -b jar.txt -G https://flags.example.com/api/audit-logs \
--data-urlencode "action=member.role_changed" \
--data-urlencode "from=2026-10-01T00:00:00Z" \
--data-urlencode "to=2026-10-04T00:00:00Z" \
--data-urlencode "limit=25"
# The same filters as a file (needs audit.export). format is csv or json.
curl -s -b jar.txt -o audit.csv \
"https://flags.example.com/api/audit-logs/export?format=csv&resourceType=member"{
"status": "success",
"message": "OK",
"data": {
"items": [
{
"id": "log_123",
"action": "member.role_changed",
"resourceType": "member",
"resourceId": "USER_ID",
"resourceName": "ada@example.com",
"projectId": null,
"environment": null,
"actorType": "user",
"actorEmail": "you@example.com",
"previousValue": { "role": "Developer" },
"newValue": { "role": "Release manager" },
"ipAddress": "203.0.113.7",
"userAgent": "Mozilla/5.0",
"requestId": "req_abc123",
"createdAt": "2026-10-03T09:30:00.000Z"
}
],
"pagination": { "page": 1, "limit": 25, "total": 1, "totalPages": 1, "hasNext": false, "hasPrev": false }
}
}Good to know#
Limits today
Search by the item, not the verb
What is the difference between an event and an audit entry?
Does the log record what API keys do?
Can I filter an export by date?
from and to on the export endpoint. from is included and to is not.Why can a developer not see my change?
If something goes wrong#
The Audit Logs page is empty or shows only a few entries
Why: A filter is active, or you hold the Developer role (or a custom role based on it) and see only your own entries.
Fix: Clear the filters. If you need everyone's entries, ask for the Auditor or another role that can see them.
The page says Changes you made. Auditors and administrators can see everyone's.
Why: You hold the Developer role, which shows only your own entries.
Fix: Ask for the Auditor role, or a custom role based on something other than Developer.
There is no Export button
Why: Your role does not hold audit.export. Auditors and admins do.
Fix: Ask an admin to export, or to give you a role with the permission.
Export stopped at the row limit
Why: The export is capped at 10,000 rows.
Fix: Narrow the time range and export in pieces.
The CSV shows a leading apostrophe on some cells
Why: Cells that start with =, +, - or @ are prefixed so a spreadsheet does not run them as formulas.
Fix: This is intended. Remove the apostrophe if you need the raw value, or use the JSON export.
An API call returns 400 about from or to
Why: The dates are not valid, for example a missing time zone or a typo.
Fix: Send ISO date-times such as 2026-10-01T00:00:00Z.
What to check#
- Change a flag, then find the
flag.changedevent and its audit entry with your name on it. - Export a short range and confirm the file holds only the rows you filtered to.
- Sign in as a developer, or ask one, and confirm they see only their own entries.