# Incident Priority

Establish an incident classification scheme and assign incident priorities for effective triage

Incident priority allows you to classify incidents by priority levels. Just as alerts can have different [severity](/incident-management/incidents/dynamic-notifications#eventalert-severity-levels) levels and notifications can have different [urgency](/incident-management/services/configurable-service-settings#notification-urgency) levels, incidents can be classified into different priority levels. Priority labels are customized on a per-account basis, so you can configure the priority scheme in PagerDuty to match the scheme you may already be using in other tools.

- [Establish an Incident Classification Scheme](#establish-an-incident-classification-scheme)
- [Configure Incident Priority](#configure-incident-priority)
- [Prioritize an Incident](#prioritize-an-incident)
- [Disable Incident Priority](#disable-incident-priority)

## Establish an Incident Classification Scheme

Before [configuring incident priority](#configure-incident-priority), establish an incident classification scheme. Your incident classification scheme establishes a common language and criteria for communicating about incident levels and response elements. This information is ideally shared organization-wide. Remember that this scheme is not just for technical responders and support staff; other parts of your organization may need to be aware of incidents and their assessed impact, and occasionally participate in incident response, as well.

The following are the steps to establish an incident classification scheme:

1. **List the incident classification levels**: This is usually P1 through P5 (for priority), or SEV-1 through SEV-5 (for severity). Typically, the lower the number, the higher its impact (i.e., P1 is more important than P5).
2. **Define what each level means**: Describe the impact and characteristics that apply to each classification level. These guidelines must be clear and objective enough that responders can accurately assess an open incident and assign it to a level. That said, incidents may be upgraded or downgraded as the situation evolves.
3. **Define the expected response**: For each classification level, identify the expected scope and response urgency. Some organizations also have formal or informal service-level agreements at each level.

For more information and examples, refer to [Severity Levels](/ops-guides/incident-response-guide/severity-levels) in the [Incident Response Guide](/ops-guides/incident-response-guide).

If your organization does not have an incident classification scheme in place, defining a limited number of classification levels is essential for effective triage and major incident response processes. If, on the other hand, you have more than five classification levels, think critically about how many levels would benefit your organization in practice. The more levels you have, the more complex and time-consuming triage can become.

> **Tip:** The Incident Priority feature does not allow any of the five levels to be blank. If your organization uses fewer than five classification levels, you can enter `---` for any unused levels.

## Configure Incident Priority

After establishing your [incident classification scheme](#establish-an-incident-classification-scheme), the next step is to configure the levels in PagerDuty.

> **Required User Permissions:** The Account Owner and Admins/Global Admins can configure and edit Incident Priority levels.

To configure this feature, in the PagerDuty web app:

1. Navigate to **User Icon**  →  **Account Settings**  →  **Incident Settings** tab. 
2. Toggle **Enable incident priority levels** to the **on** position.
3. Under **Incident Priority**, you can classify incidents with five different priority levels. Customize your levels with the following:

| Field                    | More info                                                                                                                                                                                                                                                                                                                                                  |
| :----------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Priority Level           | This is typically P1-P5 or SEV-1-SEV-5.                                                                                                                                                                                                                                                                                                                    |
| Color                    | Color labels draw attention to the most important incidents in a dashboard or other view. Use distinctive colors for the levels corresponding to major incidents to enhance visibility of the most important incidents. For example, at PagerDuty, we use red and orange for our two highest levels, and blue and gray for lower-priority incident levels. |
| Description (_optional_) | Describe the incident impact and characteristics that apply to each classification level. These guidelines must be clear and objective enough that responders can accurately assess an open incident and assign it exactly one level.                                                                                                                      |

3. Click **Save**.

![A screenshot of the PagerDuty web app showing how to configure incident priority](/images/kb/08e6c63f085943d61d82960a94529a1286a9de7321fb07458312a649c3e40a1b-incident_priority.png)
*Configure incident priority*

Priority is displayed on the **Incidents** page and on an incident's details page in both the web and mobile apps.

## Prioritize an Incident

Prioritizing incidents helps drive decisions around the response process and provides valuable context for others. When looking at an incident, the priority provides an immediate, clear indication of the prior assessment that hass been performed. You can set the Incident priority at creation or after the incident has been triggered. The following is an incident with a priority level set, **SEV-1**:

![A screenshot of the PagerDuty web app showing how to prioritize an incident during triage](/images/kb/ed9dc70f331eddb72adbf956d6c8d5ac07ddf6a257288b5c5ad45f5c40033e43-incident-priority-incident_view.webp)
*Prioritize an incident during triage*

In addition, priority is clearly displayed on the incident dashboard, making it easy to see when critical issues are active. You can sort incidents by priority on this page, so that whether looking at incidents for a single team or across your whole organization, you can instantly see critical issues:

![A screenshot of the PagerDuty web app showing incident priority on the Incidents page](/images/kb/e25b26d13e8da1fb5033fcc5f7cab5601c8da54d097d796bd19ffa5ce038beca-incident-priority-filter.webp)
*View incident priority*

You can set incident priority in multiple ways:

**Set Incident Priority Using the Web App**

### At Incident Creation

1. Navigate to the **Incidents** page. 
2. Click **New Incident**.
3. Select your desired **priority level** from the dropdown.

![A screenshot of the PagerDuty web app showing how to set priority at incident creation](/images/kb/ecb963d2666637a43c25ab90f3e25ec3637579e1f15f61a398bf1837d7cc96ad-create_incident.png)
*Set priority at incident creation*

4. Enter the remaining incident details. 
5. Click **Create Incident**.

### To an Existing Incident

1. Find the incident you want to prioritize and select its **Title** to navigate to its details page.
2. Click the **Priority** dropdown and select the desired **priority level**.

![Edit an incident's priority](/images/kb/bf4042b6dd3762672f7a8b2c4abbb2623d818688056bc7e31a063bb84c9778a8-incident-priority-active-incident.webp)

**Set Incident Priority Using the Mobile App**

### At Incident Creation

1. Navigate to the **Open Incidents** screen. 
2. Tap  in the top-right corner and select **New Incident...**.

![A screenshot of the PagerDuty mobile app showing how to create a new incident](/images/kb/91c75bf89d36f88ae418a51595700c3a3be40422fbf55786c361032381a88dea-incident-priority-mobile-new-incident.webp)
*Priority in the mobile app*

3. Tap **Priority** and select the **priority level** from the list.

![A screenshot of the PagerDuty mobile app emphasizing the Priority row](/images/kb/ef6d79972bd956b5b0314f52a9ec2cdfedb1c7f641256e0112ad9e1bde660162-incident-priority-mobile-add-priority.webp)
*Select priority*

4. Enter any remaining incident details. 

5. Tap **Create**.

The incident will then display a label displaying its priority level:

![A screenshot of the PagerDuty mobile app showing an incident's priority](/images/kb/962636558d136648940a16b2cb2025c73ad3ae95fb7672e460ecf6ffe3e1b7b5-incident-priority-mobile-priority-marker.webp)
*View priority*

### To an Existing Incident

1. Find the incident that you want to prioritize. 
2. Tap the incident’s **name** to navigate to its details screen.
3. With the **Triage** tab selected, tap **Add/Edit Priority**. 
4. Select a **priority level**.
5. Tap **Confirm** in the confirmation dialog box.

**Set Incident Priority via the REST API**

In addition to the features available in the PagerDuty [web app](#in-the-web-app) and [mobile app](#in-the-mobile-app), automated systems can also interact with incident priority. You can use the [Incident REST API](/developer/api/reference/rest/incidents/create-incident) to specify an incident’s priority when it is created, and all relevant priority details are included when the API returns an incident object.

Refer to the following developer documentation for more information about working with incident priority:

- [List priorities](/developer/api/reference/rest/priorities/list-priorities)
- [Create an incident (with priority)](/developer/api/reference/rest/incidents/create-incident).

Additionally, incident webhooks include information about an incident’s priority. Refer to [Webhooks Overview](https://developer.pagerduty.com/docs/ZG9jOjQ1MTg4ODQ0-overview) for more information.

> **Events API:** You cannot set priority from the Events API currently.

**Set Incident Priority via Event Orchestration**

[Event Orchestration](/ai-automation/aiops/event-orchestration) supports adding priority when an incident is created. Refer to [Incident Actions](/ai-automation/aiops/event-orchestration#incident-data) for more information.

## Disable Incident Priority

As an Account Owner, you can disable incident priority in the web app using the following steps:

1. Navigate to **User Icon**  →  **Account Settings**  →  **Incident Settings** tab. 
2. Toggle **Enable Incident Priority Levels** to the **off** position. Once disabled, the **Priority** column on your Incidents page no longer appears.

> **Retained Configuration Settings:** After disabling incident priority, PagerDuty retains your configuration settings. If you choose to re-enable incident priority later, toggle **Enable Incident Priority Levels** to the **on** position — your historical settings will be preserved, so you will not need to reconfigure them from scratch.