--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # EWD for demands # Enterprise-Wide Deployment for demands {#ariaid-title1} Release version: Australia Updated October 1, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Enterprise-Wide Deployment for demands Enterprise-Wide Deployment (EWD) in ServiceNow partitions demand data based on criteria such as department, controlling both who can see demands and how demands appear to users. This approach enhances demand management by combining two independent layers: Show full answer Show less * **Partitions:** Control visibility of demands and dashboards based on user roles. * **Demand experiences:** Control the layout, fields, and modules displayed on demand records for users with access. Partitions govern access across Strategic Planning Workspace, list views, search results, and dashboards, while demand experiences customize the user interface and navigation once access is granted. ## Partitioning Demands Partitions are defined by an administrator via a criteria field on the Demand table (e.g., Department), creating partitions for each value (e.g., IT Operations, Finance). Demands automatically inherit a partition based on this field. Users see only demands in partitions they are authorized for, and administrators can assign unique default dashboards per partition to enhance user experience. Partitioning also extends to related demand tables like demand tasks, cost plans, and resource assignments, ensuring comprehensive data segregation. ## Demand Experiences Demand experiences tailor the demand record's fields, modules, and layout according to governance processes such as Marketing or IT. Key behaviors controlled by demand experiences include: * Available modules * Form layouts * Dynamic fields driven by dynamic categories and attributes When dynamic fields are present, an Additional Information tab appears on the demand record (requires the Enterprise-Wide Deployment application). ## Roles and Responsibilities * **EWD Admin:** Sets up partitions, criteria fields, and role assignments. * **System Admin:** Creates dynamic categories. * **PPS Admin:** Manages demand experiences, selecting tables, views, dynamic categories, and enabled modules. * **EWD PMO:** Has visibility across all partitions, regardless of role assignment. * **Demand User:** Accesses and creates demands only within assigned partitions and experiences, without administrative capabilities. ## Demand Data Visibility With both EWD and demand experiences configured, demand users experience: * Access only to demands in their assigned partitions with no indication of other partitions' demands. * A dropdown menu to switch views if multiple partitions are accessible. * Display of only the modules enabled for a demand's experience. * Visibility of the Additional Information tab when applicable. ## Practical Benefits for ServiceNow Customers This configuration enables organizations to securely segment demand data across departments or business units while providing tailored user experiences that align with governance processes. It improves data security, user navigation, and relevance of information, ensuring each user interacts with demands appropriate to their role and context. Enterprise-Wide Deployment (EWD) partitions demand data by criteria such as department. Demand experiences extends that by controlling each demand's fields, modules, and layout. Demands support EWD in two complementary ways: partitioning, which controls who can see a demand, and demand experiences, which control what a demand looks like to users who can see it. For the full EWD concept, including partitions for other SPM tables, see [Exploring SPM Enterprise-Wide Deployment](https://www.servicenow.com/docs/vWukTR_Sj3ptliNdL44~0A "SPM Enterprise-Wide Deployment (EWD) partitions SPM tables data so that you can restrict record access by department, business unit, or other function."). Partitions and demand experiences are two independent, complementary layers, and the boundary between them is deliberate: partitions control who can see a demand and its dashboards; demand experiences control what a demand looks like and how it's navigated once you can see it. Partitions don't determine the record view, form fields, related lists, modules, or record tabs. Those are all controlled by the demand experience field. ## Partitioning demands {#ewd-for-demands-ppw__section_ewd_partitioning_for_demands} The Demand \[dmn_demand\] table is one of the tables EWD supports for partitioning. Partitioning also applies to demand-related tables, such as demand tasks, cost plans, and resource assignments. For more information, see [Supported tables for partition](https://www.servicenow.com/docs/xSUbN9ilEuJYpcQOF9yCEg "Several tables are supported for partition using Enterprise-Wide Deployment, including direct and indirect related tables for each entity."). An administrator defines a partition criteria field on the Demand table, such as Department, and creates a partition for each value, such as IT Operations or Finance. When a demand is created, it's automatically stamped with the partition that matches its criteria field. A user then sees only the demands that belong to a partition their role grants them access to, across Strategic Planning Workspace, list views, search results, and dashboards. An administrator can also configure a unique default dashboard for each partition; a user sees the default dashboard for their own partition automatically when they log in. For more information, see [Map a dashboard to a partition](https://www.servicenow.com/docs/OdCjYm7usvzoDCvXVHsjWw "Give a partition its own dashboard for an experience, such as Demand Management, so that users who select the partition see the dashboard mapped to it."). ## Demand experiences {#ewd-for-demands-ppw__section_demand_types_extend_ewd} A demand experience controls the fields, modules, and layout a demand shows for a given governance process, such as Marketing or IT. For more information, see [Demand experiences](https://www.servicenow.com/docs/hBRO_uXXzD071GGK9CA_1Q "A demand experience defines a governance process and controls which form view, modules, and dynamic attributes appear on a demand.") and [Create a demand experience](https://www.servicenow.com/docs/87ugjV~XHYFLsGKp_ZpNow "Create a demand experience to control the form view, demand modules, and dynamic attributes that appear on demands to support configuration independence across different types of demands."). The following demand-record behaviors depend on a demand's experience: * Modules available for a given demand experience * Form layout for a given demand experience * Dynamic fields when a demand experience has a dynamic category with configured dynamic attributes {#ewd-for-demands-ppw__ul_ewd_demand_type_behaviors} When a demand experience includes dynamic fields, the demand record displays an Additional Information tab that shows those fields. The Enterprise-Wide Deployment application (sn_spm_ewd) must be installed for the Additional Information tab to appear. ## Personas {#ewd-for-demands-ppw__section_ewd_demand_personas} {#ewd-for-demands-ppw__table_xc5_qvr_rkc__entry__2} | Role | Function | |-|-| | EWD admin role \[sn_spm_ewd.ewd_admin\] | Creates and configures partitions for the Demand table, including the partition criteria field and the role assigned to each partition. | | System admin role \[sys_admin\] | Creates dynamic categories from SPM Dynamic Categories. | | PPS admin role \[pps_admin\] | Creates and manages demand experiences: selects the table, form view, optional dynamic category, and which modules are enabled. | | EWD PMO role \[sn_spm_ewd.ewd_pmo\] | Views demands across all partitions, regardless of partition role assignment. | | Demand user role \[it_demand_user\] | Creates and views demands in the partitions that their role grants access to. Doesn't administer experiences or dynamic categories. On a demand record, sees the modules enabled for that demand's experience and, when applicable, the Additional Information tab with its dynamic fields. | [ ] {#ewd-for-demands-ppw__table_xc5_qvr_rkc} ## Demand data visibility {#ewd-for-demands-ppw__section_ewd_demand_data_appearance} When EWD and demand experiences are both configured, a demand user sees: * Only demands that belong to their assigned partitions in list views, search results, and dashboards, with no indication that demands in other partitions exist. * A drop-down list of available views in the menu panel, when the user has access to more than one partition. * Only the modules on a demand that are enabled for that demand's experience. * An Additional Information tab on the demand record, only when the demand's experience has a dynamic category with configured dynamic attributes. {#ewd-for-demands-ppw__ul_ewd_demand_data_appearance} **Related concepts** * [Demand experiences](https://www.servicenow.com/docs/hBRO_uXXzD071GGK9CA_1Q "A demand experience defines a governance process and controls which form view, modules, and dynamic attributes appear on a demand.") **Related tasks** * [Create a demand experience](https://www.servicenow.com/docs/87ugjV~XHYFLsGKp_ZpNow "Create a demand experience to control the form view, demand modules, and dynamic attributes that appear on demands to support configuration independence across different types of demands.") * [Create a demand](https://www.servicenow.com/docs/Z_~PcD67gF2Z5eeCFE3fGA "Create demands to capture the strategic and operational requirements and centralize information for stakeholder assessment and prioritization.") **Related reference** * [SPM Enterprise-Wide Deployment](https://www.servicenow.com/docs/nupwAHC8BQogyp2eWrj1zQ "SPM Enterprise-Wide Deployment (EWD) provides data partitioning capabilities for Strategic Portfolio Management (SPM) tables that enable organizations to separate and control record visibility across functions such as departments and business units.")