> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/access-and-sharing/audit-logs-privacy-and-security/review-the-audit-trail.md).

# Review the audit trail

See what your users are doing.

Use the audit trail to inspect available activity in the app.

## Find activity

1. Open **More → Audit trail**.
2. On the **Activity trail** page, set the date and time range.
3. Use **All Users** to narrow the actor.
4. Use **All Activities** to narrow the event type.
5. Review the matching rows and use pagination for more results.

![Activity trail date-range, All Users, and All Activities filters](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F4CF1HCT2BsBg9DG2BUZg%2F08-audit-filters.png?alt=media)

## Read a row

| Column   | What to inspect                                                                               |
| -------- | --------------------------------------------------------------------------------------------- |
| Date     | The recorded event time. Confirm the displayed timezone when correlating with another system. |
| User     | The actor shown for the event.                                                                |
| Activity | The event type.                                                                               |
| Details  | Available context, such as a resource or collection identifier.                               |

The activity selector includes event types for resources, collections, records, API tokens, backups, and codebase changes. Availability in the selector does not establish that every operation in every connected system is logged.

## Verify coverage for your use case

Perform a permitted test action on synthetic data, then check whether and how it appears. Confirm the event scope and retention before using the trail as an audit control.

For errors, switch to [System logs](/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md). For an unexpected access change, compare the activity with [the intended access policy](/access-and-sharing/overview/test-access.md) and the actual user experience.


---

# 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.jetadmin.io/access-and-sharing/audit-logs-privacy-and-security/review-the-audit-trail.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.