Property reference

`glide.sys.domain.use_record_domain`

Restricts data scope to the domain assigned to each record. The default is true, so record-domain scoping is active unless the domain-specific data or process properties override this setting.

Default: true
Type: boolean
Application: Not stated
Category: Security & Access Control

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	When active, domain scope for data follows each record's domain; the domain-specific data or process properties make this setting unused when either is true.
What area does it affect?	Domain separation and data access
What does the default mean?	The default value is "true", which means this behavior is enabled by default.
When should you review it?	Review when changing domain data scoping or configuring the domain-specific data and process properties.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name	`glide.sys.domain.use_record_domain`
Type	boolean
Application	Not stated
Default value	`true`
Description	Domain legacy

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs Available system properties ↗

Context preview Snippet 1

... be trademarks of the respective companies with which they are associated. 95 • Type: string • Default value: This field should be left empty. • Location: System Property [sys_properties] table glide.sys.domain.use_record_domain Domain legacy • Type: true | false • Default value: true • Location: System Property [sys_properties] table glide.sys.domain.use_record_domain_for_client_scripts Domain legacy • Type: true | false • Default value: false • ...

Brazil docs Domain system properties and user preferences ↗

Context preview Snippet 2

... in the United States and/or other countries. Other company names, product names, and logos may be trademarks of the respective companies with which they are associated. 1489 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 For a full list ...

Additional source link Another external reference for this property

Open reference

More in `glide.sys`

Other properties in the same namespace.

glide.sys.domain.domain_change_notify Controls the legacy domain-change notification behavior; this setting is not used when glide.sys.domain.use_re glide.sys.domain.include_domain_condition_on_join This property controls the inclusion of domain separation conditions in join queries, ensuring compliance with glide.sys.domain.no_change_roles This property specifies if roles can be modified in a domain-separated setup, impacting role assignment and se glide.sys.domain.skip_domain_insert_businessrules This property configures whether business rules for domain inserts are executed based on the session domain or glide.sys.domain.use_record_domain_for_client_scripts Determines whether domain handling for client scripts uses the domain of the associated record; the property i glide.sys.domain.use_record_domain_for_data It limits the visibility of related data to the domain of the record being accessed, enhancing security and da glide.sys.domain.verbose It activates detailed domain logging and debug messages, which assist in identifying and resolving domain sepa glide.sys.fencing.restricted_caller_access.invalidation_mode Chooses whether a database listener invalidates Restricted Caller Access records when an update set commits so

All 28 properties in glide.sys →