---
sourceDocument: Australia ServiceNow AI Platform user interface
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/platform-user-interface

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia ServiceNow AI Platform user interface

ft:clusterId :

    - platux

bundleId :

    - platux

workflow :

    - Platform


---

# Domain separation and Embedded Help

# Domain separation and Embedded Help {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Domain separation is supported for Embedded Help. 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 {#domain-separation-and-embedded-help__section_eps_wmz_5zb}

{#domain-separation-and-embedded-help__domain-sep-supported}  
* 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.
{#domain-separation-and-embedded-help__ul_yhr_g2j_xkb}

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.{#domain-separation-and-embedded-help__p_lsc_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).{#domain-separation-and-embedded-help__p_msc_nfg_h1c}

## Overview {#domain-separation-and-embedded-help__section_wg3_xr5_5zb}

The goal of Embedded Helpis to enable your users to benefit from base system help topics, as well as to create your own custom help topics. If your organization uses domain separation, you can create custom embedded help for
each domain.

## How domain separation works in Embedded Help {#domain-separation-and-embedded-help__section_xg3_xr5_5zb}

If your organization uses domain separation, you can create custom embedded help for each domain. To associate help content with a domain, the administrator configures the Help Content form to include the
Domain field. When custom content is created, the author selects the domain to which the content applies.  
Nota:  
* Content with no specified domain is in the global domain.
* If domain-specific content does not exist for a user in a domain, the user sees the global help content.
* Users in the global domain only see global help content. An administrator who wants to test domain-specific help must impersonate a user in that domain.
{#domain-separation-and-embedded-help__ul_yld_gjp_x1b}
**Tópicos relacionados**   

* [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)