> 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/what-it-captures.md).

# What the audit log captures

The audit log records meaningful actions taken in your dashboard and via the bot.

The audit log records actions taken on your server. Open it from **Dashboard, Audit Logs**. The audit log is free.

## What kinds of actions

* **Settings changes.** Any edit to your server settings, and resetting ticket counters.
* **Panels.** Creating, editing, moving, resending, and deleting a panel.
* **Templates.** Creating and deleting a template, creating and deleting a template share code, and importing a template with a code.
* **Custom commands.** Creating, editing, and deleting a custom command.
* **Tickets.** Claiming, transferring, and closing a ticket.
* **Applications.** A member submitting an application, and approving or denying one.
* **Temporary dashboard access.** Creating, claiming, and revoking a temporary access link.
* **Bot Personalizer.** Updating the Bot Personalizer settings.
* **Premium.** Accepting a premium qualification.

## What is stored per entry

Each entry records the action type, the time it happened, the user who did it, and which server it was on.

That is all. The audit log answers **who did what, and when**. It does not record which exact value changed from one setting to another. If you need to keep a record of a configuration before a risky edit, write it down or save a template first.

## What is not logged

* Opening the dashboard or viewing a page is not logged. Only changes are.
* Ticket message content is not in the audit log. That is in the transcript.
* A member opening a ticket is not an audit event. The Opened Tickets Log Channel records that instead.

## How long entries are kept

Indefinitely. There is no expiry on audit-log entries.

## Related

{% content-ref url="/pages/CbEOzkpHIFCEilUhS929" %}
[Reading the page](https://ticketking.xyz/docs/audit-logs/reading-the-page.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/what-it-captures.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.
