# Audit log

The Audit Log provides a comprehensive timeline of all activities and changes made within your Secoda workspace. This feature helps you track user actions, monitor changes, and maintain accountability across your data documentation.

### Overview

The Audit Log captures various types of activities including: resource updates, permission changes, documentation updates, role assignments, among other activities.

<figure><img src="https://secoda-public-media-assets.s3.amazonaws.com/304693e4-adea-49c4-9a12-90e393db682f.png" alt=""><figcaption></figcaption></figure>

### Accessing the Audit Log

1. Navigate to Settings in your Secoda workspace
2. Select "Audit log" from the left sidebar
3. View the chronological timeline of all workspace activities
4. Filter entries by user, date, log type, and resource

### Understanding Log Entries

Each log entry contains:

* Timestamp of the action
* User who performed the action
* Type of action performed
* Affected resource

### Best Practices

1. **Regular Auditing**: Review the Audit Log periodically to monitor workspace changes
2. **Change Management**: Use the log to track and verify planned changes
3. **Compliance**: Maintain records of sensitive data access and modifications
4. **Troubleshooting**: Reference the log when investigating unexpected changes

### Permissions

Only workspace administrators and users with appropriate permissions can access the Audit Log. This ensures security and maintains the integrity of audit records.


---

# 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://docs.secoda.co/features/audit-log.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.
