---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Define criticality for application services

# Define criticality for application services {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

For each service instance, select a criticality level that reflects how important it is to your organization operations.

## Before you begin

Determine how important the application service is to your organization.

Role required: service_mapping_admin

## About this task

Typically, you might assign high criticality to service instances, which impact your customer base or sales revenue, while giving low criticality to internal service instances causing minor inconvenience to organization employees. For example, you could set high criticality for a service instance that supports sales functionality using the organization web site. A service instance that provides internal printing for the organization employees could receive low criticality.  
You can also use a criticality value to define recovery strategies. Figure 1. Criticality levels displayed in Operator Workspace page   

## Procedure

1. In the classic environment, perform the following steps:
   1. Navigate to AllService MappingHome.  
      The Home page displays only information on service instances that Service Mapping can discover or already discovered. The Home page does not display information on service instances that are created manually or using the API.
   2. Click View Your Services on the Completed tile.
   3. Select the relevant application service.
   4. Click Additional Info.
   5. Select the appropriate option from the Business criticality list.
   6. Click Update.
   {#define-criticality-for-business-services__substeps_lvh_yhm_whb}
2. Alternatively, perform the following steps in the Agent Workspace UI:
   1. Navigate to Agent WorkspaceAgent Workspace Home.
   2. Click Lists in the left pane.
   3. Navigate to ServicesAll Services.  
      The list of services displays services in Operational status.
   4. Select the relevant application service.
   5. Click the Open Preview icon.  

      <br />

      The Details pane opens on the right.
   6. Select the appropriate option from the Business criticality list.
   7. Click Update.
   {#define-criticality-for-business-services__substeps_t2m_zmm_whb}
**Related concepts**   

* [Service definition transfer from one instance to another](https://servicenow-prod.fluidtopics.net/0m8zCq~MrSCq3TQZmNN6GA#transfer-service-definitions "Save time and effort by exporting definitions of service instances from the source instance and importing these definitions into the target instance. You can use this method to copy definitions of service instances only of the discovered type.")  
**Related tasks**   

* [Group application services](https://servicenow-prod.fluidtopics.net/fJqUMi_qakxfnAzOigjV_w "Organize application services by groups to perform actions simultaneously on multiple services, and to control user access to services. You can use Event Management to track service health by service groups.")
* [Control user access to application services](https://servicenow-prod.fluidtopics.net/Tl72BIYyrHnYkttnrTFwVw "Assign user roles to service groups to grant users access to application services in your organization. Your organization may restrict access to some services for security or secrecy reasons.")
* [Schedule a top-down discovery by Service Mapping](https://servicenow-prod.fluidtopics.net/f0ArHYog5fm~LDBlmp997A "After Service Mapping discovers configuration items (CIs) belonging to your service instance for the first time, it then rediscovers CIs to find changes and updates. Create or modify discovery schedules to control how often Service Mapping rediscovers services or CIs. For example, you may create custom discovery schedules to avoid redundant stress on the infrastructure.")

*[\>]: and then