Resolving Domain Visibility Issues for domain_admin UsersIssue Users with the domain_admin role cannot see or access sub-domains. The expected behavior is that these users should be able to switch between their parent and all associated sub-domains using the domain picker UI. Expected Behavior: The domain selector (domain picker) is available in the UI.The domain_admin user can view and switch to any sub-domains from their parent domain context. Observed Behavior: Domain selector UI is not visible or not functioning.User is restricted to their default domain without access to sub-domains.ReleaseThe core property glide.ui.domain_reference_picker.enabled was introduced around the Madrid–Orlando timeframe and persists in all subsequent versions.CauseThis is not a role-based permissions issue. The issue is caused by incomplete domain picker enablement and missing domain visibility configurations.ResolutionTo resolve the visibility and access issue for domain_admin users, configure both the domain picker UI and domain visibility settings. 1. Enable the Domain Picker UI Step 1: Set Required System Properties Navigate to: System Properties > UI Ensure the following properties are set: glide.ui.domain_reference_picker.enabled = trueEnables the domain picker interface in the UI.glide.ui.domain_picker.role = domain_admin (optional)Restricts visibility of the domain picker to users with the specified role. Step 2: Refresh the User Session After making changes, instruct the user to log out and log back in to refresh their session. Step 3: Enable the Picker in Preferences Click the gear icon (Preferences) in the header.Check the box for "Show domain picker in header." If not visible, confirm the user's roles and the system property settings are correct. 2. Set Domain Visibility for Sub-Domain Access Even with the domain picker enabled, users must have explicit access to sub-domains. Option 1: Use the Domain Visibility Related List Navigate to Domain Administration > Domains.Open the parent domain record.In the Domain Visibility related list: Add entries for each sub-domain the user should access.You can assign visibility directly to users or to groups. Option 2: Assign Domain Visibility via Groups Create or use a user group that has domain visibility to the necessary sub-domains.Add the domain_admin user to that group. This is a scalable option for granting access to multiple users. To summarize, the glide.ui.domain_reference_picker.enabled property must be set to true in order to enable the domain picker interface in the ServiceNow UI. This is a required setting that activates the visual tool allowing users to switch between domains, which is essential for domain_admin users who need to manage multiple domains. The glide.ui.domain_picker.role property is optional but useful when you want to limit who can see the domain picker. By setting this to domain_admin, only users with the specified role will see and use the domain picker, adding an extra layer of control to your instance's user interface. The Domain Visibility related list is a required configuration. It ensures that users have explicit access to sub-domains by defining which domains are visible to them. Without entries in this list, even users with domain_admin roles may be unable to view or access domains beyond their default assignment. Finally, group-based domain visibility is an optional but highly effective strategy for managing access at scale. By associating users with groups that have domain visibility rights, administrators can streamline and centralize domain access control, making it easier to manage permissions across large teams or enterprise structures. Once both UI components and visibility settings are configured, domain_admin users will be able to switch between and manage all associated sub-domains.