---
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 in Request Management

# Domain separation in Request Management {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
This is an overview of domain separation in Request 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: Standard {#domain-sep-req-management__section_gq1_2cr_xkb}

* Includes all aspects of Basic level support.
* Application properties are domain-aware as needed.
* Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
* The instance owner must configure the minimum viable product (MVP) business logic and data parameters per tenant as expected for the specific application.
{#domain-sep-req-management__ul_tfh_drj_xkb}

Sample use case: An admin must be able to make comments required when a record closes for
one tenant, but not for another.{#domain-sep-req-management__p_ssc_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-req-management__p_tsc_nfg_h1c}

## Activation information {#domain-sep-req-management__section_vnv_rps_d3b}

The Domain Support - Domain Extensions Installer plugin
(com.glide.domain.msp_extensions.installer) should be activated to enable domain separation for
Request Management. For information on how you can request for this plugin activation, see [Request domain separation](https://www.servicenow.com/docs/access?context=t_ActivateDomainSeparation&version=australia&pubname=australia-platform-security&ft:locale=en-US).

## How domain separation works in Request Management {#domain-sep-req-management__section_ydt_kth_scb}

Fulfillers see only requests, requested items, and catalog tasks that have been created within
the (tenant) domain for which the fulfiller has the visibility. For information on visibility in
domain hierarchies, see [Visibility domains and Contains
domains](https://www.servicenow.com/docs/access?context=c_DomainVisibility&version=australia&pubname=australia-platform-security&ft:locale=en-US).

## Domain separated tables {#domain-sep-req-management__section_pk2_bnh_qdb}

* Request \[sc_request\]
* Requested Item \[sc_req_item\]
* Catalog Task \[sc_task\]
{#domain-sep-req-management__ul_wm5_3vm_ndb}

## Use cases {#domain-sep-req-management__section_yfc_cnh_qdb}

* A user belonging to "Initech" domain, submits a request. Only those fulfillers belonging to "Initech" domain or global domain can see this request.
* A fulfiller belonging to a parent domain can see requests, requested items, and catalog tasks of all its child domains as well.
* A fulfiller belonging to a specific domain can create requests only on behalf of the 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-sep-req-management__ul_mv2_xvm_ndb}
**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)