---
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


---

# MIM components

# Components installed with Incident Management - Major Incident Management {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Components installed with Incident Management - Major Incident Management

Activating the Incident Management - Major Incident Management plugin installs several essential components including tables and user roles designed to support the management of major incidents within ServiceNow.
These components enable streamlined processes for identifying, approving, communicating, and resolving major incidents effectively.
Show full answer Show less  

## Key Features

* **Roles Installed:** Specialized roles are installed to ensure proper governance and operational control of major incidents:
  * **Major Incident Manager \[mimmanager\]:** Responsible for initiating, approving, rejecting, demoting, and closing major incidents. This role oversees the incident lifecycle, assigns resolution groups, and manages communication plans. It inherits granular ITSM roles such as *snincidentwrite* , *snproblemwrite* , *snchangewrite* , and *snrequestwrite* starting from the Brazil release for zboot instances.
  * **Major Incident Admin \[snmimadmin\]:** Configures all major incident management features, including properties and trigger rules. It inherits roles including *mimmanager* and related administrative privileges.
  * **Communications Manager \[communicationmanager\]:** Manages stakeholder communications during major incidents, creates and edits communication plans, and inherits similar granular ITSM roles as the Major Incident Manager from Brazil release onward.
  * **Incident Manager \[incidentmanager\]:** An existing role with expanded responsibility to manage incident properties and major incident trigger rules, and to create/edit communication plan definitions.
* **Tables Installed:**
  * **Major Incident Trigger Rules \[majorincidenttriggerrule\]:** Stores rules that determine when an incident qualifies as a major incident, extending the Application File \[sysmetadata\] table.

## Practical Implications for ServiceNow Customers

By leveraging these installed components, ServiceNow customers can effectively implement and manage major incident processes with defined roles and automated trigger rules. The granular permission model enhances security and access control, especially from the Brazil release onward. Communication management capabilities ensure clear stakeholder engagement throughout the incident lifecycle, helping to minimize business impact during major incidents.  
Several types of components are installed with activation of the Incident Management -
Major Incident Management plugin, including tables and user roles.
Note:  
The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see [Find components installed with an
application](https://www.servicenow.com/docs/access?context=find-components&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).

Demo data is available for this feature.

## Roles installed {#installed-with-mim__section_wly_yyh_wdb}

{#installed-with-mim__table_u1t_gb1_wdb__entry__3}

| Role title \[name\] | Description | Contains roles |
|-|-|-|
| Major incident manager \[mim_manager\] | A major incident manager can: * Initiate the major incident process by assessing and approving major incident candidates or creating a major incident. * Reject a major incident candidate. * Demote a major incident after it is accepted so that the incident can be handled as a regular incident. * Maintain the ownership and accountability for the life cycle of the incident. * Identifies the users and groups to be involved in the resolution activities. * Creates adhoc communication plans and tasks. * Edits a communication plan that is attached to a major incident. * Close a major incident. {#installed-with-mim__ul_bxf_5vm_zcb} | * sn_comm_management.comm_plan_viewer * sn_comm_management.comm_plan_manager * ia_admin * sn_incident_write * sn_problem_write * sn_change_write * sn_request_write * itil Note: Starting Brazil, for zboot instances, the major incident manager \[major_incident_manager\] role no longer inherit the itil role. Instead, it inherits the sn_incident_write, sn_problem_write, sn_change_write, sn_request_write granular roles from the ITSM Roles plugin (com.snc.itsm.roles). 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. |
| Major incident admin \[sn_mim_admin\] | Configure all Major Incident Management features including major incident properties and trigger rules. | * mim_manager * sn_iam_admin * sn_sow_mim.sn_mim_sow_admin {#installed-with-mim__ul_hz4_yvx_f3c} |
| Communications manager \[communication_manager\] | * Manages communications for major incidents and is responsible for communicating with all stakeholders. * Creates adhoc communication plans and tasks. * Edits a communication plan that is attached to a major incident. {#installed-with-mim__ul_qjg_q5d_kdb} | * sn_comm_management.comm_plan_viewer * ia_admin * sn_incident_write * sn_problem_write * sn_change_write * sn_request_write * itil Note: Starting Brazil, for zboot instances, the Communications manager \[communication_manager\] role no longer inherit the itil role. Instead, it inherits the sn_incident_write, sn_problem_write, sn_change_write, sn_request_write granular roles from the ITSM Roles plugin (com.snc.itsm.roles). 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. |
| Incident Manager \[incident_manager\] (Existing role with added responsibilities) | * Manages incident properties and major incident trigger rules. * Can create and edit Communication Plan Definitions. {#installed-with-mim__ul_utd_t5d_kdb} | None |
[ ]

{#installed-with-mim__table_u1t_gb1_wdb}

## Tables installed {#installed-with-mim__section_s1x_dzh_wdb}

{#installed-with-mim__table_fbz_45z_vdb__entry__2}

| Table | Description |
|-|-|
| Major Incident Trigger Rules \[major_incident_trigger_rule\] | This table extends the Application File \[sys_metadata\] table and stores the major incident trigger rules. |
[ ]

{#installed-with-mim__table_fbz_45z_vdb}