---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Allow policy exception requests from other applications

# Allow policy exception requests from other applications {#ariaid-title1}

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

Starting with Version 10.1, you can leverage new policy exception capabilities in Policy and Compliance Management from within other applications.  
Requests are routed through multiple approvals based on risk rating, policy, and control objective associated with an exception. Compliance and risk teams obtain better visibility with respect to exceptions raised for vulnerabilities.  
Note:  
Starting with Version 10.1, if you have installed Version 10.3 of the Vulnerability Response application, you can request policy exceptions using the GRC policy exception management capability inherent in the Policy and Compliance Management application. For details, see [Policy Exception Integration with Vulnerability Response](https://servicenow-prod.fluidtopics.net/~r0qR9X5BRJoKBd3MPHliQ "Starting with Version 10.1, you can request policy exceptions using the GRC policy exception management capability inherent in the Policy and Compliance Management application from within version 10.3 of the Vulnerability Response application.").

Before allowing other applications to leverage the policy exception capabilities of Policy and Compliance Management, you must first add the application to the Integration Registry
and then perform some preliminary setup.
* **[Configure policy exceptions from other applications](https://servicenow-prod.fluidtopics.net/yS7TnO7rwuo3HCCJdbC98Q)**   
  Before you can request policy exceptions from applications other than Policy and Compliance Management, you must add a UI action for making the request and, optionally, create a new list view to see policy exception target records on the Policy Exception form.
* **[Register other applications to request policy exceptions](https://servicenow-prod.fluidtopics.net/vvkPlzMw4FwkGnOkTvIctQ)**   
  Enable other applications to request policy exception from any table such as Problem or Incident and so on. The applications must be added and configured in the Integration Registry.
* **[Define policy exception reason choices](https://servicenow-prod.fluidtopics.net/1iXL5urhkjjH~44QRp7fDg)**   
  You can define reason choices to be available to any user who requests an exception.
* **[Define policy categories](https://servicenow-prod.fluidtopics.net/pMXp5z6o6bSHJeKm27RizA)**   
  You can filter policies by specific criteria to limit the number of policies displayed when you are creating policy exceptions.
* **[Create an exception questionnaire](https://servicenow-prod.fluidtopics.net/sfW7go8Z~IuY1jSMy1tLWQ)**   
  When you are setting up the Policy Exception Integration Registry, you can define configurable questions that can be included in risk assessments created from templates. The Policy Exception Integration Registry can be associated with one template at a time.
* **[Define policy exception verification rules](https://servicenow-prod.fluidtopics.net/Bn~RC8GIpaYiTg5LJ6LOqw)**   
  The verification rule is used to verify the accuracy and completeness of a policy exception request prior to sending it out for approvals. You can define multiple levels of approvers for an application.
* **[Define policy exception approval rules](https://servicenow-prod.fluidtopics.net/ZnyclEvb1hQfvuoLYAcS_Q)**   
  Approval rules define the criteria (risk rating, policy or control objective) that is used for sending approval requests for an exception. Rules can be configured for an application and you can identify multiple levels of approvers, as needed.