Service Graph Workspace View
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Use role-based access, not an ACL or page-wide audience.
ServiceNow documents that Dependency View requires the dependency_views role, while Service Graph Workspace itself is accessible with sn_cmdb_admin, sn_cmdb_editor, or sn_cmdb_user.
So the clean approach is:
- Remove dependency_views from users/groups that should not see/use Dependency View.
- Ensure only your CMDB Admin population receives dependency_views.
- Leave sn_cmdb_editor / sn_cmdb_user and their other roles unchanged, so the remaining Service Graph Workspace tools stay available.
ServiceNow also documents sn_cmdb_admin as the CMDB Administrator role — not cmdb_admin.
Dependency Views itself requires:
dependency_views
as the minimum role.
So your intended model should be:
sn_cmdb_admin
+ dependency_views
→ Dependency View available
sn_cmdb_editor / sn_cmdb_user
without dependency_views
→ Dependency View unavailable
→ Other permitted tools remain availableI would not customise the whole Service Graph Workspace page just to enforce this; ServiceNow already provides a specific role for Dependency Views. If the link still renders after removing dependency_views, then the next step is component visibility in UI Builder—ServiceNow officially supports conditional component visibility via dynamic binding or scripted properties.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
NO its not working i need to set restrictions to each and every option in below management tools
