---
sourceDocument: brazil Combined Product Files
sourceDocumentLink: https://www.servicenow.com/docs/r/delta-yokohama-brazil
Release :
- brazil
ft:locale :
- en-US
ft:publication_title :
- brazil Combined Product Files
ft:clusterId :
- delta3by
bundleId :
- delta3by
---
# Combined Incident Management release notes for upgrades from Yokohama to Brazil
# Combined Incident Management release notes for upgrades from Yokohama to Brazil {#ariaid-title1}
Release version: Brazil
Updated October 8, 2026
 14 minutes to read
Summarize
 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 Incident Management release notes for upgrades from Yokohama to Brazil
This consolidated release note provides ServiceNow customers with a comprehensive view of Incident Management updates across release families from Yokohama through Brazil.
It highlights new features, changes, security enhancements, role adjustments, and usability improvements relevant for upgrading and managing Incident Management effectively in ServiceNow.
Show full answer Show less
## Important Upgrade Information
* The ITSM Enhanced Security Features plugin is now automatically activated in Brazil upgrades, enforcing "deny unless authenticated" access controls on key ITSM tables to prevent unauthorized access. Reversion requires support intervention.
* Brazil introduces a scheduled job for automatic installation of licensed applications on new zboot instances.
* Pre- and post-upgrade tasks should be reviewed carefully to ensure smooth transitions.
## Key Features
* **User Role for Service Desk Agents:** The `snservicedeskagent` role streamlines tier 1 agent tasks and integrates additional roles when ITSM Gen AI is installed, enhancing operational efficiency.
* **Enhanced Security Model:** Deny-Unless ACLs restrict non-authenticated user access to incident-related tables, improving data protection.
* **Granular Admin Roles:** Introduced in Australia release for fine-grained configuration of incident, major incident, task outage, communication, and contact management features.
* **Form Channel for Response Templates:** Enables copying templates directly from incident forms for use in work notes or communications.
* **Auto Resolve On-Hold Incidents:** In Brazil, incidents on hold awaiting caller input can auto-resolve after configurable attempts and time intervals, enhancing incident lifecycle management.
* **Email Notification Link Redirection:** Incident and major incident email links can now open in Service Operations Workspace (SOW) rather than classic UI16, configurable via system properties.
* **Incident Reopening Enhancements:** Agents, callers, and requesters can reopen resolved incidents via classic UI16, SOW, or Portal UIs, improving incident handling flexibility.
* **Search Performance Improvements:** Configuration Items (CIs) in incident forms are now alphabetically sorted by CI name for faster and cleaner UI experience.
* **Coral Theme and Accessibility:** Coral is the new default theme with a dark mode option and includes accessibility enhancements such as keyboard navigation, screen reader support, and content reflow for better usability.
* **Incident Task Record Locking:** Closed incident tasks cannot be edited, protecting data integrity and audit compliance.
## Role and Permission Adjustments
* Brazil removes the inherited `itil` role from Incident Manager, Major Incident Manager, and Communication Plan Manager roles, replacing it with more focused granular roles for tighter access control (applicable to zboot instances).
* Communication Plan Viewer role permissions have been adjusted to align with updated role structures.
* Access control for communication channel definitions now depends on specific roles and script-based state checks rather than the `itil` role.
## Behavior Changes and Enhancements
* Email notifications now support consistent redirection behavior to SOW with updated templates matching Next Experience themes.
* Incident and problem workflows improved to add work notes with fix or workaround details instead of customer-visible comments, configurable via system properties.
* Auto-close resolved incidents now uses business days instead of calendar days for better alignment with organizational policies.
## Accessibility and UI Improvements
* Improvements in keyboard navigation, voice-over support, color contrast, and target sizes across Incident Management and Major Incident Management interfaces benefit users relying on Assistive Technologies.
* Content reflow allows zooming up to 400% without loss of functionality, aiding users with low vision or varying device types.
## Removed and Deprecated Features
No Incident Management features were removed or deprecated between Yokohama and Brazil releases.
## Activation and Requirements
Incident Management remains active by default across all releases. No additional browser or localization requirements were introduced or changed between Yokohama and Brazil.
## Practical Benefits for ServiceNow Customers
* Improved security controls automatically protect incident data from unauthorized access without manual configuration.
* The new service desk agent role simplifies permissions and task flows for tier 1 support teams.
* Enhanced email notification link handling improves user experience by directing users to preferred interfaces.
* Role restructuring aligns permissions with operational needs, reducing unnecessary access and improving governance.
* Accessibility and UI enhancements enable a more inclusive, user-friendly environment for all users.
* Automation of incident lifecycle steps, such as auto-resolving on-hold incidents and auto-closing resolved incidents, reduces manual overhead and speeds resolution processes.
Consolidated page of all release notes for Incident Management from Yokohama to Brazil.
## How to use this page
To help you prepare for your upgrade, we have combined the cross-family Incident Management release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama 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 Incident Management to Brazil
Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed.
{#dfrn3-incidentmanagement-summary__entry__2}
| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| 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 Incident Management.
{#dfrn3-incidentmanagement-summary__entry__12}
| Release | Release notes |
|-|-|
| Yokohama | [User role for service desk agents](https://www.servicenow.com/docs/access?context=inci-roles-instld-itsm-roles&family=yokohama&ft:locale=en-US) : With the sn_service_desk_agent user role, increase the operational efficiency by streamlining the process of asking about, gathering, and verifying information, as well as delivering quick resolutions. This role is designed for tier 1 service desk agents and is accessible when the ITSM Roles plugin (com.snc.itsm.roles) installed. The sn_service_desk_agent role includes the following user roles: * sn_incident_write * sn_problem_write * sn_change_write * sn_request_write * tracked_file_reader Additionally, with the installation of the ITSM Gen AI (com.sn.itsm.gen.ai) plugin, the knowledge_user, and now_assist_panel_user roles are integrated within the sn_service_desk_agent role. The sn_service_desk_agent role can be used starting with SOW version 6.1. [Enhanced security model adoption for incident tables](https://www.servicenow.com/docs/access?context=activate-itsm-enhanced-security-inci-mangmnt&family=yokohama&ft:locale=en-US) : Help prevent unauthorized access to incident-related tables using Deny-Unless ACLs. A Deny-Unless authentication ACL restricts access for a non-authenticated user, such as a public role user. Without access, the user can't perform any actions on incident-related tables, including reading, writing, deleting, creating, or accessing the report view. This feature is activated automatically and applicable on the following incident-related tables: * kb_template_incident_kcs_articl * kb_template_incident_kcs_template Additionally, this feature is available on the following incident-related tables of new or zBoot instances after installing the ITSM Enhanced Security Features (com.snc.itsm.enhanced_security) plugin: * incident * incident_task * task_ci * task outage The ITSM Enhanced Security Features (com.snc.itsm.enhanced_security) plugin can be installed and activated by an admin via a support request. Existing or upgrade users must test and evaluate the results in their non-production instance, and then install the plugin and implement the security change in their production instance. For more information, see [Deny-Unless ACL](https://www.servicenow.com/docs/access?context=acl-denial-behavior&family=yokohama&ft:locale=en-US). |
| Zurich | No updates for this release. |
| Australia | [Introduction of granular admin roles](https://www.servicenow.com/docs/access?context=req-itsm-roles-inci-mgmt&family=australia&ft:locale=en-US) : Configure all the incident, major incident, task outage and related communication features for both UI16 and SOW using the following granular admin roles: * sn_incident_admin: Configure all Incident Management features including incident management properties. * sn_mim_admin: Configure all Major Incident Management features including major incident properties and trigger rules. * sn_tcm_admin: Configure all Task Communications Management features including communication plans and tasks. * sn_iam_admin: Configure all Incident Communications Management features including creating, editing, or canceling incident communication plan, communication task, and managing contact information. Additionally, this role can administrate all Incident Communications Management capabilities." * sn_contact_admin: Configure all Contact Management features including creating and editing contact definitions, contact responsibilities, configuration of MI users, recipient lists, and groups. * sn_task_outage_admin: Configure all Task Outage features including the mapping between the Task \[task\] table and the Outage \[cmdb_ci_outage\] table. [Form channel for response templates](https://www.servicenow.com/docs/access?context=working-incident-record-form&family=australia&ft:locale=en-US) : The form channel is added to the Need more information and Schedule meeting response templates. The channel enables you to access the response templates from the incident record, copy the response templates texts to the clipboard from the incident form to be shared in the work notes, comments or other communication channels. |
| Brazil | [Scheduled job for auto installation of application](https://www.servicenow.com/docs/access?context=activate-major-incident-management-plugin&family=brazil&ft:locale=en-US) : A scheduled job is now available that executes a batch installation on a new instance to automatically install applications such as Major Incident Management only if you have the necessary entitlements for the application. This is applicable only on the newly provisioned zboot instance. [Auto resolve On-hold incident](https://www.servicenow.com/docs/access?context=incident-management-properties&family=brazil&ft:locale=en-US) : When an incident is put to On-Hold state with reason as Awaiting Caller Information, a notification for input response is sent to the caller for a specific number of attempts or strikes within specific time intervals. The business days are considered for a time interval. If the caller adds a comment on the Service Portal or replies to the notification email, the incident automatically moves to the In Progress state, and the assigned agent receives a notification. If the caller does not respond after all attempts are exhausted, the incident is automatically resolved with the resolution code Resolved - No response from caller and a resolution note indicating no caller response. You can control the number of attempts or strikes and the time interval between the attempts, using the following incident properties: * The number of attempts made before an incident that is waiting for a caller response is automatically resolved if no reply is received. Setting this value to 0 will disable the automation for this instance - By default, the value is set to 3. * Wait period in business days between two attempts. Incidents will be auto resolved after all the attempts are completed - By default, the value is set to 1. This is applicable only in the zboot instances. |
[ ]
## Changes
Between your current release family and Brazil, some changes were made to existing Incident Management features.
{#dfrn3-incidentmanagement-summary__entry__22}
| Release | Release notes |
|-|-|
| Yokohama | [Email redirection behavior for major incident email notification links](https://www.servicenow.com/docs/access?context=email-notif-redirt-inci-major-inci&family=yokohama&ft:locale=en-US) : In major incident email notifications, you can now decide where the links to a major incident record are redirected. Instead of a major incident record automatically opening in the classic UI16 interface in Major Incident Management, the record can be opened in SOW. The major incident record link in an email notification opens in SOW only if the following conditions are met: * The Redirect SOW Email notification (sow_email_notification_redirect) property is set to true. Setting this property to true enables the email redirection behavior for all tables including major incident. * The Redirect SOW Email notification for Major Incident Management (sn_major_inc_mgmt.sow_email_notification_redirect.mim) property is set to true. * You have the sn_sow_user role. The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior. [Email redirection behavior for incident email notification links](https://www.servicenow.com/docs/access?context=email-notif-redirt-inci-major-inci&family=yokohama&ft:locale=en-US) : In incident email notifications, you can now decide where the links to an incident record are redirected. Instead of an incident record automatically opening in the classic UI16 interface in Incident Management, the record can be opened in SOW. The incident record link in an email notification opens in SOW only if you have the sn_sow_user role and any of the following conditions are met: * The Redirect SOW Email notification (sow_email_notification_redirect) property is set to true. Setting this property to true enables the email redirection behavior for all tables including incident. * The Redirect SOW Email notification for Incident Management (sow_email_notification_redirect.incident) property is set to true. You can create this property if you want to enable or restrict the email redirection behavior specifically for the incident table. This property, if created and set, overrides the Redirect SOW Email notification (sow_email_notification_redirect) base system property. The ITSM Notifications Redirection (com.snc.itsm.notifications_redirection) plugin is installed and activated automatically to support this behavior. To ensure consistency, the email notification templates for incident tasks are also updated to send the notification from Service Operations Workspace (SOW) in the same format as sent from classic UI16 interface similar to incident. Also, the template theme is updated to match the Next Experience theme. [Incident and problem workflow changes](https://www.servicenow.com/docs/access?context=incident-management-properties&family=yokohama&ft:locale=en-US) : When a problem is fixed and the Share fix option is triggered, the event is added to the Work notes (Private) field instead of the Additional comments (Customer visible) field for the incident associated with the problem record. This feature is available in the base system for the new customers. For existing or upgrade customers, admin must set the Communicate problem workaround to incident worknotes (com.snc.incident.communicate_prb_workaround_to_inc_worknotes) system property to true to enable the feature. [Changes in the reopening incident behavior](https://www.servicenow.com/docs/access?context=reopening-incident&family=yokohama&ft:locale=en-US) : Enable the agents with incident write access, callers, requesters, or Opened by end users to reopen a resolved incident. Both the caller and the requester can view and use the Reopen option on the incident classic UI16 form and the Portal UIs, such as Service Portal and Employee Service Center (ESC) portal. An agent can view and use the Reopen option on the incident classic UI16 form to reopen any incident that is assigned to them or to other agents. However, on the Portal UI, an agent can only view and use the Reopen option to reopen an incident if it's assigned to them. [Sorting CIs in incident forms](https://www.servicenow.com/docs/access?context=create-an-incident&family=yokohama&ft:locale=en-US) : The search performance of the available CIs for the Configuration item field on an incident form is enhanced to promote a clean UI and quick loading and sorting of the CIs. The search results that list the CIs are sorted alphabetically by CI name instead of by CI class and then CI name. The ref_ac_order_by=sys_class_name attribute is removed from the default attributes on the cmdb_ci field of the Task \[task\] table, which increases the performance of the field. This change is applicable to new and existing users using the default attributes. You can use the Override attributes option to restrict this change for any required child tables that extend to the cmdb_ci field of the Task \[task\] table. |
| Zurich | Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Incident task record behavior changes](https://www.servicenow.com/docs/access?context=create-incident-task&family=zurich&ft:locale=en-US) : When an incident task is closed, you can no longer edit the field values in the incident task form. Disabling the fields helps prevent any further updates or modifications to closed incident tasks, reducing audit risks. [Incident and problem workflow changes](https://www.servicenow.com/docs/access?context=working-incident-record-form&family=zurich&ft:locale=en-US) : When a problem record is linked to an incident or multiple incidents, the incident and problem workflow has the following enhancements: * When a fix or workaround is shared from the problem record, an event is added in the activity stream of the incident record as work notes. The event includes a brief description of the provided fix or workaround and a link to the problem record. * When a Known Error (KE) article is linked to the problem record, an event is added in the activity stream of the incident record as work notes. The event includes the links to the problem record and the KE article. |
| Australia | No updates for this release. |
| Brazil | [Incident manager role changes](https://www.servicenow.com/docs/access?context=inci-roles-instld-itsm-roles&family=brazil&ft:locale=en-US) : The inherited itil role is now removed from the incident manager \[incident_manager\] role and replaced with the incident_write role. The is applicable only for the zboot instances. This change restricts access to incident records only, aligning permissions with the intended scope of the role and reducing unnecessary access to unrelated process areas. [Major incident manager and communication plan manager role changes](https://www.servicenow.com/docs/access?context=installed-with-mim&family=brazil&ft:locale=en-US) : The major incident manager \[major_incident_manager\] and communication plan manager \[sn_comm_management.comm_plan_mgr\] roles no longer inherit the itil role. Instead, the roles inherit the sn_incident_write, sn_problem_write, sn_change_write, sn_request_write granular roles from the ITSM Roles plugin (com.snc.itsm.roles). This is applicable only for the zboot instances. For the upgrade instances, the itil role remains inherited. Additionally, the sn_incident_write, sn_problem_write, sn_change_write, and sn_request_write granular roles are added if the ITSM Roles plugin (com.snc.itsm.roles) is installed. [Communication plan viewer role changes](https://www.servicenow.com/docs/access?context=components-installed-with-icm&family=brazil&ft:locale=en-US) : The sn_dex_desktop.notification_template_admin role is now removed from the communication plan viewer \[sn_comm_management.comm_plan_viewer\] role and added to the sn_incident_write role when ITSM Roles plugin (com.snc.itsm.roles) is installed. In case, ITSM Roles plugin (com.snc.itsm.roles) is not installed, the sn_dex_desktop.notification_template_admin role is added to the itil role. These role changes are applicable only for the zboot instances. [Itil role check removal from comm_channel create and write ACLs](https://www.servicenow.com/docs/access?context=components-installed-with-icm&family=brazil&ft:locale=en-US) : The itil role reference check is now removed from the comm_channel create and write ACLs. Create and access to the communication channel definition in the incident communication tasks is based on the commTaskGr.state.canWrite script and if you have the following roles: * Communication plan manager \[sn_comm_management.comm_plan_mgr\] * Communication plan admin \[sn_comm_management.comm_plan_admin\] * Task communication management admin \[sn_tcm_admin\] * ITSM granular roles such as sn_incident_write and the user assigned to the incident communication task and plan. [Auto close resolved incidents behavior changes](https://www.servicenow.com/docs/access?context=incident-management-properties&family=brazil&ft:locale=en-US) : The resolved incidents are now automatically closed after a specific number of business days instead of calendar days. You can use configure the number of business days using Number of days (integer) after which Resolved incidents are automatically closed. Zero (0) disables this feature \[glide.ui.autoclose.time\] property. This changes helps the maintaining the internal organizational policies. |
[ ]
## Removed
Between your current release family and Brazil, some Incident Management features or functionality were removed.
{#dfrn3-incidentmanagement-summary__entry__32}
| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]
## Deprecations
Between your current release family and Brazil, some Incident Management features or functionality were deprecated.
{#dfrn3-incidentmanagement-summary__entry__42}
| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]
## Activation information
Review information on how to activate Incident Management.
{#dfrn3-incidentmanagement-summary__entry__52}
| Release | Release notes |
|-|-|
| Yokohama | Activation information : Incident Management is a ServiceNow AI Platform feature that is active by default. |
| Zurich | Activation information : Incident Management is a ServiceNow AI Platform feature that is active by default. |
| Australia | Activation information : Incident Management is a ServiceNow AI Platform feature that is active by default. |
| Brazil | Activation information : Incident Management is a ServiceNow AI Platform feature that is active by default. |
[ ]
## Additional requirements
If any additional requirements were introduced or changed for Incident Management we have noted them here.
{#dfrn3-incidentmanagement-summary__entry__62}
| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]
## Browser requirements
If any specific browser requirements were introduced or changed for Incident Management we have noted them here.
{#dfrn3-incidentmanagement-summary__entry__72}
| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]
## Accessibility information
Review details on accessibility information for Incident Management, such as specific requirements or compliance levels.
{#dfrn3-incidentmanagement-summary__entry__82}
| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | Accessibility information : Dark theme : The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. |
| Australia | No updates for this release. |
| Brazil | Accessibility information : * Accessibility improvements were made to the Incident Management UI16 form across the full form lifecycle, including keyboard navigation, voice-over support, color contrast, and minimum target sizes. These updates benefit users who rely on screen readers or other Assistive Technology (AT), keyboard-only users, and users with low vision. * Accessibility improvements were made to the Major Incident Management UI List component, record pages and Major Incident workbench tabs, including keyboard navigation and screen reader support. These updates benefit users who rely on screen readers or other Assistive Technology (AT), keyboard-only users, and users with low vision. * Reflow support for Incident Management and Major Incident Management: 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. |
[ ]
## Localization information
If there are specific localization considerations for Incident Management we have noted them here.
{#dfrn3-incidentmanagement-summary__entry__92}
| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
| Brazil | No updates for this release. |
[ ]
## Highlight information
If there are specific highlight considerations for Incident Management we have noted them here.
{#dfrn3-incidentmanagement-summary__entry__102}
| Release | Release notes |
|-|-|
| Yokohama | * Increase the operational efficiency of the tier 1 service desk agents with the dedicated sn_service_desk_agent role. * Control whether an incident or major incident record link in an email notification redirects you to the record in the classic UI16 interface or Service Operations Workspace (SOW). * Enable agents with incident write access, callers, requesters, and Opened by end users to reopen a resolved incident from the Incident Management classic UI16 form, SOW, or Portal UIs. * Restrict unauthorized access to incident-related tables using deny ACLs. * Search for a configuration item (CI) in a list alphabetized by the CI name with an improved search performance. See [Incident Management](https://www.servicenow.com/docs/access?context=c_IncidentManagement&family=yokohama&ft:locale=en-US) for more information. |
| Zurich | * Help prevent changes to closed incident tasks to promote data integrity and to maintain a clear audit. * Manage and resolve incidents effectively with the incident and problem workflow enhancements. * Coral is the new default theme for Next Experience and Core UI, offering a more user-friendly experience. See [Incident Management](https://www.servicenow.com/docs/access?context=c_IncidentManagement&family=zurich&ft:locale=en-US) for more information. |
| Australia | * Perform the incident, major incident, task outage, and related communication features configurations using granular admin roles. * Enhance communication capabilities with the form channel added to response templates. See [Incident Management](https://www.servicenow.com/docs/access?context=c_IncidentManagement&family=australia&ft:locale=en-US) for more information. |
| Brazil | * Log incidents in the instance or by sending email. * Classify incidents by impact and urgency to prioritize work. * Assign to appropriate groups for quick resolution. * Escalate as necessary for further investigation and resolution. * Use reports to monitor, track, and analyze service levels and improvement. See [Incident Management](https://www.servicenow.com/docs/access?context=c_IncidentManagement&family=brazil&ft:locale=en-US) for more information. |
[ ]