> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/security/audit-logs/view-and-filter-audit-logs.md).
# View and filter audit logs
Browse audit events, open event details, and narrow results using filters.
Audit logs are listed in chronological order. Open any event to see full details.
### View audit logs
{% stepper %}
{% step %}
### Open audit logs
Go to **Account Settings → Security → Audit logs**.
{% endstep %}
{% step %}
### Browse events
Events are shown newest first. Scroll to load more.
{% endstep %}
{% step %}
### Open event details
Click an entry to see full context.
{% endstep %}
{% endstepper %}
### What’s included in an event
Each entry can include:
* User
* Action (event type)
* Timestamp
* Status (**success**, **failure**, **denied**)
* IP address and device info
* Before/after values (when something changes)
### Filter logs
Use filters to narrow results:
* **Category** (authentication, data access, etc.)
* **Event type** (for example `user.login`, `recording.deleted`)
* **User**
* **Severity** (Low, Medium, High, Critical)
* **Status** (Success, Failure, Denied)
* **Date range**
* **Search** (IP address, event type)
{% hint style="info" %}
If you plan to export, apply a date range first. It keeps exports fast and under the row limit.
{% endhint %}
---
# 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.screendesk.io/security/audit-logs/view-and-filter-audit-logs.md?ask=&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.
