{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":41771,"path":"platform-security/r_DefaultDomainScope.md","title":"Domain system properties and user preferences","bundle":null,"doc_type":null,"release":"australia","body":"\n# Domain system properties and user preferences\n\nAdministrators have access to properties and user preferences that control domain scope.\n\n## Properties\n\nNew 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.\n\n<table id=\"table_zqj_nkp_1r\"><thead><tr><th>\n\nProperty\n\n</th><th>\n\nDetails\n\n</th></tr></thead><tbody><tr><td>\n\nglide.sys.domain.use\\_record\\_domain\\_for\\_processes\n\n</td><td>\n\nRestricts 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\n-   Default value: true\n-   Location: System Property \\[sys\\_properties\\] table\n\n</td></tr><tr><td>\n\nglide.sys.domain.use\\_record\\_domain\\_for\\_data\n\n</td><td>\n\nRestricts domain scope to the record's domain for all data.-   Type: true \\| false\n-   Default value: true in new domain activations from Fuji onwards \\(upgrades from instances older than Fuji do not have this property in the table\\)\n-   Location: System Property \\[sys\\_properties\\] table\n\n</td></tr></tbody>\n</table>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:\n\n-   **glide.sys.domain.use\\_record\\_domain**\n-   **glide.sys.domain.use\\_record\\_domain\\_for\\_client\\_scripts**\n-   **glide.sys.domain.domain\\_change\\_notify**\n-   **glide.sys.domain.no\\_change\\_roles**\n\nFor a full list of properties see [Available system properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/r_AvailableSystemProperties.md).\n\n**Note:**\n\nIn 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.\n\n<table id=\"table_svj_pjk_dy\"><thead><tr><th>\n\nProperty\n\n</th><th>\n\nDetails\n\n</th></tr></thead><tbody><tr><td>\n\nglide.sys.domain.skip\\_domain\\_insert\\_businessrules\n\n</td><td>\n\nSpecifies 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\n-   Default value: True in new domain activations starting with Jakarta. False in existing implementations.\n\n</td></tr><tr><td>\n\nglide.sys.domain.skip\\_non\\_global\\_businessrule\\_if\\_nodomain\n\n</td><td>\n\nEnsures 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\n-   Setting the property to false restores the old behavior and doesn't align with ServiceNow® recommended practices.\n-   Recommended: Domain-separate your tables; always try to use the record's domain rather than the session domain.\n\n</td></tr></tbody>\n</table>## User preferences\n\nIn addition, user administrators can set the following user preference globally or on a per-user basis:\n\n<table id=\"table_kgr_jlp_1r\"><thead><tr><th>\n\nPreference\n\n</th><th>\n\nCategory\n\n</th><th>\n\nUpdated By\n\n</th><th>\n\nDetails\n\n</th></tr></thead><tbody><tr><td>\n\nglide.domain.session\\_scope\n\n</td><td>\n\nDomain\n\n</td><td>\n\nAdmin Only\n\n</td><td>\n\nWhen 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\n-   **Default value**: false\n\n</td></tr><tr><td>\n\nglide.domain.session\\_scope\\_notification\n\n</td><td>\n\nDomain\n\n</td><td>\n\nAdmin Only\n\n</td><td>\n\nWhen true, displays a visual cue that record values include an expanded domain scope. When false, the notification is hidden.-   **Type**: true \\| false\n-   **Default value**: true\n\n</td></tr></tbody>\n</table>**Related topics**  \n\n\n[Domain separation application properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/ds-application-properties.md)\n\n"}}