> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/managing-teams/audit-log.md).

# Audit Log

The administration events that PixieBrix records for your team, and what each field means

The Audit Log records administration changes that team Admins and Managers make to your team, such as changes to members, groups, deployments, and integration configurations. Each entry shows who made the change, what changed, and when.

The Audit Log records administration changes only. It does not record sign-ins or the activity of team members who use mods.

### Viewing the Audit Log

You must have the Admin or Manager role to view the Audit Log.

* **Team:** Go to `https://app.pixiebrix.com/teams/<team ID>/audit/`. To find your team ID, open your team in the [Admin Console](https://app.pixiebrix.com/). The team ID is the part of the URL after `/teams/`.
* **Group:** In the [Admin Console](https://app.pixiebrix.com/), open the group, then click the Audit Log tab.
* **Deployment:** In the [Admin Console](https://app.pixiebrix.com/), open the deployment, then click the Audit Log tab.

{% hint style="warning" %}
The team Audit Log page can show a maximum of 1,000 events. If your team has more than 1,000 events, the page shows an error. To get all the events, use the API with pagination. See [Team Management APIs](/developer-api/team-management-apis.md).
{% endhint %}

{% hint style="info" %}
When you delete a group or a deployment, you cannot open its Audit Log tab. Past events for it stay in the team Audit Log.
{% endhint %}

### Recorded actions

The `action_type` field identifies the action.

| Action type                                                                                             | Recorded when                                                                                                    |
| ------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| `organization.create`, `organization.update`                                                            | A team is created, or the team settings change                                                                   |
| `organization.memberships.create`, `organization.memberships.update`, `organization.memberships.delete` | A member is added to the team, the role of a member changes, or a member is removed from the team                |
| `group.create`, `group.update`                                                                          | A group is created, or the name of a group changes                                                               |
| `group.memberships.create`, `group.memberships.delete`                                                  | A member is added to a group, or a member is removed from a group                                                |
| `group.packages.create`, `group.packages.update`, `group.packages.delete`                               | Group access to a mod is given, changed, or removed                                                              |
| `group.integrations.create`, `group.integrations.update`, `group.integrations.delete`                   | Group access to an integration configuration is given, changed, or removed                                       |
| `deployment.create`, `deployment.update`                                                                | A deployment is created, or the deployment changes (version, active or paused, options, integrations, platforms) |
| `deployment.groups.create`, `deployment.groups.update`, `deployment.groups.delete`                      | A group is assigned to a deployment, or a group is removed from a deployment                                     |
| `integrations.create`, `integrations.update`                                                            | A team integration configuration is created or changes                                                           |
| `control_room.create`, `control_room.delete`                                                            | An Automation Anywhere Control Room is connected or removed                                                      |

### Fields

#### Event

| Field         | Description                                                       |
| ------------- | ----------------------------------------------------------------- |
| `id`          | The unique ID of the audit event                                  |
| `action_type` | The action. See [#recorded-actions](#recorded-actions "mention"). |
| `timestamp`   | The date and time of the change, in UTC (ISO 8601 format)         |

#### Actor

The `actor` object identifies the user who made the change.

| Field                          | Description                                                          |
| ------------------------------ | -------------------------------------------------------------------- |
| `actor.id`                     | The ID of the user                                                   |
| `actor.name`                   | The full name of the user                                            |
| `actor.email`                  | The email address of the user                                        |
| `actor.service_account`        | `true` if the change was made with a team API service account        |
| `actor.deployment_key_account` | `true` if the change was made with a deployment key account          |
| `actor.date_joined`            | The date and time that the PixieBrix account of the user was created |

#### Target object and action object

The `target_object` is the main item that changed, for example a team, group, or deployment.

The `action_object` is a second item in the change, if there is one. For example, when a member is added to a group, the `target_object` is the group and the `action_object` is the member. If the change has only one item, `action_object` is `null`.

Both objects have the same fields:

| Field          | Description                                                                                                                      |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `id`           | The ID of the item                                                                                                               |
| `content_type` | The type of item, for example `organization`, `group`, `package deployment`, or `service credential` (integration configuration) |
| `label`        | The name of the item. For a user, the label is the email address.                                                                |

#### Data

The `data` object shows the details of the change. The fields in `data` change with the action type.

| Field                             | Action types                                | Description                                                                                                       |
| --------------------------------- | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| `data.name`                       | `organization.*`, `group.*`, `deployment.*` | The name of the team, group, or deployment                                                                        |
| `data.scope`                      | `organization.*`                            | The scope of the team (the `@name` prefix for team mods)                                                          |
| `data.default_role`               | `organization.*`                            | The role that new team members get                                                                                |
| `data.enforce_update_millis`      | `organization.*`                            | The time, in milliseconds, that members have to apply a deployment or browser extension update. Empty if not set. |
| `data.role`                       | `organization.memberships.*`                | The team role of the member: Member, Developer, Restricted, Manager, or Admin                                     |
| `data.permission`                 | `group.packages.*`, `group.integrations.*`  | The access level of the group: Read or Write                                                                      |
| `data.mod`                        | `deployment.*`                              | The registry ID of the deployed mod                                                                               |
| `data.version`                    | `deployment.*`                              | The deployed mod version                                                                                          |
| `data.active`                     | `deployment.*`                              | `true` if the deployment is active, `false` if the deployment is paused                                           |
| `data.platforms`                  | `deployment.*`                              | The platforms of the deployment                                                                                   |
| `data.options_config`             | `deployment.*`                              | The mod option values of the deployment                                                                           |
| `data.integration_configurations` | `deployment.*`                              | The IDs of the integration configurations that the deployment uses                                                |
| `data.url`                        | `control_room.*`                            | The URL of the Control Room                                                                                       |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pixiebrix.com/managing-teams/audit-log.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.