---
sourceDocument: Brazil Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/impact

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Configure exception approval behavior

# Configure exception approval behavior {#ariaid-title1}

Release version: Brazil  
Updated October 28, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure how exception reasons are enforced, approved, and re-evaluated when findings are detected using the Scan Engine. Settings control exception behavior.

## Before you begin

All instances must be registered in My SN Instances before configuring approval settings. See [Register your instance in My SN Instances](https://www.servicenow.com/docs/qVtcMVX4ueNM5WLtwJLobg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.") for details.

Role required: Scan Engine admin (sn_se.scan_engine_admin)

## About this task

This task sets the exception reason options in order. For what each setting does and the values it accepts, see [Configure exception reason properties](https://www.servicenow.com/docs/N0AFaFXt6W2vXFO1dVFanw "When real-time enforcement, enforce_real_time_validation, is enabled, exception reasons can be configured for Suggest, Review, Recommend, and Act level findings based on the exception reason scope. The scope controls which finding levels can have exceptions. It doesn't decide which findings block a save."). For an overview of exception reasons and the approval lifecycle, see [Exception handling in Scan Engine](https://www.servicenow.com/docs/wKTHOG99L5R_SwgY463rvA "Exception handling enables developers and administrators to manage findings that are out of scope, pre-existing, or acceptable risks. The Scan Engine exception model supports enterprise approval workflows, predictable lifecycle behavior, and reliable governance across all finding levels.").

## Procedure

1. Navigate to AllImpactConfigurationScan Engine Properties and select the Exception Reason tab.  
   The exception reason settings are displayed.
2. Select or clear Enforce rejected exception reason validations.
3. Select the Exception reason scope: Recommend only, Act and Recommend, or All levels.
4. On each non-production instance where you want exceptions approved in production, select Enable approvals in production.
5. On the production instance, in the Approval group(s) field, select the group or groups that approve or reject exception reasons.
6. Select or clear Exclude approved exception reasons from technical debt.
7. Control re-evaluation behavior.
   1. For Upon new finding found, select Auto Accept Existing Reason or Re-approve Existing Reason.
   2. For Upon line number change, select Auto Accept Existing Reason or Re-approve Existing Reason.
8. Select Save.

*[\>]: and then


