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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Domain separation

# Domain separation and Universal Task {#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 Universal Task

Domain separation in ServiceNow Universal Task allows for the management of data, processes, and administrative tasks within distinct logical groupings known as domains.
This feature is essential for organizations that need to ensure that specific users have controlled access to data relevant to their domain.
Show full answer Show less  

## Key Features

* **Process Domain Separation:** Configuration tables, such as those for task types, are process domain-separated, allowing parent domains to implement configurations in child domains while permitting overrides.
* **Data Domain Separation:** Data tables like the Universal Task table allow access to data across domains, with child domains' data accessible to parent domains.
* **Support Level:** Basic support for domain separation functionalities is provided.

## Key Outcomes

With domain separation, ServiceNow customers can manage and control how data and configurations are handled across different organizational domains. This ensures that when, for example, a service provider communicates with a tenant-customer, the communication is appropriately handled within the correct domain context. Additionally, organizations can tailor task types per service while maintaining overarching control at the parent domain level, enhancing operational efficiency and data governance.  
Domain separation is supported for ServiceNow
Universal Task. Universal Task enables agents to request extra
information from the employee or to task the employee to accomplish an activity, in order to
resolve a ticket. 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-task__id_qys_jyl_x4b}

{#domain-sep-universal-task__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-task__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-task__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-task__p_msc_nfg_h1c}

## Overview {#domain-sep-universal-task__section_cyn_1yl_x4b}

In the Universal Task framework, all the configurations are process
domain-separated, and the data tables, namely, Universal Task table, Employee
form table, and Task template table are data domain separation offerings.

## How domain separation works in Universal Task {#domain-sep-universal-task__section_dyn_1yl_x4b}

The configuration tables in Universal Task are process domain-separated. So,
the configurations created by the parent domains are also implemented in the child domains.
However, a child domain can override the configuration, if needed. For example, In an
organization, the services are the child domains, while the organization is the parent
domain. The task types available for Universal Task in a particular
organization, will also be available for the various services of the organization. However,
a particular service can override the task types as needed.

The data tables in Universal Task are data domain-separated. So the data
stored in any of the child domains is accessible to the parent domain. For instance, if a
service is using task templates, the data captured in the Task templates table for the
service domain is accessible to the organization domain, but not to the domains of other
services, unless configured.

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

The following Configuration tables are process separated.

* sn_uni_task_config
* sn_uni_task_base_task_config
* sn_uni_task_catalog_task_config
* sn_uni_task_emp_input_task_config
{#domain-sep-universal-task__ul_omt_5yl_x4b}  
The following Data tables are data separated.

* sn_uni_task_universal_task
* sn_uni_task_template
* sn_uni_task_employee_form
{#domain-sep-universal-task__ul_pcj_yyl_x4b}
**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)