# Audit Logs

### What are Audit Logs?

Audit Logs allow you to see a detailed history of user-driven actions performed within DinMo. For instance, if an unexpected issue occurs in your workspace—such as incorrect data being sent to a destination—admins can review the logs to identify and correct the root cause. This promotes **operational clarity** and helps **enforce best practices**.

### Viewing Audit Logs

Workspace admins can view audit logs by navigating to the *Audit Logs* tab in the *Settings* page. The logs are displayed in a table format, with the most recent actions shown at the top. Each log entry includes:

* **Date and Time**: The timestamp of the action, displayed in the viewer’s local timezone.
* **Action Name**: The type of action performed (e.g., "Segment updated").
* **Resource Name**: The specific name of the resource that was affected.
* **User**: The individual who performed the action.

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FdKupTWecM5WUC8VF2Nfx%2Fimage.png?alt=media&#x26;token=a5633f8c-54a7-4ac3-a3e1-fd2ec3607677" alt=""><figcaption></figcaption></figure>

### Filtering Audit Logs

To make it easier to find specific actions, Audit Logs can be filtered by:

* **User**: Filter by one or multiple users who performed the actions.
* **Resource Type**: Narrow down the logs to specific resource types (e.g., only Destinations or Models).
* **Resource Name**: Search for actions related to a specific resource by name.
* **Date Range**: Focus on actions performed within a specific timeframe.

You can combine multiple filters to drill down into the exact information you need.

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2F2ZfD5yQEcClYQZBsfqSL%2FCapture%20d%E2%80%99e%CC%81cran%202025-01-28%20a%CC%80%2009.46.11.png?alt=media&#x26;token=c45b4086-86e3-4e8f-b344-8f7bb82157a0" alt=""><figcaption><p>Audit Logs - Filter to the level of information needed to find the information you need</p></figcaption></figure>

### Examples of Use Cases:

* Ensure team members **only edit their own segments** by reviewing the creator and last editor of each resource.
* **Troubleshooting**: Identify misconfigured connections by tracking who created or updated a specific source or destination.
* **Compliance**: Maintain a complete record of changes for audits or internal reviews.