# Reassign incidents

### How to reassign incidents?

Select any number of incidents and click on **reassign** on the header of the incidents table.

![Reassign button on incidents table](/files/-MGKkm9qgtSUi7l25ZCM)

You can reassign an incident to a team member. Not all incidents will have assignee to it, especially when you have Slack app notifying you on channels.

![Reassigned incident](/files/-MGKl6kExv4WPfl50-xd)

Once reassigned, the user will get an email notifying them about it.

### What happens to escalations?

Your escalation policy for the incident *will NOT be affected*. It will continue as is.

### Where do I reassign incident(s)?

You will see the reassign incident option on every incident table. More particularly it can be found on -

1. Dashboard
2. Incident details page
3. Incidents listed for a service

{% hint style="danger" %}
You cannot assign an incident to a team member with **Support role**
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.spike.sh/incidents/reassign-incidents.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.