> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/administration/audit-log.md).
# Audit Log
The Audit Log gives you a searchable record of actions taken in Material, such as viewing messages, issues, and files. To open it, from the top toolbar, click **Audit Log**. From here, you can drill down into individual events. To review message access or force unlock requests, from the left navigation expand **Email Redaction**, then click **Message Access Log** or **Force Unlock Requests**.
Actions logged include detection lifecycle events such as `detection_disabled`, which is recorded whenever a detection is turned off, whether by an admin or by the automatic circuit breaker.
To subscribe or create alerts for various audit log events, create an [**Event Subscription**](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/set-up-a-notification.md).
---
# 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.material.security/administration/audit-log.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.
