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

# Reading the page

Filtering and reading the Audit Logs page.

The Audit Logs page is at **Dashboard, Audit Logs** in the sidebar. To open it you need the **View Audit Logs** dashboard permission, or be the server owner or have Discord Administrator or Manage Server.

Each entry shows the action, who did it, and when.

## Narrowing the list

You can filter the list three ways, and combine them:

* **By date.** Pick a preset range or set a custom date range.
* **By user.** Pick a recently active user, or type a user ID to see only one person's actions.
* **By event type.** Pick one or more action types. The list offers only the event types that have actually happened on your server, so you are never picking from actions you have never used.

This is how you answer questions like "what did this moderator change last week" or "who reset the ticket counters."

<figure><img src="https://1268186137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrnuG1qjzbOoh0efVpoK8%2Fuploads%2Fgit-blob-32f8e724dbc61fb6f437549e7321809f3f2caf43%2Faudit-logs-page.png?alt=media" alt="The Audit Logs page with the date and event-type filters set, and a table of audit entries below"><figcaption></figcaption></figure>

## Related

{% content-ref url="/pages/Nin30Dy0fPFzy7oflTml" %}
[What the audit log captures](https://ticketking.xyz/docs/audit-logs/what-it-captures.md)
{% endcontent-ref %}

{% content-ref url="/pages/LC5SJ1kQhcxNhXhwqsDc" %}
[What audit logs do not show](https://ticketking.xyz/docs/audit-logs/what-it-doesnt-show.md)
{% endcontent-ref %}


---

# 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://ticketking.xyz/docs/audit-logs/reading-the-page.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.
