--- sourceDocument: Brazil Platform security sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Platform security ft:clusterId : - psec bundleId : - psec workflow : - Platform --- # Domain system properties and user preferences # Domain system properties and user preferences {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Domain system properties and user preferences This document explains key system properties and user preferences that control domain scope in ServiceNow instances using domain separation. Administrators manage these settings to restrict or expand domain visibility and behavior for records, processes, and business rules, ensuring proper data isolation and process execution within domain boundaries. Show full answer Show less ## Domain system properties New domain separation activations automatically restrict domain scope to the record's domain for related data and processes. When viewing records, all related data and processes are limited to that record's domain. Each open tab can have a different domain scope based on the record displayed. Two primary properties enforce domain scoping: * **glide.sys.domain.userecorddomainforprocesses**: Restricts all processes except business rules to the record's domain. * **glide.sys.domain.userecorddomainfordata**: Restricts all data access to the record's domain. When either is true, older properties related to domain scope are ignored. For business rules executed on the domain table, the property **glide.sys.domain.skipdomaininsertbusinessrules** determines whether they run based on the session domain (default true for new activations from Jakarta release onward) or the domain hierarchy (default false for existing implementations). Setting this to true improves domain insert performance. Another property, **glide.sys.domain.skipnonglobalbusinessruleifnodomain**, ensures only global domain business rules run when querying non-domain-separated tables, aligning with recommended practices. ## User preferences User administrators can configure domain scope preferences globally or per user: * **glide.domain.sessionscope** : Controls if the default domain scope is the user's session domain (true) or the record's domain (false). Users with the `domainexpandscope` role can override this. * **glide.domain.sessionscopenotification**: Toggles a visual indicator showing when domain scope is expanded beyond the record's domain. ## Key outcomes * Administrators can enforce strict domain isolation for data and processes, enhancing security and data governance. * Business rule execution can be optimized for performance and aligned with domain separation best practices. * User preferences provide flexibility to tailor domain scope visibility per user or session, improving usability without compromising security. Administrators have access to properties and user preferences that control domain scope. ## Properties New activations of domain separation automatically restrict domain scope to the record's domain for all related data or processes. When the user views a record in a form, the record's related data (such as reference picker and related list data) and applied processes (such as business rules and client scripts) are restricted to the record's domain scope. If there are records in multiple tabs, each tab has its own domain scope based on the record opened within that tab. The following properties restrict domain scope to either the record's domain and the user's current session domain. {#r_DefaultDomainScope__table_zqj_nkp_1r__entry__2} | Property | Details | |-|-| | glide.sys.domain.use_record_domain_for_processes | Restricts domain scope to the record's domain for all processes. This property does not apply to business rules. Business rules are always processed from the domain record. * Type: true \| false * Default value: true * Location: System Property \[sys_properties\] table {#r_DefaultDomainScope__ul_f2p_wkp_1r} | | glide.sys.domain.use_record_domain_for_data | Restricts domain scope to the record's domain for all data. * Type: true \| false * Default value: true in new domain activations from Fuji onwards (upgrades from instances older than Fuji do not have this property in the table) * Location: System Property \[sys_properties\] table {#r_DefaultDomainScope__ul_dv3_2mp_1r} | [Table 1. Domain system properties] {#r_DefaultDomainScope__table_zqj_nkp_1r} When either the glide.sys.domain.use_record_domain_for_processes or the glide.sys.domain.use_record_domain_for_data property is set to true, the following properties are not used, regardless of their setting: * glide.sys.domain.use_record_domain * glide.sys.domain.use_record_domain_for_client_scripts * glide.sys.domain.domain_change_notify * glide.sys.domain.no_change_roles {#r_DefaultDomainScope__ul_gsz_flp_1r}For a full list of properties see [Available system properties](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). Note: In new activations of domain separation starting with the Jakarta release, the session domain determines the business rules executed on the domain table. In previous versions, business rules executed on the domain table were set based on the newly created domain's hierarchy. This behavior is modified by the glide.sys.domain.skip_domain_insert_businessrules property. Setting this property to true significantly improves domain insert performance. {#r_DefaultDomainScope__table_svj_pjk_dy__entry__2} | Property | Details | |-|-| | glide.sys.domain.skip_domain_insert_businessrules | Specifies the domain scope for business rules executed on the domain table. In new activations of domain separation, the property default is true and business rules are determined by the session domain. In existing implementations, the property default is false and the business rules are determined by the newly created domain's hierarchy. * Type: true \| false * Default value: True in new domain activations starting with Jakarta. False in existing implementations. {#r_DefaultDomainScope__ul_vvj_pjk_dy} | | glide.sys.domain.skip_non_global_businessrule_if_nodomain | Ensures that only bus.rules from global domain are executed when using queryNoDomain() or when table is not domain-separated, so you can skip any other business rules * Type: true \| false * Setting the property to false restores the old behavior and doesn't align with ServiceNow® recommended practices. * Recommended: Domain-separate your tables; always try to use the record's domain rather than the session domain. {#r_DefaultDomainScope__ul_ukb_315_dlb} | [Table 2. Domain scope properties for business rules executed on the domain table] {#r_DefaultDomainScope__table_svj_pjk_dy} ## User preferences In addition, user administrators can set the following user preference globally or on a per-user basis: {#r_DefaultDomainScope__table_kgr_jlp_1r__entry__4} | Preference | Category | Updated By | Details | |-|-|-|-| | glide.domain.session_scope | Domain | Admin Only | When true, sets the default scope to the user's session domain rather than the record's domain. When false, the default scope is the record's domain. Users with the domain_expand_scope user role can still change the domain scope as needed. * Type: true \| false * Default value: false {#r_DefaultDomainScope__ul_b2z_cmp_1r} | | glide.domain.session_scope_notification | Domain | Admin Only | When true, displays a visual cue that record values include an expanded domain scope. When false, the notification is hidden. * Type: true \| false * Default value: true {#r_DefaultDomainScope__ul_ltz_bmp_1r} | [Table 3. Domain scope user preferences] {#r_DefaultDomainScope__table_kgr_jlp_1r} **Related concepts** * [Domain separation application properties](https://www.servicenow.com/docs/OwX5qxpT9Pc19LAUwUjk3Q "The Domain Separation plugin has two new tables to give service providers more flexibility in customizing their applications that use domain separation. These tables are the System Application Property table [sys_application_property] and the System Application Property Value table [sys_application_property_value].")