> 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/manage-users/notification-rules.md).
# Incident (Personal) Notification Rules
Incident (Personal) Notification Rules determine how an individual user is notified for an incident that is assigned to them. One can set up rules to be notified on any of the following notification channels:
* Email
* [Push notification on the Squadcast mobile app](/mobile-app/using-the-mobile-app.md)
* SMS
* Phone
As a preference, one would like to be notified a certain way for P1 priority incidents versus P4 or P5 priority incidents. By selecting the priority first, users have a way to define how they should be notified for incidents assigned to them.
{% hint style="info" %}
**Edit Notification Rules for other users of Squadcast**
Irrespective of your User Role in Squadcast, you will only be able to set/edit your own Incident (Personal) Notification Rules. You will not be able to do it for any other member of Squadcast. If you wish to explicitly specify Notification Channels for all the users, this can be done in the Escalation Policy by selecting **Custom** from the drop-down.
{% endhint %}
### Edit Notification Rules
1. Click on the user icon in the upper right corner and select **Profile**
2\. You will be taken into the **My Profile** section where you can navigate to **Alert Settings** to configure this
By default, there will be a a fallback / default configuration that will be used for all incidents without a defined priority if it is assigned to that user.
3\. To define a priority-specific configuration, start by selecting **Add Notification Rules**
Here, you can select the priority that this configuration needs to apply to and define the notification rules
4\. Select **Save** after making changes to save the configuration
{% hint style="info" %}
**Info:**
1. Each priority - P1 through P5 can have one configuration each
2. You can set up a rule to be notified immediately, as soon as the incident is triggered, if you input 0 in the text box that asks for time
3. You cannot add `SMS` and `Phone` more than 2 times within each of your priority-specific configurations. However, there are no such limits for `Push` or `Email`
4. A maximum of 8 rules per priority-specific configuration can be configured
5. You cannot define 2 rules through the same medium to be dispatched at the same time - for instance, you cannot have 2 rules via Email that has to be triggered at time t=0 as believe spam has not helped anyone, and definitely not while looking at high priority incidents
{% endhint %}
You’re good to go. Now, when an incident is assigned to **you**, you will be notified based on your notification preferences set in the **Incident (Personal)** **Notification Rules** section.
*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/manage-users/notification-rules.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.