---
sourceDocument: Xanadu Customer Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/customer-service-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Customer Service Management

ft:clusterId :

    - csm

bundleId :

    - csm

workflow :

    - Customer and Industry


---

# Domain separation and Recommended Actions

# Domain separation and Recommended Actions {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Domain separation is supported for Recommended Actions. 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 {#recommended-actions-domain-separation__id_usv_bkp_dzb}

{#recommended-actions-domain-separation__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.
{#recommended-actions-domain-separation__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.{#recommended-actions-domain-separation__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=xanadu&pubname=xanadu-platform-security&ft:locale=en-US).{#recommended-actions-domain-separation__p_msc_nfg_h1c}

## Overview {#recommended-actions-domain-separation__section_brz_xcp_dzb}

The tables and data in the application are domain separated. Recommendation authors can only see the context applicable to them based on the domain. In runtime, recommendations are evaluated in the user context and data is created
in the corresponding domain applicable to the user.

## How domain separation works in Recommended Actions {#recommended-actions-domain-separation__section_crz_xcp_dzb}

To use domain separation in the Recommended Actions application, you can create separate Context records for each domain. Context serves as a starting point in Recommended Actions. All other configurations such as Rule, Recommendation, and Resource Generator can then be associated with the domain of the corresponding context record.

Runtime evaluation and generation of recommendations are user-specific. The domain applicable to the user is selected and the corresponding Rules applicable to the user's domain are evaluated to give a final set of recommendations
to the end user. Execution records created use the same domain of the context that was applicable for the given user.

## Domain-separated tables {#recommended-actions-domain-separation__section_drz_xcp_dzb}

When you create related entities for a context, the domain for the related entities is set to the domain of the context. The following tables in the application are domain separated:

* Context
* Recommended Action Rule
* Recommendation
* Resource generator
* Recommendation group
* Search result recommended action mapping
* Recommended Action Context
* Recommended Action Execution
* Recommended Action Order
* Field recommendation
* Field recommendation input
* Field recommendation definition
* Resource generator type
* Resource generator type input
* Recommendation grouping strategy
* Action Type Definition
* Trend Definition
{#recommended-actions-domain-separation__ul_xlv_scq_dzb}
**Related topics**   

* [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US)