--- sourceDocument: Australia Conversational Interfaces sourceDocumentLink: https://www.servicenow.com/docs/r/australia/conversational-interfaces Release : - australia ft:locale : - en-US ft:publication_title : - Australia Conversational Interfaces ft:clusterId : - convint bundleId : - convint workflow : - Platform --- # Domain separation and Sidebar # Domain separation and Sidebar {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Domain separation and Sidebar Domain separation in ServiceNow enables segmentation of data, processes, and administrative tasks into distinct logical domains. This allows control over user access and visibility of data across different domains, supporting multi-tenant environments. Sidebar supports domain separation, allowing you to manage discussions and interactions based on domain-specific records. Show full answer Show less ## Key Features * **Domain-aware Sidebar:** Sidebar discussions are linked to the base task or interaction record and are visible only to users with access to that domain's records. * **Parent-child domain hierarchy requirement:** Domain separation for Sidebar is supported only with a parent-child domain structure. * **Version requirements:** Full domain separation support requires the Vancouver and August versions of the Sidebar store app (Omni Experience Standard Feature Set). * **Activation per domain:** For new Sidebar users on Vancouver, Sidebar is inactive by default and must be activated manually per domain through settings or database records. * **Emojis workaround:** Due to a known emoji issue with domain separation, a manual update is required in the Enable Emojis ACE Content block referencing the domain's syscscollabsettings record. * **Microsoft Teams integration limitation:** When Sidebar is integrated with Microsoft Teams, activation or deactivation of Sidebar must be managed manually. Domain separation is not supported with multiple domains in Teams, nor can a unique Teams instance be paired per domain. ## Practical Considerations for ServiceNow Customers * Enable domain separation on your instance to use Sidebar with domain-specific controls. * Ensure you have the correct Sidebar app versions to leverage domain separation features fully. * Manage Sidebar activation individually for each domain, especially for new Sidebar users. * Apply the emoji workaround if you encounter display issues in domain-separated Sidebar discussions. * Plan your Microsoft Teams integration carefully, as domain separation is limited and requires manual management. Domain separation is supported for Sidebar . 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: Standard {#sidebar-domain-separation__section_sdj_vvn_c5b} * Includes all aspects of Basic level support. * Application properties are domain-aware as needed. * Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance. * The instance owner must configure the minimum viable product (MVP) business logic and data parameters per tenant as expected for the specific application. {#sidebar-domain-separation__ul_tfh_drj_xkb} Sample use case: An admin must be able to make comments required when a record closes for one tenant, but not for another.{#sidebar-domain-separation__p_ssc_nfg_h1c} For more information on support levels, see [Application support for domain separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=australia&pubname=australia-platform-security&ft:locale=en-US).{#sidebar-domain-separation__p_tsc_nfg_h1c} ## Domain separation and Sidebar {#sidebar-domain-separation__section_l4f_wvn_c5b} To set up domain separation for Sidebar, enable domain separation for your instance. If your instance has multiple domains, you can turn Sidebar on or off for each domain. No special configuration is needed to configure a domain-separated environment with Sidebar. Domain separation for Sidebar is supported only when domains are set up using a parent-child domain hierarchy. Sidebar discussions are domain separated according to the base record (task or interaction record). You can see and create sidebar discussions only if you have access to the task or interaction record. For example, say INC00001 belongs to the record created in the ACME domain and the Cisco domain doesn't have access to INC00001. Users that belong to the Cisco domain can't interact with Sidebar discussions based on INC00001. ## Sidebar versions for domain separation {#sidebar-domain-separation__section_hpz_lbt_dyb} To fully use domain separation, you must be on both the Vancouver version and August version of the Sidebar store app (Omni Experience Standard Feature Set). If you are a first time Sidebar user in Vancouver (you did not use Sidebar earlier and are not trued up to the Vancouver store app) and need to use domain separation, Sidebar is inactive by default. Navigate to the Conversational Interfaces settings page for each domain and activate Sidebar manually. Alternatively, you can access the sys_cs_collab_settings table and manually insert a new record for each domain. There is a known issue with emojis not working as expected when used with domain separation. To work around this issue, go to the Enable Emojis ACE Content block and update the record field with the sys_cs_collab_settings record's sys_id for the given domain. ## Domain separation with the Sidebar and Microsoft Teams integration {#sidebar-domain-separation__section_jg5_xsm_dyb} If Sidebar and Microsoft Teams are integrated and configured, activating Sidebar prompts a message stating that the Microsoft Teams integration must be manually turned on. Deactivating Sidebar prompts a message stating that the integration with Microsoft Teams is also turned off. Domain separation will not work with Microsoft Teams if multiple domains are configured. Pairing a unique Microsoft Teams with each domain is not supported. **Related topics** * [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=australia&pubname=australia-platform-security&ft:locale=en-US)