The audit log pages are being rolled out. If Audit log or Admin audit is missing from your settings sidebar, they are not enabled for your organization yet; contact us. Events are recorded either way.
The project audit log
Entries are listed newest first, and each one opens to show the full detail of the change, including the state before and after it. Filter the feed by:- Resource type, such as prompt or environment, and event type
- Actor, the person, API key, or automated process that made the change, and actor type
- Environment
- Time range
audit:read permission on the project. These permissions are for people only and cannot be given to an API key.
The admin audit log
The admin audit log covers organization-level administration. Filter it by resource type, event type, workspace, and actor. Reading it needs theorg_audit:read permission at the organization level. Unlike the project log, it can also be read by an API key that carries the org_audit:read scope, for example to feed a SIEM or a compliance archive.
Exporting
Both logs export the events that match the current filters as CSV or JSON. The CSV export has one row per event with the actor, resource, event type, and timing columns; the JSON export also includes the full before and after state of each change. A single export is capped at 50,000 rows. If your selection is larger, narrow the filters by time range, resource type, or actor and export again. Exporting the project log needsaudit:export, which owners and admins hold. Exporting the admin log needs org_audit:export.
Next steps
Roles & permissions
Who can view and export the audit logs.
API keys
Give a key the admin audit scopes.