- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2022 04:45 AM - edited 12-16-2022 04:50 AM
Workspaces: How to hide/ restrict users Workspace based on roles as per the below screenshot.
Workspaces menu on the instance banner, and this will display the available workspaces to the users, we have a requirement to restrict users (based on Roles) from accessing a specific workspace from the Workspaces menu on Next experience banner.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2022 05:14 AM - edited 12-16-2022 05:18 AM
Hi Vijay,
To hide a workspace, you can configure 2 read ACLs of ‘type:ux_route’
for that workspace and add required roles to allow users to access it.
- Read ACL type ux_route with name = now.<workspace URL path>.home
- Read ACL type ux_route with name = now.<workspace URL path>.*
For example:
To hide access to CSM/FSM workspace,
- Get the workspace URL Path by navigating to the table: "sys_ux_page_registry"
- URL path for the record: "CSM/FSM Configurable Workspace" is "cwf/agent"
- Configure one read ACL of type: "ux_route" with Name: now.cwf.agent.home and another read ACL type: ux_route with the Name: now.cwf.agent.* and add required roles to these ACLs in order to allow users with mentioned roles only can access the workspace.
- If the workspace URL contains "/" replace it with "." in the ACL name.
In the same way you can do this for the remaining workspaces as well.
Note: The above steps will hide the workspace from the banner Workspaces menu only.
Thanks,
Harish Kota
If the solution works for you, please hit like/Accept as solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday
Hi Community,
I am trying to restrict the visibility of a custom Next Experience workspace so that it only appears in the Workspaces header dropdown for users who hold a specific custom role ([Custom Role]). Standard itil users without this role should not see the workspace in the navigation bar.
Created 2 ACLs manually giving URL path (now.URLpath.* & now.URLpath.home)
I strictly followed ServiceNow's official Support Knowledge Article KB1167916 (How to manage workspace visibility in Unified Navigation), along with several other recommended Next Experience menu configuration steps, but the workspace remains visible in the header menu for itil users.
LINK ->
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1167916
Please let me know the solution for this as soon as possible.