{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":45835,"path":"security-management/vulnerability-response/add-exception-approver.md","title":"Add an exception approver","bundle":null,"doc_type":null,"release":"australia","body":"\n# Add an exception approver\n\nAdd users to the approver groups so that you can request an exception.\n\n## Before you begin\n\nPersona and granular roles are available to help you manage what users and groups can see and do in the Vulnerability Response application. For an initial assignment of the persona roles in Setup Assistant, see [Assign the Vulnerability Response persona roles using Setup Assistant](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-assign-personas_SA.md). For more information about managing granular roles, see [Manage persona and granular roles for Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr_manage_granular-roles.md).\n\nRole required: sn\\_vul.exception\\_approver\n\n## About this task\n\nUpto Vulnerability Response v14.0, an exception request for a vulnerable item or remediation task is approved using the default two-level approval workflow. The request must be approved by two levels of approvers.\n\n**Note:** Upto Vulnerability Response v14.0, if there's no first-level approver, an exception can't be requested. However, starting from Vulnerability Response v15.0, if 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 **All** > **User Administration** > **Groups**.\n\n2. In the Name column, search for **Exception**, and click **Exception Approver - Level 1**.\n\n **Note:** Starting from Vulnerability Response v12.8.1, you can use the system properties provided in the base system for exception approvals via workflow in the System Properties \\[sys\\_properties\\] table. So, when an exception or false positive request is raised via workflow, it’s sent for approval to the group IDs defined in the system property. Navigate to **All** > **System Properties** and select **sn\\_vul.exception\\_approver\\_L1**, **sn\\_vul.exception\\_approver\\_L2**, or **sn\\_vul.false\\_positive\\_approver\\_group** to change the property value.\n\n3. On the Group Exception Approver - Level 1 form, click the Group Members related list.\n\n4. Click **New** to create a list.\n\n5. On the form, fill in the fields.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nUser ID\n\n\n\nUnique identifier for the user.\n\n
\n\nFirst name\n\n\n\nUser's first name.\n\n
\n\nLast name\n\n\n\nUser's last name.\n\n
\n\nTitle\n\n\n\nUser's job title. Enter a title or job description, or select one from the list.\n\n
\n\nDepartment\n\n\n\nUser's department.\n\n
\n\nPassword\n\n\n\nPassword assigned to the user. This password can be permanent or temporary.\n\n
\n\nPassword needs reset\n\n\n\nOption to enable the user to reset the password to ensure security.\n\n
\n\nLocked out\n\n\n\nOption to lock the user out of the instance and terminate all the user's active sessions. The system prevents users with the admin role from locking themselves out.\n\n
\n\nActive\n\n\n\nOption to make this user active. Only you can see an inactive user in these areas:- Lists of users\n- Selection list on reference fields \\(magnifying glass icon\\)\n- Auto-complete list that appears when you type into a reference field\n\n\n
\n\nWeb service access only\n\n\n\nOption to designate this user as a non-interactive user.\n\n
\n\nInternal Integration User\n\n\n\nOption to designate this user as an internal integration user.\n\n
\n\nEmail\n\n\n\nUser's email address.\n\n
\n\nLanguage\n\n\n\nUser's preferred language.\n\n
\n\nCalendar integration\n\n\n\nCalendar used to manage the work schedule. For example, Outlook.\n\n
\n\nTime zone\n\n\n\nTime zone for this user's location.\n\n
\n\nDate format\n\n\n\nUser's preferred format for dates.\n\n
\n\nBusiness phone\n\n\n\nUser's business phone.\n\n
\n\nMobile phone\n\n\n\nUser's mobile phone.\n\n
\n\nPhoto\n\n\n\nPhoto that you can upload by clicking on **Click to add...**.\n\n
6. Click **Submit**.\n\n7. Repeat steps 1–5 to create an Exception Approver - Level 2.\n\n The approver must navigate to **Vulnerability Response** > **My Approvals** and approve requests.\n\n **Note:** To approve an exception for GRC: Policy and Compliance Management, see [Policy and Compliance Management optional setup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/governance-risk-compliance/policy-compliance-optional-steps.md).\n\n\n"}}