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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Domain Separation for ITSM Mobile Agent

# Domain Separation for ITSM Mobile Agent {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
This is an overview of domain separation and ITSM Mobile Agent. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which
users can see and access data.

## Support level - Basic {#domain-separation-itsm-mobile-agent__section_tbf_fnm_5mb}

* 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. This includes domain 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-itsm-mobile-agent__ul_jfm_gnm_5mb}

Use case: When a service provider (SP) uses chat to respond to a tenant-customer's message,
the client must be able to see the SP's response.

## ITSM Mobile Agent overview {#domain-separation-itsm-mobile-agent__section_zq3_knm_5mb}

The mobile platform supports domain separation for all native clients. The mobile UI design
clearly indicates the domain that a record is associated with.

Before extending the domain separation functionality to mobile, the feature must be enabled on
the platform web-based interface. For further information on configuration, see [Domain separation setup and
administration](https://www.servicenow.com/docs/access?context=c_DomainSeparationSetup&version=australia&pubname=australia-platform-security&ft:locale=en-US).

## How domain separation works in mobile {#domain-separation-itsm-mobile-agent__section_jss_mnm_5mb}

You can use the company or account fields to display appropriate records by domain. These
fields are available in tables when the domain separation plugin is enabled. Because each
company or account is linked to a single domain, when you create a record, you can use these
fields to specify the domain in which you want to create the record.

After the feature has been set up through the platform web-based interface, a two-part process
is required to further extend the domain separation functionality on mobile. For additional
information about configuring domain separation on mobile devices, contact Customer Service and Support.

## Domain separated tables {#domain-separation-itsm-mobile-agent__section_lkh_pnm_5mb}

* Incident \[incident\]
* Incident Task \[incident_task\]
{#domain-separation-itsm-mobile-agent__ul_wgc_qnm_5mb}

## Use cases {#domain-separation-itsm-mobile-agent__section_sc1_rnm_5mb}

* An ESS user belonging to "Initech" domain, creates an incident. Only those ITIL users belonging to "Initech" domain or global domain can see this incident.
* An ITIL user belonging to a parent domain can see incidents of all its child domains as well.
* An ITIL user belonging to a specific domain can create incidents only on behalf of the domains that they have access to.
* An ITIL user can associate child incidents only of those domains that they have access to.
* If a user has access to multiple domains, the domain specified on the current record drives the functionality of that record and reference fields.
{#domain-separation-itsm-mobile-agent__ul_q1t_rnm_5mb}