> 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/remediate-alerts.md).
# Remediate alerts
You can remediate alerts to mitigate both short-term and long-term risk.
{% hint style="warning" %}
You need **Admin** permission to remediate alerts.
{% endhint %}
Click the **Remediation** button at the top-right of each alert to enable the following:
* **Inventory actions -** Perform on-demand remediation actions for assets involved in the alert (for supported actions). Click the action to open a filtered asset page showing all assets involved in the alert, where you can apply [inventory actions](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md).
* **Workflows -** Create [new workflows](/docontrol-user-guide/workflows/create-a-workflow.md) to support future use cases that are similar to the alert. Click a workflow option to open the workflow canvas, where you can create a workflow from a playbook or scratch.
{% hint style="info" %}
The **Create workflow from playbook** link is available for playbooks that support the alert type, and is grayed out if no such playbook exists.
{% 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/remediate-alerts.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.
