> For the complete documentation index, see [llms.txt](https://docs.countercyclical.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.countercyclical.io/workspace-settings/audit-logs.md).

# Audit Logs

Monitor workspace security, access, and resource activity from a centralized event history.

Audit Logs provide a chronological record of activity across the workspace. Use them for security investigations, compliance reviews, administrative oversight, and understanding changes to workspace resources.

See also [Event Streaming](https://docs.countercyclical.io/workspace-settings/event-streaming) and [Data Retention](https://docs.countercyclical.io/workspace-settings/data-retention).

Access Audit Logs from [**Settings › Security › Audit Logs**](https://dashboard.countercyclical.io/settings/workspace/security/logs).

### Reviewing Audit Events

The **All Logs** view displays recorded workspace events. Each entry summarizes the actor, action, affected resource, client or device information, and when the event occurred.

Select **Log Details** beneath an event to expand its underlying structured record. Depending on the event, these details can include the action, actor information, client and browser metadata, resource information, permissions, and other event-specific fields.

The **Action Taken** view can be used to focus on events representing actions recorded by the audit system.

### Filtering Audit Logs

Use **Filter** to narrow the audit trail to events relevant to an investigation or review. Available properties include:

* **Action** — the operation recorded by the event.
* **Resource** — the workspace resource associated with the event.
* **Actor** — the account responsible for the activity.
* **Permission** — permission information associated with the event.
* **Device Type** — the type of device used.
* **Browser** — the browser associated with the event.
* **IP Address** — the network address recorded for the event.
* **Resource ID** — the identifier of the affected resource.
* **Occurred Date** — when the event occurred.

**Advanced Filters** can be used when a review requires more specific filtering criteria.

You can also open the **⋮** menu on an individual event to quickly filter the audit trail using metadata from that event, such as its account, permission, action, resource, device type, or browser. This is useful when investigating related activity without manually reconstructing a filter.

### Searching and Saving Filters

Use **Search Audit Logs** to locate relevant events directly.

For investigations or compliance reviews you expect to repeat, configure the required filters and select **Save Filter**. Saved configurations can then be reopened from **View Saved Filters**, reducing the need to recreate common audit queries.

### Exporting Audit Logs

Select **Export Logs** to download the events matching the current audit-log query. The interface indicates the number of matching events before export and notes that some fields may be redacted.

Available export formats are:

* **Portable ZIP (.zip)** — archive containing JSON, CSV, a manifest, and redaction notes.
* **Excel Workbook (.xlsx)** — workbook containing a manifest and normalized audit-event sheets.
* **JSON Archive (.json)** — structured event archive with export and security metadata.
* **CSV File (.csv)** — flat, formula-safe audit-event data suitable for spreadsheet or warehouse import.

Apply filters before exporting when you only need a particular period, actor, resource, or class of activity. This produces a more focused dataset for investigations and compliance workflows.

### Audit-Log Retention

Audit Logs are subject to the workspace's configured retention policy. Workspace administrators can configure how long audit evidence is retained from [**Settings › Security › Data Retention**](https://dashboard.countercyclical.io/settings/workspace/security/retention).

If audit records need to remain available for regulatory, contractual, litigation, or internal-control purposes, configure the applicable retention period before relying on the audit trail as a long-term system of record.

#### Related Pages

{% content-ref url="/pages/bup2j5bp4vbFRZVuXBU8" %}
[Data Retention](https://docs.countercyclical.io/workspace-settings/data-retention.md)
{% endcontent-ref %}

{% content-ref url="/pages/Ulklm2wIU87fg6nLtwXV" %}
[Event Streaming](https://docs.countercyclical.io/workspace-settings/event-streaming.md)
{% endcontent-ref %}

{% content-ref url="/pages/ObHijOsTzeI28I0ANBYA" %}
[Usage Analytics](https://docs.countercyclical.io/workspace-settings/usage-analytics.md)
{% endcontent-ref %}
