---
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 and Service Portfolio Management

# Domain separation and Service Portfolio Management {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Domain separation is supported in Service Portfolio Management. 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\* {#SPM2-domain-separation-SPM2__section_dl1_xnc_llb}

The
support level is Basic but has some exceptions or special conditions.{#SPM2-domain-separation-SPM2__p_nsc_nfg_h1c}  
* Business logic: Ensure that data goes into the proper domain for the application's service provider (SP) use cases.
* The user interface, cache keys, reporting, rollups, and aggregations all use the domain at production run time.
* The owner of the instance must be able to set up the application to function across multiple tenants.
{#SPM2-domain-separation-SPM2__ul_msq_t2x_zkb}

Sample use case: When an SP uses chat to respond to a tenant-customer's message, the client
must be able to see the SP's response.{#SPM2-domain-separation-SPM2__p_psc_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).{#SPM2-domain-separation-SPM2__p_qsc_nfg_h1c}
\*All components of Service Portfolio Management (SPM) and Service Owner Workspace (SOW) are
domain-separated in releases of New York and forward. If using Financial Management for the SPM plugin for estimated spend, there can be only one fiscal calendar defined per instance. When this plugin is activated, there can be
only one approach for service offering cost modeling per instance (using either the Financial Management engine or local data. Different domains cannot choose their own spend model.
**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)