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

# Agentic alerts

Agentic alerts are proactive AI-powered notifications for early threat detection, where each alert type supports a use case in a specific SaaS app. 

These alerts analyze and contextualize, leverage benchmarks, and advise you what steps to take next, helping you to make smart decisions about complex situations in a more accurate way.

{% hint style="warning" %}

* Agentic alerts are a beta feature and are being released gradually.
* Agentic alerts are currently excluded from global alert metrics and calculations that appear in posture pages and dashboards.
  {% endhint %}

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fi5olFoFkAsOyn7szlDoL%2Fagentic%20alert%20view.png?alt=media&amp;token=77594d3b-d894-44db-ad37-69433b9cc4b1" alt=""><figcaption></figcaption></figure>

Agentic alerts notify you about anomalous behavior in these apps, giving you an enriched-AI context to investigate and remediate:

* Google Drive
* Google Workspace
* Okta

{% hint style="info" %}

* To customize settings for individual alert types, see [Configure agentic alerts](/docontrol-user-guide/risk-management/alerts/configure-alerts/configure-agentic-alerts.md).
* For a full list of DoControl agentic alerts, see the DoControl Alert Specifications.
  {% endhint %}


---

# 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/alerts/agentic-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.