Domain separation and Conversational Analytics

  • Release version: Zurich
  • Updated November 3, 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 Conversational Analytics

    Domain separation in the Conversational Analytics dashboard allows for the logical grouping of data into domains, enhancing data security and user access control. This feature is essential for service providers managing multiple tenants, ensuring that users only see data relevant to their domain.

    Show full answer Show less

    Key Features

    • Data Isolation: Users in one domain cannot access the data or functionality of another domain, providing enhanced security.
    • Administrative Control: Domain-specific administrators cannot view or manage dashboards outside their assigned domain.
    • Global Approach: Currently, only a global approach to domain separation is supported.
    • Plugin Requirement: The Domain Support - Domain Extensions Installer plugin is necessary for all domain support features.

    Key Outcomes

    By implementing domain separation, service providers can effectively manage and secure tenant data, ensuring compliance and operational efficiency. This setup is critical for environments where multiple clients share the same instance, allowing for streamlined data governance while maintaining distinct operational boundaries.

    Domain separation is supported in Conversational Analytics dashboard. Domain separation enables you to separate data into logical groupings called domains. You can control several aspects of this application, including which users can see and access data.

    Support level: Basic*

    The support level is Basic but has some exceptions or special conditions.

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

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

    Required approach to domain separation

    Currently, only Global approach is supported to domain separation in Conversational Analytics dashboard. To learn more, see Domain separation and Performance Analytics.

    Overview of domain separation

    Conversational Analytics dashboard is built on the Platform Analytics experience. See Domain separation for Platform Analytics dashboards for more information.

    How domain separation works in Conversational Analytics

    With domain separation in Conversational Analytics, users in one domain cannot access data or functionality that belongs to another domain. Additionally, administrators who are assigned to a domain cannot see or manage Conversational Analytics dashboard in other domains, ensuring complete separation and security.
    Note:
    If you override a formula in any domain, the system applies that updated formula to all other domains.

    Requirements

    All domain support features require the Domain Support - Domain Extensions Installer [com.glide.domain.msp_extensions.installer] plugin. For details, see Request domain separation.

    Use cases

    If you are a service provider that hosts multiple clients in the same instance, you can set up domain separation to separate tenant data. Administrative tasks and process separation are currently not supported.