> 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.md).

# Audit trail and system logs

Choose the log view that matches the question you are investigating.

| View                                                                                          | Open it from       | Use it for                                                           |
| --------------------------------------------------------------------------------------------- | ------------------ | -------------------------------------------------------------------- |
| [Audit trail](/access-and-sharing/audit-logs-privacy-and-security/review-the-audit-trail.md)  | More → Audit trail | Review available activity by date, user, and activity type.          |
| [System logs](/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md) | More → System logs | Investigate system or integration messages using filters and search. |

The Audit trail navigation item opens a page headed **Activity trail**. System logs is a separate view.

## Investigate a reported problem

Record the app, environment, time, affected user, and symptom. Start with the relevant view, narrow the filters, and compare the event or message with the action the user reports.

An absent entry can have several causes, including the selected filters, event coverage, or retention. Do not interpret an empty view as proof that an action never occurred.

Confirm available event coverage, retention, and any export requirements for your deployment before relying on these views for a formal audit. See [Security and data handling](/access-and-sharing/data-privacy-and-security.md) for handling diagnostic information.


---

# 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.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.