> 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-alerts.md).

# User alerts

All alerts are displayed where the user is either the actor or target, since integrating with DoControl. The user's email is displayed in **bold**. 

You can display either:

* **Active** alerts - Displayed in the main Alerts page
* **Archived** alerts - Not displayed in the main Alerts page; kept for future reference

<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%2FDYWmmtSpFTzuBuF0yoma%2FIdentities%20alerts.png?alt=media&amp;token=751f0785-b231-4087-ab34-5fa1d299e31c" alt="" width="563"><figcaption><p>Alerts triggered by the user</p></figcaption></figure></div>

You can view both active and archived user alerts, according to these parameters:

<table><thead><tr><th width="220">User alert parameter</th><th>Description</th></tr></thead><tbody><tr><td>Severity</td><td>An indication of how risky the alert is (low, medium, high). This parameter is fully customizable.</td></tr><tr><td>Alert name</td><td>Description of alert type based on the event which triggered the alert</td></tr><tr><td>App</td><td>SaaS app from which the alert was triggered</td></tr><tr><td>Actor</td><td>Email of the user who triggered the alert</td></tr><tr><td>Target</td><td>Email of the target user who received the asset</td></tr><tr><td>Date &#x26; time</td><td>Date and time when the alert was generated</td></tr><tr><td>View alert</td><td>Click to open the alert in the <a href="/docontrol-user-guide/risk-management/alerts/view-alerts.md">Alerts</a> page</td></tr></tbody></table>

## View alerts

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

<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%2Faxid8WhhhlQbEVSaLNb4%2Fview%20alerts.png?alt=media&amp;token=12098f0a-a2e5-487a-a40f-1496e78120ec" 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-alerts.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.