> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/identities/identity-card/user-events.md).

# User events

All events triggered by the user in the last 30 days are displayed.

<div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FDdo1x05ZyxU0aeEuAfdO%2FIdentities%20events.png?alt=media&amp;token=2eadd40c-4148-4c62-bf61-bf608ed96fec" alt="" width="563"><figcaption><p>Events triggered by the user</p></figcaption></figure></div>

You can view user events, according to these parameters:

<table><thead><tr><th width="254">User event parameter</th><th>Description</th></tr></thead><tbody><tr><td>Date &#x26; time</td><td>The date and time when the event occurred</td></tr><tr><td>Actor</td><td>The user who triggered the event. Clicking the actor's email opens the user's profile.</td></tr><tr><td>Target</td><td><ul><li>The recipient of the event, or who the actor shared data with.</li><li>If the recipient is a Google email alias, the user's real email address is displayed.</li><li>Clicking the target's email opens the user's profile.</li></ul></td></tr><tr><td>App</td><td>The SaaS app involved in the event</td></tr><tr><td>Asset</td><td>The name of the asset involved. Clicking the link opens the Asset page.</td></tr><tr><td>Event type</td><td>User action as defined in the relevant SaaS app</td></tr><tr><td>Triggered</td><td>Number of workflows or alerts that were triggered by this event. Click the Workflows or Alerts icon to view the <a href="/docontrol-user-guide/saas-data-monitoring/events.md#triggered-entities">triggered entities</a>.</td></tr><tr><td>View event</td><td>Click to open the event in the <a href="/docontrol-user-guide/saas-data-monitoring/events.md">Events</a> page</td></tr></tbody></table>

{% hint style="success" %}
Click **Download CSV** to export a file with all events for a specific user.
{% endhint %}

## View events

To view events for a specific emai&#x6C;**,** select the actor's relevant email and click **View events.**

<div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fk3jqaTGO41FRxXm4ZtYo%2Fview%20events.png?alt=media&amp;token=c9f552ce-41d6-43a7-8b3c-8e9c1bd231a9" alt=""><figcaption></figcaption></figure></div>


---

# 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://docs.docontrol.io/docontrol-user-guide/risk-management/identities/identity-card/user-events.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.