Conditionally Make a Guided Tour Available based on User Role or Group

Jordan Humphrey
Giga Expert

Hello, I am looking to create a separate tour for our "ITIL" users on our new Employee Service Center portal but also need to have a tour specifically designed for "non-ITIL" users who do not have a "role" on their profile (basically, the "Everyone" default).

 

When setting up a tour, it appears I'm restricted to either selecting those who have a role OR to leave the filter blank which shows it for everyone. The problem is, the ITIL users will see both instances of the tour twice (the ITIL version and the non-ITIL version). Currently, the way the users are imported into our sys_user table (via AD integration), there is not a default "role" assigned. In previous years at the last company I worked for, I always at a minimum gave everyone the "user" role. What is the best practice/recommendation here?

 

In addition, is there a way to differentiate based off user's preferred language so the properly translated tour appears for them?

1 ACCEPTED SOLUTION

Ravish Rawat
ServiceNow Employee
ServiceNow Employee

Explicit Roles can help in your scenario and you can restrict using snc_internal. Make sure to test it thoroughly so not to break any existing scenarios due to the addition of new roles. 

 

com.glide.explicit_rolesplugin provides the snc_external and snc_internal roles.

When this plugin is activated:
  • All existing users are automatically assigned the snc_internal role. This role does not change existing access levels or system behavior. Rather, it provides a category to differentiate internal users from external users. All internal users maintain the same level of access as before the plugin was activated.

  • Newly created users are automatically assigned the snc_internal role when they first attempt to log in to the instance, unless they have been explicitly assigned the snc_external role. You can add the snc_external role to a new user before they first log in to the instance to provide external user rights.

View solution in original post

2 REPLIES 2

Ravish Rawat
ServiceNow Employee
ServiceNow Employee

Explicit Roles can help in your scenario and you can restrict using snc_internal. Make sure to test it thoroughly so not to break any existing scenarios due to the addition of new roles. 

 

com.glide.explicit_rolesplugin provides the snc_external and snc_internal roles.

When this plugin is activated:
  • All existing users are automatically assigned the snc_internal role. This role does not change existing access levels or system behavior. Rather, it provides a category to differentiate internal users from external users. All internal users maintain the same level of access as before the plugin was activated.

  • Newly created users are automatically assigned the snc_internal role when they first attempt to log in to the instance, unless they have been explicitly assigned the snc_external role. You can add the snc_external role to a new user before they first log in to the instance to provide external user rights.

jon421553
Kilo Contributor

Hi! Great idea to create separate tours for ITIL and non-ITIL users. To avoid ITIL users seeing both, assign a default “snc_internal” role to everyone via AD integration, then set the non-ITIL tour for only that role. For language, use translated strings in the sys_ui_message table tied to user profiles. Why aren’t you using a default role this time?