> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/saas/govern/detect-introduction.md).

# Access and Activity

Learn how Immuta audit logs, dashboards, and notifications help you monitor data access

Immuta continually monitors your data environment to help answer questions about your most active data users, the most accessed data, and the events happening within your data environment. This understanding can help drive prioritization of where to place access control policies.

## Why audit data access

Organizations managing sensitive data need to show how access is granted, who used it, and whether it was appropriate. Immuta audit logs provide your organization with the following:

* **Technical transparency** into how access is granted and enforced.
* **Operational accountability** to trace decisions and user behavior back to the person or process responsible.
* **Regulatory evidence** to meet compliance obligations under frameworks like HIPAA, GDPR, and CCPA.

## How it works

Immuta captures two kinds of audit events in a consistent format, the universal audit model (UAM):

* **Application events**: Actions taken in Immuta, like policy changes, tag changes, and access approvals
* **Query events**: Queries users run against governed data in supported platforms.

You can use these events in three ways:

1. **Audit**: Search events on the audit page, or export them to S3 or ADLS Gen2 for long-term storage and analysis.
2. **Dashboards**: View data source activity by time frame, most active data sources and users, queries over time, and sensitive data indicators. Each column is assigned a sensitivity level based on its classification under your data security framework and the mitigations applied to the user querying it.
3. **Notifications**: Send email notifications or webhooks when specific events occur.

## Access changes without policy changes

Immuta policies are dynamic and metadata-driven, so a user's access can change even when no one edits a policy. For example, a policy grants access to tables tagged `business.marketing` to users with the attribute `department=marketing`. If a user is given that attribute, or a table is given that tag, the user gains access without any change to the policy itself.

The audit logs record these indirect changes as `AttributeApplied` and `TagApplied` events. When investigating why a user's access changed, review attribute, group, and tag events alongside policy events.

### Current access vs. access history

Audit logs are a chronological record of the actions that led to access. To see what users can access right now and why, use [Comply](https://documentation.immuta.com/saas/comply/introduction.md). Comply is built on the access summary export, a point-in-time snapshot of current access, and shows which policies, tags, requests, groups, or attributes determine each user's access. Use Comply for questions like "Who has access to sensitive customer data?" and audit logs for questions like "When did this user gain access, and who made the change?"

{% hint style="info" %}
**Private preview**: Comply is in private preview and available to select accounts.
{% endhint %}

## Choose between dashboards and notifications

Not every event needs an alert. In general, use dashboards to observe trends and support audits, and use notifications for events that require a decision or response.

| Use case                                                   | Recommended approach |
| ---------------------------------------------------------- | -------------------- |
| Track policy edits over time                               | Dashboard            |
| Review access grants and removals weekly                   | Dashboard            |
| Catch permissions or attributes applied manually in Immuta | Notification         |
| Track changes to Immuta permissions                        | Notification         |
| Detect query spikes on sensitive data                      | Dashboard            |

## Questions Immuta can answer

* What data access activity took place in the last 24 hours?
* Who accessed sensitive data, and what sensitive data was accessed?
* What are the most trafficked data sources containing sensitive data?
* Which users were most active in accessing sensitive data?
* How do I quantify, assess, and show my organization's data security posture?
* How can I stay aware of data security posture changes?

To find the audit events that answer specific governance questions, see [Events for common audit questions](https://documentation.immuta.com/saas/govern/detect-introduction/index.md#events-for-common-audit-questions).


---

# 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://documentation.immuta.com/saas/govern/detect-introduction.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.
