# What audit logs do not show

The audit log tells you who did what and when. It does not store a full record of every change. Several common questions are not covered.

## No before and after values

Each entry stores only the action type, the user, and the time. It does not record what specifically changed.

So a settings-change entry tells you that a user changed something in settings at a certain time. It does not tell you which setting changed, or what the old and new values were.

If you suspect a specific change was made:

* Check what the setting is set to now.
* Compare the audit-log time against who was using the dashboard then.
* Ask the user what they changed.

## No undo or rollback

There is no undo button and no revert action. The audit log records that a change happened. It does not keep the previous state to restore.

What you can do instead:

* Set the affected setting back by hand.
* Restore a panel from a saved [template](/docs/panels/templates.md) if you have one.

## No record of views

Opening the dashboard or viewing a page does not create an audit entry. Only changes are recorded. There is no way to see who has only looked at your server's settings.

## No ticket message content

The audit log does not record what was said inside tickets. That content is in the transcript of the closed ticket. Transcripts are not edited or deleted, so they act as a separate record of ticket content.

* For what was said in a ticket, open the **transcript** of the closed ticket.
* For who closed, claimed, or transferred a ticket, the audit log records that.

## Some actions are not audited

The audit log does not record these:

* A member opening a ticket. The Opened Tickets Log Channel records that instead.
* A member sending a message in a ticket. The transcript records that.
* A member leaving the server. Discord's own audit log records that.
* Releasing a claim with /unclaim.
* Linking or unlinking a Steam account.
* Redeeming top.gg votes.
* Premium purchases.

For these, look at the relevant log channel, the transcript, or Discord's own audit log.

## No IP or device data

Audit entries identify the user by their Discord user ID only. There is no IP address logging and no device information.

## Working with these limits

When you give someone outside your staff team a hand with your dashboard, use Temporary Dashboard Access instead of a shared login. Their actions then show up under a clear identity in the audit log.

## Related

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

{% content-ref url="/pages/rnAynQ0SgRUc1zHeRvJO" %}
[Temporary Dashboard Access](/docs/permissions-and-your-support-team/temporary-dashboard-access.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/audit-logs/what-it-doesnt-show.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.