Domain separation and Strategic Planning

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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 Domain separation and Strategic Planning

    Domain separation in Strategic Planning allows ServiceNow customers to logically group and isolate data, processes, and administrative tasks into distinct domains. This capability ensures that data visibility and access are controlled based on user permissions tied to specific domains. It supports multi-tenant environments by maintaining data segregation across tenants.

    Show full answer Show less

    Key Features

    • Basic support level: The application ensures that data is correctly allocated to the appropriate domain during runtime.
    • Comprehensive domain separation: Includes user interface elements, cache keys, reporting, rollups, and aggregations to maintain consistent data isolation.
    • Multi-tenant setup: Requires instance owner configuration to enable Strategic Planning to operate across multiple tenants.
    • Domain-separated data objects: Lens, portfolio plans, planning items, and roadmaps can be created and managed within separate domains.
    • Automatic enforcement: Once domain separation is enabled on the instance, Strategic Planning data is automatically segregated based on domain, restricting visibility to authorized users only.
    • Full domain separation support: All tables installed with Strategic Planning are designed to support domain separation, ensuring consistent data isolation across the application.

    Practical Implications for Customers

    ServiceNow customers leveraging Strategic Planning in multi-tenant or service provider scenarios benefit from robust domain separation to maintain data privacy and governance. For example, when a service provider responds to a tenant’s inquiry via chat, only users with access to that domain can view the interactions, ensuring confidentiality.

    Enabling domain separation requires proper setup by the instance owner, but once configured, it enforces strict data access controls across all Strategic Planning components, facilitating secure and organized strategic management across multiple organizational units or customers.

    Domain separation is supported for Strategic Planning. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

    Support level: Basic

    • Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.
    • The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
    • The owner of the instance must set up the application to function across multiple tenants.

    Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer’s message, the customer must be able to see the SP's response.

    For more information on support levels, see Application support for domain separation.

    Overview of domain separation in Strategic Planning

    You can create lens, portfolio plans, planning items, and roadmaps in different domains.

    How domain separation works in Strategic Planning

    After you enable domain separation on your ServiceNow instance, the data of Strategic Planning is automatically domain separated. So, the data of lens, portfolio plans, planning items, and roadmap configuration for different domains is visible to only those users who have access to these domains.

    Domain separated tables in Strategic Planning

    All the tables installed with Strategic Planning support domain separation. For a complete list of tables, see Components installed with Strategic Planning Workspace.