---
sourceDocument: brazil Combined Product Files
sourceDocumentLink: https://www.servicenow.com/docs/r/delta-australia-brazil

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - brazil Combined Product Files

ft:clusterId :

    - delta3ba

bundleId :

    - delta3ba


---

# Combined Change Management release notes for upgrades from Australia to Brazil

# Combined Change Management release notes for upgrades from Australia to Brazil {#ariaid-title1}

Release version: Brazil  
Updated October 8, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 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 Combined Change Management Release Notes for Upgrades from Australia to Brazil

This consolidated guide assists ServiceNow customers in preparing for Change Management upgrades from the Australia to Brazil release versions.
It details key new features, upgrade considerations, and enhancements relevant to Change Management within the IT Service Management (ITSM) framework, focusing on functionality improvements, security, compliance, and usability.
Show full answer Show less  

## Important Upgrade Information

* **ITSM Enhanced Security Features Plugin:** Automatically activated during upgrades to both Australia and Brazil releases. This plugin enforces "deny unless authenticated" access control list (ACL) rules on several ITSM tables to enhance security. Customers can revert to previous access control settings by contacting ServiceNow Support.

## New Features

* **Granular Admin Role (Australia):** Introduces the `snchangeadmin` role, replacing broader admin and ITIL roles with a focused permission set for configuring Change Management features.
* **Exclude Change Requests from Conflict Check (Australia):** Enables exclusion of specific change requests from conflict detection to streamline change processing.
* **Change Templates and Enhanced Data Model (Australia):** Allows creation and management of change templates to standardize common changes. The enhanced data model supports better categorization and role-based access without impacting existing standard changes.
* **Compliance Dynamic Schema (Brazil):** Stores risk and compliance data as dynamic name-value pairs rather than static table columns, allowing flexible compliance tracking tailored to regulated industries.
* **Change Lockdown (Brazil):** Enables pausing of all or selected in-flight change requests during critical events, with automatic conflict detection marking changes inside lockdown periods.
* **Scaled Change (Brazil):** Supports complex environments by generating and managing child change records for multiple configuration items, integrating scheduling, conflict detection, and approval workflows.
* **ITIL Change Process Assignment and State Field Policies (Brazil):** Assign ITIL change processes to models and enforce field-level policies (mandatory/read-only) based on change request states to improve compliance and process control.

## Changes, Removals, and Deprecations

No significant changes, removals, or deprecations were introduced between the Australia and Brazil releases for Change Management.

## Activation and Requirements

* Change Management is an AI Platform feature active by default in both Australia and Brazil releases.
* No additional requirements or specific browser changes were introduced in these releases.

## Accessibility Enhancements

The Create a Change Request page now supports reflow, allowing users to zoom up to 400% without losing content or functionality. Page layouts automatically transform into a vertical stacked view to assist users with low vision or diverse device setups. This feature can be disabled via system properties as needed.

## Practical Benefits for ServiceNow Customers

* **Security:** Enhanced ACLs improve data protection for change management records automatically after upgrade.
* **Administration:** Granular roles simplify permission management, reducing risk of broad access.
* **Change Efficiency:** Excluding certain changes from conflict detection and using change templates standardizes and accelerates change creation and compliance.
* **Compliance and Risk:** Dynamic schema allows flexible tracking of compliance attributes relevant to regulated industries without schema changes.
* **Change Control:** Change lockdown and scaled change features enable better handling of critical events and large, complex change scenarios.
* **Process Customization:** Assigning ITIL processes to change models and enforcing state-based field policies facilitate tailored workflows and governance.
* **Accessibility:** Improved page zoom and layout reflow support inclusive access for users with varying needs.

These enhancements provide customers with more precise control over Change Management processes, improved security and compliance handling, and better user experience, enabling smoother upgrades and more effective IT service change governance.  
Consolidated page of all release notes for Change Management from Australia to Brazil.

## How to use this page

To help you prepare for your upgrade, we have combined the cross-family Change Management release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Australia to Brazil.  
Tip:  
If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

## Important information for upgrading Change Management to Brazil

Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed.  
{#dfrn3-changemanagement-summary__entry__2}

| Release | Release notes |
|-|-|
| Australia | Upgrade information :   The ITSM Enhanced Security Features plugin (com.snc.itsm.enhanced_security) is now activated automatically when you upgrade to the Australia release. Previously, the plugin was activated only on new instances. Activating the plugin adds "deny unless authenticated" access control list (ACL) rules to several IT Service Management tables. To revert to the pre-upgrade behavior, contact ServiceNow Support for a list of ACLs to deactivate on specific tables. As a last resort, Support can run a script that deactivates all the new ACLs. |
| Brazil | Upgrade information :   The ITSM Enhanced Security Features plugin (com.snc.itsm.enhanced_security) is now activated automatically when you upgrade to the Brazil release. Previously, the plugin was activated only on new instances. Activating the plugin adds "deny unless authenticated" access control list (ACL) rules to several IT Service Management tables. To revert to the pre-upgrade behavior, contact ServiceNow Support for a list of ACLs to deactivate on specific tables. As a last resort, Support can run a script that deactivates all the new ACLs. |
[ ]

## New features

Between your current release family and Brazil, new features were introduced for Change Management.  
{#dfrn3-changemanagement-summary__entry__8}

| Release | Release notes |
|-|-|
| Australia | [Granular admin role](https://www.servicenow.com/docs/access?context=installed-with-cm-itsm-roles&family=australia&ft:locale=en-US) :   Assign the single feature-specific granular sn_change_admin role to users to grant permission to configure Change Management features and system properties. This role replaces the previous general admin and ITIL roles. The sn_change_admin role includes the sn_change_writer, change_manager, and sn_change_cab.cab_manager roles. [Exclude change request records from conflict check](https://www.servicenow.com/docs/access?context=configure-conflict-properties&family=australia&ft:locale=en-US) :   Exclude change requests from the conflict check process by setting the Exclude from conflict detection field to true. This setting also means that the change record is not displayed as a conflicting change when conflict checker is run on other change records. [Create change templates](https://www.servicenow.com/docs/access?context=create-change-template&family=australia&ft:locale=en-US) :   Control mandatory and read-only fields for change models by configuring change templates and defining template field policies. Change templates provide baseline standardization for common changes, making changes easier to create as well as driving a higher standard of change and compliance. Similar to the concepts used for existing standard change templates, templates used for change models can be proposed, reviewed, versioned, or retired. [Enhanced data model for change templates](https://www.servicenow.com/docs/access?context=change-data-model&family=australia&ft:locale=en-US) :   Use the enhanced data model that supports better categorization and role-based access for change templates for all change models automatically. This feature is optional for newly created standard changes. This data model does not impact the existing standard change catalog and migration of these standard changes is not required. |
| Brazil | [Compliance dynamic schema](https://www.servicenow.com/docs/access?context=compliance-dynamic-schema&family=brazil&ft:locale=en-US) :   Store risk and compliance details on change requests without adding columns to the Change Request table. Compliance dynamic schema saves these details as name and value pairs in a single field using the platform Dynamic Schema feature. Regulated industries can capture information such as whether a change handles personal data, whether an audit trail is required, and how long a rollback takes. The base system includes example dynamic categories such as Risk and Compliance, Financial Risk and Compliance, and SaaS/Cloud Security Compliance, and example attributes covering areas such as audit trail, downtime, estimated impacted users, lead time, rollback time, and compliance. You can deactivate the examples and define categories and attributes that match your organization's compliance requirements. You can also read and update attribute values from scripts, including risk condition scripts and business rules, using the dynamic schema scripting API. [Change lockdown](https://www.servicenow.com/docs/access?context=change-lockdown&family=brazil&ft:locale=en-US) :   Change lockdown allows change managers to pause all or a subset of in-flight change requests. Use it during major unplanned IT, critical, or financial events. [Change lockdown conflict detection](https://www.servicenow.com/docs/access?context=lockdown-conflict-detection&family=brazil&ft:locale=en-US) :   Automatically flag change requests that overlap an active lockdown period. Conflict detection runs alongside maintenance window and blackout window checks. Any change request inside a lockdown is marked as an Inside Change Lockdown conflict and placed on hold. Reschedule it outside the lockdown period to clear the conflict and continue processing. [Scaled change](https://www.servicenow.com/docs/access?context=scaled-change-overview&family=brazil&ft:locale=en-US) :   Scaled Change extends change management to complex environments with many configuration items. A single Scaled Change generates and coordinates child change records for every affected configuration item. It uses scheduling intelligence, conflict detection, and approval workflows to keep large-scale changes on track from planning through closure. [ITIL change process assignment for change models](https://www.servicenow.com/docs/access?context=itil_change_process_models&family=brazil&ft:locale=en-US) :   Assign an ITIL change process to a change model so the ChangeRequest API uses that model when it creates a matching change request. [State field policies for change models](https://www.servicenow.com/docs/access?context=state-field-policies-change-models&family=brazil&ft:locale=en-US) :   Use state field policies to make change request fields mandatory or read-only at each state in a change model. Policies are enforced on the form when a change request is created or updated. |
[ ]

## Changes

Between your current release family and Brazil, some changes were made to existing Change Management features.  
{#dfrn3-changemanagement-summary__entry__14}

| Release | Release notes |
|-|-|
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Removed

Between your current release family and Brazil, some Change Management features or functionality were removed.  
{#dfrn3-changemanagement-summary__entry__20}

| Release | Release notes |
|-|-|
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Deprecations

Between your current release family and Brazil, some Change Management features or functionality were deprecated.  
{#dfrn3-changemanagement-summary__entry__26}

| Release | Release notes |
|-|-|
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Activation information

Review information on how to activate Change Management.  
{#dfrn3-changemanagement-summary__entry__32}

| Release | Release notes |
|-|-|
| Australia | Activation information :   Change Management is a ServiceNow AI Platform feature that is active by default. The Change Management plugins listed are activated by default. |
| Brazil | Activation information :   Change Management is a ServiceNow AI Platform feature that is active by default. The Change Management plugins listed are activated by default. |
[ ]

## Additional requirements

If any additional requirements were introduced or changed for Change Management we have noted them here.  
{#dfrn3-changemanagement-summary__entry__38}

| Release | Release notes |
|-|-|
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Browser requirements

If any specific browser requirements were introduced or changed for Change Management we have noted them here.  
{#dfrn3-changemanagement-summary__entry__44}

| Release | Release notes |
|-|-|
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Accessibility information

Review details on accessibility information for Change Management, such as specific requirements or compliance levels.  
{#dfrn3-changemanagement-summary__entry__50}

| Release | Release notes |
|-|-|
| Australia | Accessibility information : Reflow for Create a change request page :   The Create a change request page now supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. Additionally, content can be enlarged without scrolling in two dimensions at a width equivalent to 320 CSS pixels or a height equivalent to 256 CSS pixels. Page layouts are transformed into a vertical, stacked view automatically when users increase browser zoom to 400%. This enhancement helps users with low vision or who have trouble seeing web content in a browser due to monitor size, device type, poor lighting, or other situations. Reflow can be turned off with a system property for instances, experiences, and pages. |
| Brazil | Accessibility information :   Reflow support for the Create a change request page: Content can be zoomed up to 400% through your browser settings, with page layouts automatically transforming into a vertical, stacked view without loss of content or functionality. This enhancement helps users with low vision or who have trouble seeing web content due to monitor size, device type, poor lighting, or other situations. Reflow can be turned off with a system property for instances, experiences, and pages. |
[ ]

## Localization information

If there are specific localization considerations for Change Management we have noted them here.  
{#dfrn3-changemanagement-summary__entry__56}

| Release | Release notes |
|-|-|
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]

## Highlight information

If there are specific highlight considerations for Change Management we have noted them here.  
{#dfrn3-changemanagement-summary__entry__62}

| Release | Release notes |
|-|-|
| Australia | * Configure the properties in Change Management application using the sn_change_admin role. * Manage conflict detection for change request using the new Exclude from conflict detection option. * Configure change templates with a specific change model. * Use change templates to manage the change request creation process. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=australia&ft:locale=en-US) for more information. |
| Brazil | * Control the full change lifecycle from request to closure using a structured workflow that reduces IT service disruption. * Define change models using custom state models, state transitions, and transition conditions. Out-of-the box change models include ITIL change models for Standard, Normal, or Emergency changes with dedicated approval paths. * Use machine learning to assess change risk and suggest standard change templates. * Run agentic AI workflows through a conversational interface. Use it to plan changes, assess conflicts, assess change quality, schedule changes, suggest configuration items, create outages, and generate standard change template proposals. * Track team performance with the Change Success Score, which uses historical data to predict successful change completion. This feature requires an ITSM Professional subscription. See [Change Management](https://www.servicenow.com/docs/access?context=c_ITILChangeManagement&family=brazil&ft:locale=en-US) for more information. |
[ ]


