# Audit

The Audit page provides a centralized log of important changes in your organization, including changes made through JetBrains Central Console. You can review changes and see who made them, when they happened, and whether they succeeded. You can also export the log for further analysis.

An action appears in the log even if it was rejected or failed. Read-only actions, such as viewing a resource, don't appear at all.

The audit log doesn't show how AI is used in your organization. For usage and adoption metrics, see [AI adoption and usage](ai-adoption-and-usage.html). For details of individual AI sessions, see [Session explorer](session-explorer.html).

Once an event is recorded, it can't be edited or deleted in JetBrains Central Console.

> **Note:**
> Viewing and exporting the audit log requires the [Manage organization](roles.html#permissions_manage_org) permission.

## Event categories

The audit log covers the following categories of events:

* User management: adding, updating, or removing [users, groups, or service accounts](users-and-access.html), and changing group membership. When you change a user's group membership, the log records the change for that user. To view which group was affected, check the [event metadata](#view-event-details).

* Role assignments: assigning or unassigning a [role](roles.html) for a user, group, or service account. When you change roles for several users, groups, or service accounts at once, the log records a separate event for each of them.

* AI access management: enabling or disabling [AI access](ai-access.html) at the organization level, choosing whether it is [granted to everyone in the organization or manually per user or group](ai-settings.html#change-ai-access-settings), and granting or revoking it per user, group, or service account. Logging works as follows: * When you change AI access for several users, groups, or service accounts at once, the log records a separate event for each principal whose access changed. * When you enable or disable AI access for the entire organization, or change how it is granted, the log records a single event. Both changes appear under the same action in the log table and in the action filter. * When you revoke AI access granted to a user individually, the log records the change even if the user still has access through a group. * When you grant access to a user who already has it through a group, nothing changes, and nothing is logged. * When you change a group's AI access, the log records a single event for that group. Access is recalculated for each group member, but those changes are not logged separately.

* AI credit limit management: updating the [individual limit](manage-ai-credits.html#set-ai-credit-limits) of a user or service account, and the organization's [default AI credit limit](ai-settings.html#default-ai-credit-limit).

> **Note:**
> This list describes the events that are currently reported to the audit log, not everything that happens in your organization. Services report to the audit log independently, and more will start doing so over time, so events from other categories may also appear on the page. If a change isn't listed here, it might not be recorded yet.

## Browse and filter the audit log

The audit log is presented as a table of events. Each event is described by the following columns:

* Timestamp: When the event occurred.

* Principal: Who performed the action. It can be a user, a service account, or a JetBrains Central Console internal service. > **Note:** > Some changes are made automatically, for example, when a new organization member receives AI access. Such events are attributed to the internal service that performed them, and the service name is shown as the principal (for example, `ai-management`). Not all automatic changes are recorded, so the log doesn't include an event for every automatic change.

* Action: The type of action that was performed, shown as a technical identifier in the form `domain.entity.verb` (for example, `ai.user-access.granted`).

* Target: The entity that was affected by the action. The column shows the entity type and its name, for example, a user, a group, or the organization itself.

* Result: The outcome of the action. It can be one of the following: * Success: The action completed successfully. * Failure: The action did not complete because of an internal error. * Denied: The action was rejected because of insufficient permissions. * Pending: The action's outcome hasn't been recorded yet. * Blocked: The action was blocked by a policy rule.

> **Note:**
> The Principal and Target columns show current names, not the names used at the time of the event. If a name is unavailable, the log shows an ID instead.

The log table can be filtered by the following criteria:

* By the time the event occurred. Select a predefined time range or specify a custom date range. In the table, you can only select a date range within the last 90 days.

* By the principal who performed the action. Type a name and select one or more principals (users or service accounts). > **Note:** > Events performed by a JetBrains Central Console internal service cannot be filtered this way.

* By the action. Select one or more actions to include in the log. The list includes only the actions that have already occurred in your organization.

## View and export the audit log

Procedure: View event details

1. In the sidebar, select Audit.

If you don't see this page, your role doesn't have the necessary [permissions](roles.html#permissions).

2. Click a row in the audit log table to open the Event Details panel.

3. Review the event details, including its metadata. You can click a metadata value to copy it.

> **Note:**
> Metadata describes what changed, for example, the previous and new values of a setting. The metadata an event includes depends on the action, and some actions have no metadata at all.

Procedure: Export the audit log

1. In the sidebar, select Audit.

If you don't see this page, your role doesn't have the necessary [permissions](roles.html#permissions).

2. Click the Download button in the top-right corner.

3. In the export dialog, select a predefined time range or specify a custom date range for the events you want to export.

> **Note:**
> Unlike the audit log table, the export is not limited to the last 90 days. It is limited by the number of events instead: a single export can include up to 50,000 events. If your selection matches more, the export fails. In this case, narrow the date range or the other filters and export the log in several parts.

4. Select the principals and actions you want to include in the exported log.

To export the log for all principals and actions, leave these values unchanged.

5. Click Download.

The downloaded CSV file includes the audit log for the selected date range. You can use it for compliance reviews or further analysis. For each event, the file lists the timestamp, principal, action, target, and result, but not the event metadata. To see what changed, open the event in the Event Details panel.