> ## Documentation Index
> Fetch the complete documentation index at: https://to11.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit Logs

> Review who changed what in a project and in your organization, and export the record.

to11 keeps two audit logs. Each entry records the actor, the change, and when it happened, so you can answer "who changed this, and when?" after the fact.

| Log | Scope | Records | Opened from |
| - | - | - | - |
| **Audit log** | One project | Changes to the project's prompts and skills, its environments, and the project itself | **Settings → Audit log**, under **Project** |
| **Admin audit** | The organization | Changes to members' roles, invitations, workspaces, API keys, the GitHub and Slack integrations, and which project a GitHub repository belongs to | **Settings → Admin audit**, under **Organization** |

> [!NOTE]
>
> 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](https://to11.ai/docs/help/support.md). 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**

Reading the project audit log needs the `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 the `org_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 needs `audit:export`, which owners and admins hold. Exporting the admin log needs `org_audit:export`.

## Next steps

> [card] [Roles & permissions](https://to11.ai/docs/platform/roles-and-permissions.md)
>
> Who can view and export the audit logs.

> [card] [API keys](https://to11.ai/docs/platform/api-keys.md)
>
> Give a key the admin audit scopes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.