# Business Services

Create business services to model how technical services support your business infrastructure and to communicate incident status to non-technical stakeholders

Business services allow you to model capabilities that span multiple technical services and that may be owned by several different teams. Mapping [technical services](/incident-management/services/services-and-integrations) to business services gives responders context on an incident’s impact to the business. [Status Pages](/incident-management/communicate/status-pages-overview) use business services to let non-technical stakeholders see when there is an incident affecting one of the business services they care about.

Business services should be:

- Recognizable to non-technical stakeholders
- Supported by one or more [technical services](/incident-management/services/services-and-integrations) in PagerDuty

You may have business services listed on an external status page, within a service catalog/CMDB, or defined in relation to existing health metrics from a monitoring tool.

> **Required User Permissions:** Admin, Manager, Global Admin and Account Owner base roles can create and edit business services. Managers must have Manager level access to the Team associated with the business service.
>
> If you are not sure what role you have, or if you need your permissions adjusted, visit our sections on [Checking Your User Role](/account-admin/user-roles#check-your-user-role) or [Changing User Roles](/account-admin/user-roles#edit-user-roles).

## Create a Business Service

1. In the PagerDuty web app, navigate to **Services**  →  **Business Services** and click **New Business Service**. 
2. Enter the following information:

| Field           | Description                                                                                                                                                                           |
| :-------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Name**        | Enter a meaningful name that will define the business service.                                                                                                                        |
| **Owner**       | Enter the owner as yourself or a point of contact for the business service. _(Optional)_                                                                                              |
| **Team**        | Select a [Team](/account-admin/teams) associated with this business service. _(Optional)_. Only available on Business, Enterprise for Incident Management and Digital Operations (Legacy) plans. |
| **Description** | Provide a description of what the business service is responsible for.                                                                                                                |

3. Under **Services**, select the **Technical Services** or **Business Services** tab and then search and select [supporting services](#supporting-services) by clicking  to the right of the service's name.
4. Click **Create Business Service** to save. 

> **Non-Critical Technical Services:** Sometimes there is a technical service that supports a business service, but is not critical to its function. You may prefer to omit **non-critical technical services** that support a business service, since a disruption to one of those technical services does not necessarily mean that the business service is disrupted.

## Edit a Business Service

1. Navigate to **Services**  →  **Business Services** and select the **name** of the desired business.
2. To the right of the business service’s name, click  **Edit**.
3. In the edit view, make the required changes and click **Save Changes**.

## Edit Business Services Settings

An incident must have a [priority](/incident-management/incidents/incident-priority) in order to affect a business service. By default, incidents on a supporting technical service with **any** priority will affect a business service. Alternatively, you can configure a business service to require that incidents meet a specified priority threshold.

1. Navigate to **Services**  →  **Business Services** and click .
2. Select when you would like business services to show an incident: 
   - **If a supporting technical service has an open incident with any priority assigned**  
     _or_
   - **If a supporting technical service has an open incident with a priority at or above** and select the **priority level**. 
3. Click **Save Changes**.

## Delete a Business Service

1. Navigate to **Services**  →  **Business Services** and select the **name** of the desired business.
2. Select **More**  →  **Delete Business Service**.
3. In the confirmation dialog, select **Delete Service**.

## Supporting Services

Supporting services are [technical services](/incident-management/services/services-and-integrations), or even other business services, that a business service requires in order to be considered operational. If one of the supporting services mapped to a business service experiences an incident with a qualifying [priority](/incident-management/incidents/incident-priority), this business service will be impacted and appear on [Status Pages](/incident-management/communicate/status-pages).

## Service Graph

The [Service Graph](/incident-management/services/service-graph) visually maps how Business Services connect with technical services across your infrastructure, helping teams quickly understand service dependencies and assess incident impact on business-critical functions.

## Subscribe to Business Services

After defining business services, users can subscribe so that they are notified whenever there is an impacting incident. Please read [Business Service Subscription](/incident-management/services/business-services/subscription) for more information.