--- 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 September 25, 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 by criteria such as department, controlling visibility and user experience separately. This approach allows organizations to manage who can see specific demands and how those demands are presented to users. Partitioning restricts access to demands and dashboards based on roles, while demand experiences customize the demand record's fields, layout, and modules. Show full answer Show less ## Key Features * **Partitioning:** Administrators define a partition criteria field (e.g., Department) on the Demand table and create partitions for each criteria value (e.g., IT Operations, Finance). Demands are automatically assigned to a partition. Users see only demands within partitions their roles permit, including dashboards mapped uniquely per partition. * **Demand Experiences:** Configured by PPS admins, demand experiences determine the form layout, enabled modules, and dynamic fields shown on demand records based on governance processes like Marketing or IT. Dynamic categories display additional fields under an "Additional Information" tab when applicable. * **Role-Based Access:** Specific roles manage different aspects of EWD: * **EWD Admin:** Creates partitions and assigns roles to partitions. * **System Admin:** Creates dynamic categories. * **PPS Admin:** Manages demand experiences. * **EWD PMO:** Views demands across all partitions. * **Demand User:** Views and creates demands only within assigned partitions and experiences. ## What to Expect With EWD and demand experiences configured, users experience: * Access limited strictly to demands within their assigned partitions, with no visibility into other partitions. * Dashboards and list views tailored to their partition access. * Demand records displayed according to the configured demand experience, including relevant modules and dynamic fields. * A consolidated and secure way to manage demand data across enterprise departments, improving governance and user navigation. 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-dw__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-dw__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. See [Demand experiences](https://www.servicenow.com/docs/7wyoo8u35TphYi7d4qZhxQ "A demand experience defines a governance process and controls which form view, modules, and dynamic attributes appear on a demand.") for how a demand experience is structured, including form view precedence when more than one view rule applies, and [Create a demand experience](https://www.servicenow.com/docs/zYTtph6gT1abAbOjAdzOdw "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.") for how to create one. 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-dw__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-dw__section_ewd_demand_personas} {#ewd-for-demands-dw__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-dw__table_xc5_qvr_rkc} ## Demand data visibility {#ewd-for-demands-dw__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-dw__ul_ewd_demand_data_appearance} **Related concepts** * [Demand experiences](https://www.servicenow.com/docs/7wyoo8u35TphYi7d4qZhxQ "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/zYTtph6gT1abAbOjAdzOdw "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/ZLhTCzaCcqZq_IxOg5g8ww "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.")