Configuring Simplified Change Management

concept brazil Updated Sep 10, 2026 7 min read configuring-change-management-experience-in-it-service-management.md
Raw file servicenow.com

Configure Change Management through a guided experience that walks you through the core setup areas required to make Change Management operational.

The setup provides an opinionated, wizard-driven experience with defaults pre-applied in some steps. Rather than building your configuration from scratch, you can configure by exception, accepting defaults where they apply and customizing only where your organization's needs differ.[Omitted video] Description: Change Management made simple

Simplified Change Management overview

Simplified Change Management offers the core functionality of the full Change Management application. It's purpose-built for organizations that need a fast, low-friction path to change governance without the complexity of an enterprise-scale deployment.

Compared to the standard Change Management application, the simplified experience reduces scope in three key ways:

  • Fewer change types to configure

    The standard change application supports a wide range of change types with individually configurable workflows, risk models, and approval chains. Simplified change focuses on the most common change patterns—Standard, Normal, and Emergency with prebuilt workflows that work with the base system, so you aren't required to design approval logic before you can go live.

  • Opinionated defaults instead of open-ended configuration

    The full change application gives you complete control over every configuration parameter, which requires significant ServiceNow expertise to set up correctly. Simplified change makes those decisions for you using defaults based on common practices. You only need to act where your organization's requirements genuinely differ from the defaults.

  • Guided setup instead of open configuration

    The standard change application is configured through multiple administration modules spread across the platform. Simplified change consolidates all required setup into a single, step-by-step guided setup experience within the Configuration Console, so you know what to configure next and can track your progress in one place.

Simplified Change Management is intended for organizations that are new to ServiceNow change governance, are transitioning from spreadsheet or email-based change tracking, or need to reach an operational state quickly without a dedicated implementation team. If your organization requires advanced workflow customization, complex multi-stage CAB structures, or integration with enterprise release management tools, the full Change Management application may be a better fit.

Configuration areas

Navigate the setup across the core configuration areas within the Configuration Console, each accessible from the ITSM fulfiller experience > Change Management section. You can move through the areas in any order, skip an area and return to it later as needed.

  • Forms

    Configures the change forms that IT fulfiller staff use to create and manage changes. For more information, see Configure team roles for Simplified Change Management

  • Lists

    Configures which columns appear in the change lists for the IT fulfiller staff. For more information, see Configure risk for Simplified Change Management

  • Team roles

    Defines who can approve, build, or review a change by mapping individuals and groups to their respective roles in the change process. For more information, see Configure team roles for Simplified Change Management.

  • Risk configuration

    Establishes how risk is assessed for change requests. Pre-configured risk assessment questions, responses, and score ranges are provided as defaults, allowing organizations to start with a working risk model and refine it over time as their change governance matures. For more information, see Configure risk for Simplified Change Management.

  • Change Advisory Board (CAB)

    Configures the CAB structure that governs change approvals. Admins define CAB membership, meeting schedules, and the types of changes that require CAB review. Default CAB role mappings are pre-applied to reduce initial setup effort. For more information, see Configure Change Advisory Board for Simplified Change Management.

  • Change models

    Specifies the templates and workflows used for each type of change—Standard, Normal, and Emergency. Base system change models are included as defaults. Admins can modify existing models or create new ones to reflect their organization's change types and workflows. For more information, see Configure change models for Simplified Change Management.

  • Change schedules

    Defines the maintenance windows and blackout periods that control when changes can be implemented. Default schedules are provided as a starting point and can be customized to align with the organization's operational calendar and service availability requirements. For more information, see Configure schedules for Simplified Change Management.

  • Notifications

    Configures when and how stakeholders are notified about change activity, approvals, and completions. Default notification rules cover the most common communication touchpoints in the change lifecycle and can be extended or suppressed based on organizational preferences. For more information, see Configure notifications for Simplified Change Management.

Roles required

You must have the Change Management Setup Administrator (sn_itsm_chg_admin.admin) role to configure all the sections of the Change Management setup. This role contains the following roles that can be assigned for access to specific sections:

Note: The following roles no longer automatically inherit the sn_ia_config.ia_user role. Users who need to configure the console must now be assigned both the appropriate Change Management role (for example, sn_itsm_chg_admin.forms_config) and the sn_ia_config.ia_user role explicitly. Existing roles aren't modified during upgrade, allowing you to maintain full control over assignment of elevated privileges. After upgrading, if you have previously relied on inherited access, you won't be able to configure the console until the sn_ia_config.ia_user role is assigned explicitly.

Role Description
sn_itsm_chg_admin.forms_config Grants access to review and configure change forms.
sn_chg_setup.lists_config Grants access to configure which columns appear in change lists.
sn_itsm_chg_admin.team_roles_config Grants access to configure team roles and group assignments.
sn_itsm_chg_admin.risk_config Grants access to configure risk assessment questions, scoring, and risk threshold bands.
sn_itsm_chg_admin.cab_config Grants access to configure Change Advisory Board membership, meeting schedules, and approval policies.
sn_itsm_chg_admin.change_models_config Grants access to configure change models, approvals, and change type behaviors.
sn_itsm_chg_admin.change_schedules_config Grants access to configure change windows, blackout periods, and maintenance schedules.
sn_itsm_chg_admin.notification_config Grants access to configure notifications.

Note: The parent role (sn_itsm_chg_admin.admin) uses the dotted suffix pattern, while child roles follow a underscore suffix pattern (for example, sn_itsm_chg_admin.team_roles_config). This is an intentional naming convention, not a typo.

Parent Topic:Configuring the fulfiller experience in Simplified IT Service Management

Search documentation
Search document titles and file paths on the brazil branch