---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Apply domain separation on dot walked fields

# Apply domain separation on dot walked fields {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The glide.sys.domain.include_domain_condition_on_join property controls whether join queries are given domain separated conditions or not in order to ensure they apply domain separation functionality for
dot walked fields.
The glide.sys.domain.include_domain_condition_on_join system property controls whether join queries are given domain separated conditions or not, in order to ensure they apply domain separation functionality
for dot walked fields.

Ensure that the property glide.sys.domain.include_domain_condition_on_join is set to true when the Domain Separation plugin is active.  
Warning:  
This is a safe harbor property, meaning the value can't be altered once it's changed. It is non-revertible.

## More information {#sc-apply-domain-separation__section_more_information}

{#sc-apply-domain-separation__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Property name | glide.sys.domain.include_domain_condition_on_join |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | true Note: If domain separation is installed, otherwise the property doesn't exist. |
| Default value | \<none\> |
| Fallback value | false |
| Category | [Access control](https://www.servicenow.com/docs/UcoTP53NgzpgtyyAIm1CdQ "The access control category audits the process of protecting resources from unauthorized access through granting and denying requests based on a permission model. This includes ensuring an entity accessing a resource holds valid credentials to do so, creating and protecting a well-defined set of roles or permissions and ensuring role or permission controls are protected from replay and tampering.") |
| Purpose | Controls whether join queries are given domain separated conditions or not, in order to ensure they apply domain separation functionality for dot walked fields. |
| Security risk | * Severity score: 6.5 * CVSS score: Medium * Security risk details: Sensitive information could be disclosed that is not to be shared with a specific domain. {#sc-apply-domain-separation__ul_g1g_3sf_xwb} |
| Functional impact | There may be moderate functional impact to the instance if components are reliant on the unsafe cross domain queries. Instances should be tested in non-production environments before enabling. |
| References | [Domain separation for service providers](https://www.servicenow.com/docs/ucQoIhLEA9ZnfAojjIczPQ "With the ServiceNow Platform, service providers (SPs) can provide their customers with faster onboarding, meet compliance, and protect their data using domain separation. You can separate client data, processes, and reports into logical groupings called domains. SPs control who sees and accesses what content.") |
[ ]

{#sc-apply-domain-separation__table_ajc_b43_3kb}