---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Unauthorized change request

# Unauthorized change request {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Unauthorized Change Request

ServiceNow captures and manages unauthorized change activities on configuration items (CIs) as part of the Service Mapping integration with IT Service Management (ITSM).
When an unauthorized change is detected on a CI within an application service, an emergency unauthorized change request is automatically created in the Change Management application.
This enables timely review, approval, or rejection by the Change Management team to maintain control over unplanned changes.
Show full answer Show less  

## Key Features

* **Automated Detection and Request Creation:** Unauthorized changes trigger a `ci.change.unplanned` event, leading to the automatic creation of an emergency change request if event processing is enabled.
* **Flapper Algorithm for False Positives:** A learning pattern reduces false positives by identifying measurement errors or minor variations (e.g., case sensitivity) and preventing unnecessary change requests.
* **Change Request State Flow:** Unauthorized change requests follow a unique workflow. They start in the Review state, skipping Schedule and Implement because the change has already occurred. Requests can be approved, rejected, and then closed with a post-implementation review task created.
* **Notification and Review:** Notifications regarding unauthorized changes are sent to relevant stakeholders, including the Change Management group and CI owners. Users can disable notifications if excessive emails are generated.
* **Post-Implementation Review:** After approval, a review task is assigned to evaluate the risk and impact of the unauthorized change.
* **Modification of Unauthorized Change Requests:** Change managers can convert an unauthorized change request into an emergency change request by clearing the Unauthorized checkbox and providing a work note.
* **Configurable Settings:** The Unauthorized Change Properties page allows administrators to enable or disable unauthorized change detection and configure criteria for these changes.

## Practical Guidance for ServiceNow Customers

Customers can monitor unauthorized CI changes effectively and reduce noise from false alerts using the flapper algorithm. The emergency change request workflow is designed to handle already implemented changes, enabling quick review and remediation.

Change managers have control to adjust the status of unauthorized change requests and disable notifications when needed to reduce alert fatigue. Post-implementation reviews ensure that risks associated with unauthorized changes are assessed and addressed.

By leveraging these features, ServiceNow customers can maintain tighter governance over unplanned changes to CIs within their application services, improving overall change management discipline and reducing operational risks.  
Understand how an unauthorized change activity on a configuration item (CI) is captured
and managed, so that you can review and take timely action on this change.

As part of the ServiceNow®
Service Mapping integration with ServiceNow®
ITSM, the Change Management application receives an event notification when an unauthorized change activity is detected. As a result, an emergency unauthorized change request is created for the relevant CI. You can review and approve
or reject the unauthorized change from the Change Management application.  
Note:  
Unauthorized change requests are created only for the CIs that are part of the application services. Also, there is a flapper algorithm that uses a learning pattern to minimize false positives.

At times, the discovery process (horizontal or top-down discovery) identifies a change on a
CI property that may not be an actual change by definition. This identification is due to a
measurement error or just a different representation of the same value, such as case
sensitivity. The learning pattern identifies the false positives (flapper changes) and
prevents triggering the recomputation and time-line updates as an emergency change request is
a critical action. You want to avoid false positives and report only real changes.  
The learning pattern identifies the false positives as follows:

1. When a CI property associated with a service changes, the new value (CI and field pair) is logged in the flapper's data table.
2. The system runs a nightly job and executes various algorithms on the data that is collected to identify patterns that point to false positives.
3. The system runs all the relevant strategy predicates for the changed CI fields with a confidence level greater than 90%. This step determines whether all the new values are false positives or not. If all the new values are false positives, then the change is ignored, and the model is not updated.  
   Note:  
   If the CI is associated with an active change request, then this step is skipped.
{#unauthorized-change-request__ol_snx_hbp_jkb}  
An unauthorized change request is created when an unplanned CI change activity occurs, and the system triggers the following checks:

* The system checks to see if the CI is part of the allowed CI classes. If it is allowed, then the system checks to see if this specific CI has been flagged previously. If it was flagged and the previously created unauthorized change was within the notification ignore period, then no further action is taken. If not, then further checks are made to see whether this CI is associated to a change request that matches the condition stated in the properties. If not, then the change to the CI that was detected is flagged as unauthorized and a ci.change.unplanned event is raised.
* On receipt of the ci.change.unplanned event, the script checks to see if the Enable event processing field is true. If it is true, then an unauthorized change request is created. By default, this property is false.
{#unauthorized-change-request__ul_hzt_kks_whb}

The ci.change.unplanned event that is generated automatically triggers
the creation of an Emergency type change request.

## Unauthorized change state flow {#unauthorized-change-request__section_unauth_state_flow}

An unauthorized change follows a different state flow from a standard change because the implementation has already occured:

1. On creation, the request enters the Review state and skips the schedule and implement states.
2. If you select Request Approval, the state returns to Authorize for approval.
3. After approval, the change goes to the Close state, and a post-implementation review task is created.
{#unauthorized-change-request__ol_hyy_n44_qkc}

For the standard change state flow, see [State progression for normal, standard, and emergency changes](https://www.servicenow.com/docs/hUc0dse44~pFsMnoGsDqRg "Each change request model progresses through a number of state values in a specific order.")

## Identify and review unauthorized changes {#unauthorized-change-request__section_identify_review}

With the help of the following details that are pre-populated on the form, you can identify and review the unauthorized change:

* The Unauthorized option is selected. This option indicates that the change is an unauthorized change.
* The Assignment group field is populated with Change Management.
* The Configuration item field is populated with the item that the unauthorized change was made for.
* The Description field is populated with the changed fields of the configuration item, including the CI field name and its new value.
{#unauthorized-change-request__ul_vzh_52f_xhb}  
An email notification is sent to the Assignment group, CI Item managed by, Owned by, and Assigned to members for review and approval. However, if there are many CI changes and there are no open change requests created to include the CIs, the system creates unauthorized change requests on these CIs. When this event occurs, the members receive numerous unauthorized change notification emails. In such a case, you can choose to disable these notifications. For more information, see [Disable unauthorized change
notification](https://www.servicenow.com/docs/8_XR5owzrMBST4YMzVygwA "You can choose to disable the generation of unauthorized change requests that you receive on any unauthorized change event. When a configuration item (CI) that is part of an application service is updated, the system identifies this update and verifies whether the updated CI is part of an open change request.").  
Note:  
Email notifications are sent only when there is an unplanned change on the CI that is part of an application service (discovered or manual service).

Because an authorized change records a change that was already implemented, the request enters the Review state directly, skipping the Schedule and Implement states. If you select Request Approval, the state returns to Authorize for sign-off before the request follows the regular process to close.

## Assign post-implementation review {#unauthorized-change-request__section_swz_b3s_whb}

When a change is implemented without approval, post-implementation review is necessary to
evaluate the risk and impact of the unauthorized change.

After the unauthorized change is approved, a change task is created with
State field as Review. This change task is
assigned to the Change Management group with the Short description
field as Post Implementation Review. The assigned members who receive
the notification can review and close the change task.

## Modify the unauthorized change setting {#unauthorized-change-request__section_f5n_xls_whb}

As a change manager, you can clear the Unauthorized check box to
convert the unauthorized change request to an emergency change request. When you clear the
check box, enter the reason for this modification in the Work notes
field.

If you are an ITIL user, clear the Unauthorized check box by
creating an outage from the task record with the Type field specified
as <kbd class="ph userinput">Outage</kbd>. For more information, see [Create an outage from a
task](https://www.servicenow.com/docs/mvAqLKB_L2hUp3Cd9xYmXg "Create an outage from a task record to understand the down time of a configuration item.").  
Note:  
When there is an unauthorized change without an outage record associated, then the state flow moves from Authorize to Review and skips the schedule or implement state. The state changes because the implementation has already happened for this change.
* **[Disable the creation of an unauthorized change request](https://www.servicenow.com/docs/8_XR5owzrMBST4YMzVygwA)**   
  You can choose to disable the generation of unauthorized change requests that you receive on any unauthorized change event. When a configuration item (CI) that is part of an application service is updated, the system identifies this update and verifies whether the updated CI is part of an open change request.
* **[Unauthorized change properties](https://www.servicenow.com/docs/LzWRaXbrDMQffh3_dVHk~g)**   
  Use the Unauthorized Change Properties page to turn on or turn off the unauthorized change capability, and to configure the criteria for additional unauthorized change properties.

**Related tasks**   

* [Create a change request from a configuration item (CI)](https://www.servicenow.com/docs/4y7hNM~B3BEbAckXOG6lOA "Create a change request from a list of configuration items (CIs), or add selected CIs from a list to a change record.")
* [Create a standard change request from the catalog](https://www.servicenow.com/docs/UhlImJGK8HJ~COLVaNb1YQ "Create a standard change request from a published catalog template.")
* [Copy a change request](https://www.servicenow.com/docs/oDcGhmCVrwjzbu_ww_qi8w "Copy the details of an active or canceled change request to a new change request.")
* [Create a change task](https://www.servicenow.com/docs/sdnhr_EIjQqLMn3oPPQKWQ "You can create change tasks for a change request. A change task is a piece of work related to the change request. For example, there can be tasks to plan the change, implement the change, and test, and review the work.")

