> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/escalation-policies/reassign-an-incident.md).
# Reassign an Incident
### Prerequisites
* The User Role for the user in the Team must have the necessary permissions in order to reassign incidents.
### Reassigning Incidents
An incident in the `Triggered` or `Acknowledged` state can be reassigned to a different **User**, **Squad,** or **Escalation Policy**.
1\. Open an incident that you wish to reassign from the **Dashboard** or **Incidents** page
2\. Click on **Reassign**
3\. Select a **User**, **Squad,** or an **Escalation Policy** from the drop-down
{% hint style="info" %}
**Note:**
When an incident is reassigned to a User or Squad then the user(s) are notified based on their Personal [Notification Rules](/manage-users/notification-rules.md) set up under their Profile settings.
{% endhint %}
4\. Click on **Reassign** to complete the action
5\. The reassigned action is auto-recorded in the **Incident Activity Timeline** of the incident and the same can be viewed in the **Responders** section
{% hint style="info" %}
**Note:**
The Incident Activity Timeline will show incident reassignment, mentioning both the assigned and assignee.
{% endhint %}
*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://support.incidents.cloud.solarwinds.com/escalation-policies/reassign-an-incident.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.