> 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/assign-team-member.md).

# Assign team member

You can assign alerts to DoControl team members one-by-one or in bulk. DoControl automatically notifies team members by email that they have an alert to investigate.

When it comes to assigning alerts, you can:

* [Assign an alert](#assign-an-alert-to-a-team-member) to a team member
* [Assign multiple alerts](#assign-alerts-in-bulk-to-a-team-member) to the same team member
* [Reassign an alert](#reassign-an-alert-to-another-team-member) to a different team member during the investigation process
* [Remove a team member](#remove-a-team-member-from-an-assigned-alert) from a specific alert
* [Unassign team members](#unassign-team-members-from-alerts-in-bulk) from alerts in bulk

{% hint style="info" %}

* Once an alert is assigned to a team member, the alert status changes from **New** to **In progress**.
* You cannot assign auto-resolved alerts to team members.
  {% endhint %}

## Assign an alert to a team member

1. In the **Alerts** inbox, select an alert.
2. Under **Assign team member**, enter a user name.\
   \
   ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F7NN8hELkcARr64Xziwss%2Fassign%20alert.png?alt=media\&token=73985c22-08c9-4a01-9967-904e6a437704)

The team member automatically receives a notification email with the assigned alert, including severity level and event details, and a link to the alert.

## Assign alerts in bulk to a team member

1. In the **Alerts** inbox, select multiple alerts.
2. Click **Assign** in the bulk selection bar.&#x20;
3. Select a team member from the dropdown list. All selected alerts are assigned to the selected team member.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FPk5oiEZuO4NiRTqc7ExU%2Falert%20selection%20bulk.png?alt=media&amp;token=3ec8b047-a575-4dcf-aa16-cba9c9a5b715" alt=""><figcaption></figcaption></figure>

## Reassign an alert to another team member

1. In the **Alerts** inbox, select an alert.
2. Under **Assign team member**, select another user from the dropdown list.\
   \
   ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FpTv4Eysb7HaktllFnsWd%2Falert%20in%20progress.png?alt=media\&token=5dcdeeb8-987a-4f83-bad5-9be541ef4ef5)

The alert is reassigned to another team member.

{% hint style="info" %}
You can assign each alert to one team member only.
{% endhint %}

## Remove a team member from an assigned alert

1. In the **Alerts** inbox, select the relevant alert.
2. Under **Assign team member**, click **x** next to the user's name.\
   \
   ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FQxLb4suGpT7HHwPNBAD8%2Fremove%20user%20from%20alert.png?alt=media\&token=b6ef7454-968f-407e-ab6c-b50024640d5d)\
   \
   The alert is unassigned from this user.

## Unassign team members from alerts in bulk

1. In the **Alerts** inbox, select multiple alerts.
2. Click **Unassign** in the bulk selection bar. All team members are unassigned from the selected alerts.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fg06NmODLGpEuwOvbjgo3%2Falert%20selection%20bulk.png?alt=media&amp;token=6e4c4627-8858-4069-b5c2-1065ec6a9230" alt=""><figcaption></figcaption></figure>


---

# 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/assign-team-member.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.
