> 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.md). # Manage alerts To enable end-to-end visibility of risk management from alert triggering to resolution, DoControl provides your organization with full alert management capabilities.

{% hint style="info" %} * You need **admin** permission to manage and change alerts. * Viewers can view, filter and share alerts. {% endhint %}

Alert action	Description
View alerts	From the alert inbox, see the full picture on what happened, by who, and the estimated risk of this action
Set alert status	Assign different statuses to alerts one-by-one or in bulk to efficiently handle their investigation and resolution: New, In progress, Suppressed or Resolved
Assign team member	Manage alert caseload across your team: Delegate an alert to a team member to investigate
Filter alerts	Get visibility on the most critical issues by filtering alerts according to severity, alert status, SaaS app, and other parameters such as alert category, alert type, ID, actor and target.
Add note	Summarize the alert investigation or add important reminders in an alert note.
Archive alerts	Focus more on active alerts by removing alerts from the main alert view, and keeping archived alerts for future reference. You can also archive alerts automatically.
Open Jira ticket	Open a pre-populated Jira story to remediate a specific alert.
Share alerts	Copy the alert link (with alert ID) and share alert in another platform.
Configure alerts	Customize the settings for each DoControl alert type: change the severity, and exclude specific actors and targets from receiving alerts
Remediate alerts	Perform on-the-fly DoControl remediation actions to mitigate unnecessary or potentially risky data exposure, and implement automated workflows.
Define alert-triggered workflows	Bind a workflow to a specific alert in order to close the remediation loop faster and ensure better long-term risk coverage

## Alert processing updates DoControl triggers an alert when an anomalous event or behavior is detected across your organization's SaaS apps. This alert is displayed to DoControl users, and your SecOps team is automatically notified. Situations might arise where the alert snapshot was changed while the alert was still in active handling status (New or In Progress). If the alert snapshot was changed after the alert was triggered, some assets might not be displayed. DoControl displays the alert status as: `Processing data`

An alert processing update can occur when: * Assets are still being processed in DoControl's inventory. * Assets were deleted after the alert was triggered: either by the actor, target, or by a remediation action in the workflow. When the alert snapshot changes, DoControl notifies you how many assets are currently available to view, as in the following example:

Clicking the asset link opens the [Assets](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets.md) page with full asset details, including their sharing status. --- # 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.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.