--- title: "Criticality" slug: "criticality" updated: 2024-05-16T09:16:09Z published: 2024-05-16T09:16:09Z canonical: "help.symphonysummitai.com/criticality" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Criticality Criticality refers to the degree of importance or significance of a configuration item (CI) within an organization's IT infrastructure or business processes. By understanding the criticality of various components, organizations can make informed decisions about maintenance, upgrades, incident response, and disaster recovery. Let's explore the following Use Case for configuring Criticality! | **Use Case** User persona:Application Designer | **Solution** | | --- | --- | | John, the app designer wants an element that ensures efficient management of IT incidents and minimizes downtime in IT infrastructure supporting servers, networking equipment, databases, applications, and user devices. | John can configure **Criticality** under CMDB configuration and categorize their CIs into different criticality levels based on their impact on business operations and services. He can define four levels: 'High', 'Medium', and 'Low'. Based on this, IT team can manage its software development and deployment processes more effectively, maintaining a balance between stability and innovation. | ### Configure Criticality To configure **Criticality**, perform the following steps: 1. Select **CMDB** > **Criticality**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1692872959466.png?sv=2026-02-06&spr=https&st=2026-11-19T00%3A55%3A31Z&se=2026-11-19T01%3A55%3A31Z&sr=b&sp=r&sig=CoUsyNLE5rpINLDbQWxawZhKGjcJTQd8rBYtMC3yRxM%3D)Figure: Define Criticality 2. Configure the **Criticality** for CMDB. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1692873185903.png?sv=2026-02-06&spr=https&st=2026-11-19T00%3A55%3A31Z&se=2026-11-19T01%3A55%3A31Z&sr=b&sp=r&sig=RrJgrtalZV1hJZDT7n9oyMUUWQz23JcUmBMj1TIgPiw%3D) Figure: Configuration screen 3. Specify the **Tenant** (ex: Information Technology), **Criticality Name** as Low, Medium or High, Sort Order as 1 or 2 or 3 and check the **Active**. The screenshot for field values under the **Criticality** is shown below. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1692941086517.png?sv=2026-02-06&spr=https&st=2026-11-19T00%3A55%3A31Z&se=2026-11-19T01%3A55%3A31Z&sr=b&sp=r&sig=KxNq8U3niy2tWhpJBdT%2Fl8DIILlYaSG9RoE8l2M1j60%3D)Figure: Criticality 4. Click **Save** to submit the configuration. The configured list of Criticality appears as shown below. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1692878059944.png?sv=2026-02-06&spr=https&st=2026-11-19T00%3A55%3A31Z&se=2026-11-19T01%3A55%3A31Z&sr=b&sp=r&sig=f1gdVx3UaCbtWcMjnS2FUPcbJvzOMpwFg3uY3WPtbGI%3D)Figure: Criticality list