Domain separation and Digital Product Release

  • Release version: Washingtondc
  • Updated June 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 in Digital Product Release

    Domain separation in Digital Product Release facilitates the organization of data, processes, and administrative tasks into distinct logical units known as domains. This capability allows for controlled access to data based on user roles, enhancing security and data integrity within the application.

    Show full answer Show less

    Key Features

    • Data Organization: Enables logical grouping of data and processes.
    • User Access Control: Administrators can determine which users see and access specific data.
    • Runtime Support: The application supports domain separation during runtime, ensuring proper data handling.
    • Domain Field: Each table includes a "Domain" field that is essential for configuring separation in Digital Product Release.

    Key Outcomes

    Implementing domain separation allows service providers to manage tenant-specific interactions smoothly, such as ensuring that customer responses from service providers are visible to the intended tenant-customer. This functionality enhances user experience and operational effectiveness across multiple tenants.

    Domain separation is supported for Digital Product Release. 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 Digital Product Release

    All tables in Digital Product Release can be domain-separated and include the required domain separation field.

    How domain separation works in Digital Product Release

    • Each table in Digital Product Release includes the domain separation field called Domain.
    • Customers can use this field to configure domain separation in their implementation of Digital Product Release.