- 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
‎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
‎02-22-2023 10:52 AM
Can we hide the entire workspaces menu from the banner without restricting access or setting each workspace to inactive?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-04-2023 12:14 AM
Yes with Unified Menu Navigation table we can hide the entire workspaces tab hidden or role specific.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-21-2023 11:13 AM