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

# Audit log

Every sign-in, setting change and data action in your workspace, with who did it, from where and when.

Every sign-in, setting change and data action in your workspace: who did it, from where and when. Available on Enterprise.

{% embed url="<https://app.screendesk.io/recordings/a9637022-6fcb-48d5-b250-2caeaf67b464>" %}

Open **Settings → Audit log**:

* **Events**: filter the list and click an event for details. **Export** saves it as CSV or JSON, up to 10,000 events at a time. Entries are kept for 365 days; click **Change** to keep them from 30 days to 7 years.
* **Access review**: every member with their roles and last sign-in. Approve each one or flag it for follow-up, then export it for your auditor.
* **SIEM webhooks**: send events to your security tools as they happen. See [SIEM webhooks](https://docs.screendesk.io/security/audit-logs/webhooks-and-siem-delivery.md).

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FNHXh93D3Y0uV1rxv9ZVx%2Fdocs-panel-audit.png?alt=media" alt="Settings, Audit log, Events"><figcaption></figcaption></figure>

Entries can't be edited or deleted. [Integrity and event reference](https://docs.screendesk.io/security/audit-logs/integrity-and-event-reference.md) lists every event.


---

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