Configuring SPM Enterprise-Wide Deployment

  • Release version: Zurich
  • Updated August 10, 2026
  • 2 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 Configuring SPM Enterprise-Wide Deployment

    Configuring Enterprise-Wide Deployment (EWD) in ServiceNow Strategic Portfolio Management (SPM) enables function-level data separation across your organization. This is achieved by creating partitions, setting partition criteria on supported tables, and assigning partition roles to users or groups. The configuration ensures that users only access data relevant to their assigned partitions, enhancing security and compliance.

    Show full answer Show less

    Key Features

    • Partition Creation: Define partitions with associated roles to segment data logically, such as separating IT Operations from HR Learning and Development.
    • Partition Criteria Configuration: Assign a reference column (e.g., Department) consistently across all partitions on supported tables to enforce data separation.
    • Role Assignment: Grant access to partitions by assigning the corresponding partition roles to users or user groups.
    • Data Update for Existing Records: Run a scheduled job to update existing records with partition details, ensuring historical data adheres to the partitioning scheme.
    • Supported Tables: Partitioning applies to core tables including Project, Demand, Program, and Portfolio. Related records inherit partition values automatically.
    • Workspace Compatibility: Partition enforcement requires specific minimum versions of supported workspaces such as Project Workspace (7.3.0) and Portfolio Planning Workspace (8.15.0).

    Key Outcomes

    • Function-Level Data Separation: Ensures users see only the data relevant to their role and partition, improving data security and governance.
    • Consistent Partitioning: Using a uniform reference column across partitions maintains data integrity and simplifies management.
    • Seamless Integration with Existing Data: Scheduled updates apply partition details to existing records, providing comprehensive partitioning coverage.
    • Controlled Deployment: Changes to partition configuration and role assignments should be applied during maintenance windows to avoid access issues and ensure proper record visibility.

    Practical Considerations for ServiceNow Customers

    • Ensure you have the EWD admin role [snspmewd.ewdadmin] before starting configuration.
    • Plan your partition structure carefully, as the partition criteria field becomes read-only after initial configuration on each table.
    • Identify the appropriate reference column to maintain consistency across partitions on each supported table.
    • Assign partition roles thoughtfully to users or groups to control data access effectively.
    • Run the Update existing records with partition details scheduled job after setting up partitions to update historical data.
    • Apply all configuration changes during a maintenance window to ensure visibility updates propagate correctly without disrupting users.

    Configuring Enterprise-Wide Deployment (EWD) involves creating partitions, defining partition criteria for supported tables, and assigning partition roles to users or user groups to enforce function-level data separation.

    High-level configuration process

    EWD configuration is an administrative activity that requires planning before implementation. To achieve data separation with EWD, complete the following steps in order:

    1. Create a partition record with assigning a new or existing role to it. For details, see Create and configure a partition.
    2. Configure partition criteria for each supported table that you want to define data partitioning for that partition. For details, see Assign partition role for access to the partition.
    3. Assign the partition role associated with the partition record to the users or user groups who should have access to those partitioned tables. For details, see Verify partition configuration.

      Repeat this process for each function partition you need to create. For example, create separate partitions for IT Operations and HR Learning and Development.

    4. Update the existing records in the project, demand, programs, portfolios, and planning item tables with partition details by running the scheduled job. For details, see Update partition details for existing records.
    Important:
    Apply partition configuration changes and role assignments during a maintenance window when users are not accessing the instance, to ensure record visibility updates take effect correctly.

    Partition configuration checklist

    Before configuring Enterprise-Wide Deployment, ensure the following are in place:

    • The EWD admin [sn_spm_ewd.ewd_admin] role assigned to you.
    • The reference column to use as the partition criteria field is identified. All partitions on the same table must use the same reference column — for example, Department for all partitions on the Project table.
    • The users or user groups that should have access to each partition are identified.
    • A plan for handling existing records is in place. After configuring partitions, run the Update existing records with partition details scheduled job to populate partition values on historical records.
    Important:
    Once partition criteria is configured for a table, the criteria field becomes read-only and cannot be changed for subsequent partitions on that table. Plan your partition structure accordingly before creating partitions.

    Supported tables for partition criteria

    Partition criteria can be configured for the following core tables:

    • Project [pm_project]
    • Demand [dmn_demand]
    • Program [pm_program]
    • Portfolio [pm_portfolio]

    Related records and sub-entities for these tables automatically inherit the partition value from the parent record. For a full list of tables in scope, see Supported tables for partition.

    Supported workspace versions

    Partition enforcement is supported in the following workspaces. For partition enforcement to function in a workspace, that workspace must be installed at the specified minimum version:
    • Project Workspace (7.3.0)
    • Portfolio Planning Workspace (8.15.0)
    • Strategic Planning Workspace (4.15.0)
    • Resource Management Workspace (5.7.0)