How to enable domain picker for Requestor (with no role ) or set visibility for multiple domain?

[MD SAJID AKHTAR]

How to enable domain picker for Requestor (with no role ) or set visibility for multiple domains?

My instance is domain-separated environment where one user as a requestor (with no role) is part of 2 domains/accounts.
With Visibility domains, user can create the tickets under multiple domain, but he/she is not able to view the tickets, as their company can be set to only 1 account in the user table.

Need suggestions to enable domain picker on the banner for Requestor & also some work-around so that user will able to see the tickets for his supported accounts.

Thanks

[Jan Strama1]

Hi,

for the Access to the Domain Picker you can add a custom Role and then add this Role in the "glide.ui.domain_picker.role" System property which will allow the User to see the Domain Picker option in his Profile Settings

For the Access to the Domain you can create a "Domain Visibility" User group and add the  Domain the user(s) should get access to via the "visibility domains" related list. When the user is a member of the Group he can see records in both his and the added Domain:

Hope this is helpfull?

Best Regards

Jan

[MD SAJID AKHTAR]

Hello Jan,

I have created one custom role "Custom_Domain_picker" and added that role to the property & to the user profile as well.

But still no luck. Domain picker is not available to the user profile ( Requestor).

Please find the screenshot and let me know if I am doing anything wrong.

[NISCHITHH]

Yes. glide.ui.domain_picker.role is a valid ServiceNow system property, primarily associated with the UI16 domain picker. It controls which roles can access the domain picker.

However, if you are using Next Experience / Polaris, the relevant property is:

glide.ui.polaris.domain_picker.role

For example, to allow only users with the admin or a custom role:

glide.ui.polaris.domain_picker.role = admin,my_custom_role

The roles are specified as a comma-separated list.

Which property should be used depends on the UI:

UI16:
glide.ui.domain_picker.role

Next Experience / Polaris:
glide.ui.polaris.domain_picker.role

If the instance is using the Next Experience interface, I would check glide.ui.polaris.domain_picker.role first rather than glide.ui.domain_picker.role.