{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":31283,"path":"it-operations-management/service-level-objective-management/sr-add-change-approval-slos.md","title":"Activate SLO-based change approval decisions","bundle":null,"doc_type":null,"release":"australia","body":"\n# Activate SLO-based change approval decisions\n\nActivate Service Level Objective \\(SLO\\) change approval decisions to evaluate change requests based on SLO performance.\n\n## Before you begin\n\nReview change approval policies and their terminology, including policy inputs, decisions, and approval definitions. For more information, see [Change approval policies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/change-approval-policy.md).\n\nRole required: admin\n\n## About this task\n\nActivate the Service Level Objective Change policy's decisions to include SLO performance in your change management process. The policy is active by default, however, its decisions are inactive.\n\nWhen you activate the policy's decisions, the policy evaluates SLOs as inputs and implements the following:\n\n-   Require group manager approval if these conditions are true:\n    -   The lowest SLO error budget is less than 25%.\n    -   The highest SLO burn rate is greater than 1%.\n-   Auto-approve change requests if these conditions are true:\n    -   The lowest SLO error budget is greater than 25%.\n    -   The highest SLO burn rate is less than 1%.\n\n## Procedure\n\n1.  Navigate to **All** > **Change** > **Change Policy** > **Change Approval Policies**.\n\n2.  Select the **Service Level Objective Change policy**.\n\n3.  In the **Decisions** tab, set **Active** to true for these decisions:\n\n    -   **Budget < 25% and Burn Rate > 1**\n    -   **Budget > 25% and Burn rate < 1**\n4.  Select **Update** to save your changes.\n\n    The decisions are active and part of your change management process.\n\n\n## What to do next\n\nUse a test change request to verify that change requests are either auto-approved or routed to a manager as expected.\n\nYou can also customize the Service Level Objective Change policy, including its name and conditions, as needed.\n\nFor more advanced setups, use Flow Designer to customize the SLOs and services included as policy inputs:\n\n**Important:** Customizing the flow prevents it from receiving future release updates. That behavior is intentional to avoid overwriting your customizations.\n\n1.  Navigate to **Process Automation** > **Flow Designer**.\n2.  In the list of flows, select **Change - SLO – Authorize** and then select **SLO - Get worst performing SLOs**.\n3.  Customize the **Action Inputs** section.\n4.  Select **Done** to implement your changes.\n\n**Parent Topic:**[Using SLO Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/service-level-objective-management/using-service-level-objective-management.md)\n\n"}}