> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/guided-redaction/redaction-project-audit-log.md).

# Viewing the audit log for a project

{% hint style="info" %}
**Required guided redaction permission:** View audit log
{% endhint %}

The audit log tracks the following actions associated with the project:

* Project is created
* Files are added or removed
* Project status changes
* File status changes
* Comments are added
* Files are exported

To display the audit log:

1. On the project details page, click **More**.
2. In the menu, click **Audit log**.

For each entry, the audit log includes the following information:

* When the action occurred.
* The email address of the user who performed the action.
* The type of action.
* A description of the action.


---

# 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.tonic.ai/textual/guided-redaction/redaction-project-audit-log.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.