Domain separation and Business Continuity Management

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 1 minute to read

    • Domain separation is supported for Business Continuity Management. 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.

    Business Continuity Management supports domain separation. The tables are striped with the domain ID and domain path. Domain separation for Business Continuity Management means that only a user in the application's domain or parent domain can access the data. All functionality for Business Continuity Management works in a domain-separated environment as long as the Business Continuity Management actions are performed by users within that domain.

    How domain separation works in Business Continuity Management

    Domain separation is supported only at the data level for Business Continuity Management. Cross-level scheduled job data setup is not supported. Therefore, you must copy the scheduled job in each of your domain to respect the data level separation.

    To set up domain separation for Business Continuity Management:
    1. Create your domain and then create Business Continuity Management users in that domain.
    2. Only a specified user (Business Continuity Management admin in that domain) should populate configuration data in the domain of the application.
    3. Only users in the application's domain should upload or create data in the domain.
    Follow these guidelines for successful domain separation:
    • Create a separate user for each domain to perform upload, edit, or export of configuration data.
    • Avoid uploading or creating configuration data for a given application in multiple domains.
    • Only users in the application's domain should upload or create data in the domain.
    • Policies and exporters must be either in the application's domain or in the global domain.

    Domain-separated tables in Business Continuity Management

    All Business Continuity Management tables include a Domain column.