New role contained within a role not applied until refresh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2015 02:13 PM
Hi Everyone,
All support staff have the ITIL role. We recently built a new table and gave access to it via role B. We then modified the ITIL role so that it contained role B. I was surprised to find out that support staff didn't automatically inherit role B. Rather, it seems I need to remove the ITIL role from their account and re-add it in order their accounts to recognize role B.
Is this normal within the world of permissions or ServiceNow? It seems odd to me, but I'm slightly new to the game. Is there a more proper or best practice for handling the scenario?
Thanks,
Scott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2015 07:26 AM
DOH, I always forget to try stuff in a developer instance. I gave it a whirl reproducing the same steps and it worked a-ok.
- Activated Release Management Plugin. This created created the rm_tables/roles.
- Confirmed release_v2_user contains the rm roles
- Gave Service Desk and Database each the ITIL role
- Added release_v2_user to itil
- Checked Beth within the Database group and she had all the rm roles.
Maybe it's a glitch within Eureka, or we somehow did something super funky to cause this in our instances.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2015 07:28 AM
Check the business rules on user roles table. Also, raise a HI ticket if you find nothing. May be a known problem. Who knows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2015 06:44 AM
Should anyone else run into this, PRB588766 exists for this issue in Eureka. As mentioned above, it was fixed in Fuji.