---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/employee-service-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Domain separation and Universal Request

# Domain separation and Universal Request {#ariaid-title1}

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

Domain separation is supported for ServiceNow
Universal Request. Universal Request helps Help Desk agents to
resolve cases across the enterprise for a better employee experience. 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-sep-universal-request__id_dlf_rwl_x4b}

{#domain-sep-universal-request__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-sep-universal-request__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-sep-universal-request__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-sep-universal-request__p_msc_nfg_h1c}

## How domain separation works in Universal Request {#domain-sep-universal-request__section_m1y_2wl_x4b}

All configurations are strictly domain separated.

The Universal Request table is data-separated.

## Tables {#domain-sep-universal-request__section_n1y_2wl_x4b}

Configuration tables (strict domain separation)

* universal_request_service_set
* universal_request_service_conf
* universal_request_state_mapping
* universal_request_route_conf
* universal_request_transfer_mapping
* universal_request_transfer_fields_mapping

{#domain-sep-universal-request__ul_i53_ywl_x4b}

Data tables (data separated): universal_request.
**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)