> 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/configure-alerts/configure-global-settings/agentic-alert-exclusions.md).
# Agentic alert exclusions
To reduce noise and over-automation, you can focus exclusively on risky behavior by excluding entities from triggering agentic alerts.
You can exclude specific [actors](#exclude-actors) and [targets](#exclude-targets), including domains, as well as connected [Google apps](#exclude-connected-google-apps) acting on behalf of users. These exclusions do not affect existing DoControl alerts.
Key benefits of excluding entities from triggering agentic alerts include:
* Reduce noise and alert fatigue by surfacing fewer, more relevant alerts
* Increase precision by avoiding repeated actions on predictable, low‑risk behavior
* Align detection with real business context and policy exceptions
* Improve analyst efficiency and build trust by enabling more autonomous triage and remediation
## Exclude actors
You can exclude specific users from triggering agentic alerts only. These exclusions do not affect existing DoControl alerts.
**To exclude actors from triggering agentic alerts:**
1. In the Alerts page, click **Configure alerts.**
2. Scroll down to **Agentic alert exclusions > Exclude actors**.
3. Enter the emails of the actors to exclude.
4. Enter any actor domain to exclude from triggering agentic alerts.
## Exclude targets
You can exclude specific recipients affected by actions related to agentic alerts, so that agentic alerts will not be triggered when these targets are involved. These exclusions do not affect existing DoControl alerts.
**To exclude targets from triggering agentic alerts:**
1. In the Alerts page, click **Configure alerts.**
2. Scroll down to **Agentic alert exclusions > Exclude targets**.
3. Enter the emails of the targets to exclude.
4. Enter any target domain to exclude from triggering agentic alerts.
## Exclude connected Google apps
You can ignore activity that a connected Google app performs on behalf of a user, so that these Google apps will be excluded from triggering agentic alerts.
{% hint style="info" %}
Connected Google apps use originating app IDs to identify third-party applications that perform actions on behalf of users.
{% endhint %}
**To exclude connected Google apps from triggering agentic alerts:**
1. In the Alerts page, click **Configure alerts.**
2. Scroll down to **Agentic alert exclusions > Exclude connected Google apps**.
3. Type the originating app ID of the Google app to exclude, and click **Enter**.
---
# 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/configure-alerts/configure-global-settings/agentic-alert-exclusions.md?ask=&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.
