> 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/manage-alerts/set-alert-status.md).

# Set alert status

To manage the alert lifecycle efficiently, you can assign different statuses to alerts. These statuses enable you to focus on alerts according to their stage in the investigation process.

You can change the alert status for:

* [A single alert](#change-the-alert-status-for-a-single-alert)
* [Multiple alerts](#change-the-alert-status-for-multiple-alerts)

You can also [filter alerts](/docontrol-user-guide/risk-management/alerts/filter-alerts.md#filter-alerts-by-status) according to status:

<table><thead><tr><th width="169">Alert status</th><th>Description</th></tr></thead><tbody><tr><td>New</td><td>The initial status of a newly-generated alert.<br>An alert remains New until a user changes its status.</td></tr><tr><td>In progress</td><td>Indicates that the incident is being investigated.</td></tr><tr><td>Suppressed</td><td>Indicates that this specific alert is irrelevant or does not carry any risk.  </td></tr><tr><td>Resolved</td><td>An investigation of the incident was completed.</td></tr><tr><td>Auto-resolved</td><td>The alert was automatically resolved without any manual intervention. To configure auto-resolved alerts, see <a href="/docontrol-user-guide/risk-management/alerts/configure-alerts.md#auto-resolve-alerts">Auto-resolve alerts</a>.</td></tr></tbody></table>

{% hint style="info" %}
Hover over the alert status to see the **date** and **time** when the alert status was changed, and  if relevant, the **team member** who changed it.
{% endhint %}

As the investigation of a specific alert progresses, you can change the alert status to reflect the investigation process. The alert status can be changed for alerts one-by-one or in bulk.

## Change the alert status for a single alert

1. In the **Alerts** inbox, select an alert.
2. Click the **Status** dropdown next to the alert name.
3. Select an alert status from the dropdown list. The alert status is changed to the new status.

## Change the alert status for multiple alerts

1. In the **Alerts** inbox, select multiple alerts.
2. Click **Set status** in the bulk selection bar. <br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FwMJnjr5UwKuk6BB7Uj6x%2Fset%20status.png?alt=media&amp;token=736b9d26-7d22-48f9-a6ac-4752fea27b9b" alt=""><figcaption></figcaption></figure>
3. Select a status from the dropdown list:
   * New
   * In progress
   * Suppressed
   * Resolved

All selected alerts are set to the new status.

{% hint style="info" %}
You cannot change an alert status to **auto-resolved** since this is a system status assigned by DoControl.&#x20;

However, you can change auto-resolved alerts to a different status if necessary.
{% 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/manage-alerts/set-alert-status.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.
