> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/security/audit-logging.md).

# Audit logging

Keep track of events occurring in your workspace for real-time management and monitoring.

### Overview

Audit logging provides comprehensive tracking of all actions taken within your workspace. This feature is available on an opt-in basis for enterprise customers and can be enabled per workspace.

### Accessing Audit Logs

Once enabled for your workspace, audit logs are accessible through the Enterprise section of the application: go to **Settings > Enterprise** and select **View Audit Logs**. The portal provides a searchable interface where you can:

* View all logged events in chronological order
* Filter by action type (e.g., file operations, user management, workspace changes)
* Filter by user who performed the action
* Filter by timestamp or date range
* View detailed information about each event

### Streaming Audit Logs to a SIEM

In addition to viewing and exporting logs from the portal, Enterprise workspaces can stream audit log events to a SIEM or other supported destination. Go to **Settings > Enterprise > Audit Log Streaming** to set up a stream. For more details, see [SIEM integration](https://academy.shade.inc/help-center/security/shade-siem-documentation.md)

### What Gets Logged

Our audit logging captures authenticated user actions across the platform. Every single request made to your workspace (whether it be through the app, web, mount, or api), including read-only requests such as viewing or listing files, is captured by our logging system and stored with our audit log provider, WorkOS. Each log entry includes:

* **Action**: The specific operation performed (e.g., file upload, permission change)
* **Actor**: The user who performed the action, including their IP address
* **Targets**: The resources affected by the action (files, folders, users, etc.)
* **Timestamp**: When the action occurred
* **Workspace context**: The workspace where the action took place

### What Doesn't Get Logged

To maintain performance and focus on security-relevant events, we exclude:

* Internal system operations
* Authentication token refreshes
* Unauthenticated requests
* A small set of routine background lookups (for example, listing your workspaces or looking up a workspace from its URL)

### Security & Privacy

* Audit logs are isolated per organization
* Only authenticated actions within your workspace are logged
* Logs are retained according to your enterprise agreement
* Access to audit logs is restricted to workspace administrators

### Enabling Audit Logging

Audit logging is enabled by our team at the workspace level. Contact your account representative to activate this feature for your organization.

***

For questions about audit logging or to request activation, please reach out to your account manager or contact enterprise support.


---

# 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://academy.shade.inc/help-center/security/audit-logging.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.
