Launch Week 02 wrapped — explore all five launches

Project Audit Logs

View a log of all actions performed in your project.

Included on the Enterprise plan. Book a demo, opens in a new tab. Included on the Team plan. Not included on the Starter plan. Not included on the Free plan.

Audit logs provide a chronological record of every action performed in your project, helping you track changes, debug issues, and maintain accountability.

Project Audit Logs

Overview

The audit logs page shows all API and user actions that have occurred in the project. Each log entry includes:

ColumnDescription
DateTimestamp of the action (UTC).
StatusHTTP status code returned by the action (e.g., 200 for success).
LogsThe action performed, shown as a method and resource path (e.g., PUT client.prompts.update).
UserThe email of the user or API key that triggered the action.

A timeline chart at the top visualizes action volume over time, making it easy to spot spikes or unusual activity.

Need audit logs for compliance review?Give security and compliance teams the visibility they expectTalk to us

Searching Logs

Use the search bar to filter logs by any field — action name, user email, status code, or resource path. This is useful for narrowing down specific changes, such as finding all retention config updates or actions by a particular user.

Exporting Logs

Click Save as CSV to export audit logs. Choose Current view to export what the viewer is showing, or All time to export every audit log ever recorded for this project — the dialog shows the exact row count and date range before you commit.

Small exports download immediately. Larger ones are prepared in the background: a card appears on this page showing progress, you receive an email when the file is ready, and the Download CSV button gives you the finished file (a gzipped CSV). Download links are generated fresh each time you click and expire after 15 minutes.

Only organization Owners and Admins can export audit logs. One export runs at a time.

You can also do this programmatically — see Create Project Audit Log Export.

Common Actions

Actions follow a resource.action naming pattern. Some examples:

  • client.retention-configs.inherit.update — Updated the inherit-from-organization retention setting
  • client.retention-configs.retention-policies.create — Created a retention policy
  • client.rt-frameworks.schedule.create / delete — Created or deleted a real-time framework schedule
  • client.prompts.update — Updated a prompt

Last updated on

Built byConfident AI