{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":45150,"path":"security-management/sem-approve-ex-rule-request.md","title":"Approve an exception rule request","bundle":null,"doc_type":null,"release":"australia","body":"\n# Approve an exception rule request\n\nAssess exception rule requests from users so that you can approve or reject these requests.\n\n## Before you begin\n\nRole required: sn\\_vul.exception\\_approver\n\n## About this task\n\nException approver level 1 user group members can approve the level 1 exception rule requests. Similarly, exception approver level 2 user group members can approve the level 2 exception rule requests. Both the user groups inherit the exception approver role by default.\n\n**Note:**\n\nIf you are deploying the VR application for the first time, the flow designer for exception management is enabled by default. If you are already using the workflow, you can update to the flow designer. In both cases, you cannot change it back to workflow. To configure approval rules for exception management and false positive, see [Configure approval rules for Exception Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/exception-mgt-approval-rules.md).\n\n## Procedure\n\n1.  Navigate to **Workspaces** > **Security Exposure Management**.\n\n2.  Select **Administration** in the navigation pane.\n\n3.  Select **Review** on the **Exception rules** tile.\n\n4.  Select a request from your queue.\n\n5.  Approve or reject the request with and explain why you approved or rejected the request.\n\n    You can review the **Impacted findings** metric on the **Overview** tab to see how many findings match the rule's conditions. Select the count to view the matching findings or refresh it to recalculate based on the latest data.\n\n\n**Parent Topic:**[Configuring an exception rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/sem-configure-exception-rule.md)\n\n"}}