UI view only visible to specific groups
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi! I have a created a UI view for the Requested Items list and I want it to be visible only to two specific groups. I checked the UI View configurations but only one group can be added. Tried using View Rule but it seems like it is replacing the default view and I don't want this to happen. I've read about adding role to the view, but is there other way without doing this? Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi @Momiji ,
The clean OOB solution is to use a dedicated role. The Group field on the UI View supports only one group, and there is no OOB multiple-group related list for this requirement.
Recommended configuration:
1. Create a custom role, for example:
x_company.ritm_special_view
2. Assign this role to both required groups through the Roles related list on each Group record.
3. Navigate to:
System UI > Views
4. Open your custom Requested Item view.
5. Leave the Group field empty and add the new role in the Roles field.
6. Use a unique view name, such as:
ritm_special_view
This avoids unintentionally restricting another table that uses the same view name.
7. Do not create a View Rule unless you want to automatically force users into that view. View Rules determine which view is displayed and can override the default view or saved user preference; they are not the correct mechanism for controlling which views appear in the view selector.
Expected result:
Users in Group A
-> Receive the custom role
-> Can select the custom RITM view
Users in Group B
-> Receive the custom role
-> Can select the custom RITM view
All other users
-> Do not see the custom view
-> Continue using their existing/default view
Assigning a dedicated UI-only role to both groups is more maintainable than scripts containing group names or sys_ids.
Also note that a UI View is not a security control. It only changes the displayed fields or list columns. If any record or field data must be protected, configure the appropriate ACLs separately.
After making the change, test by impersonating:
- A user from Group A
- A user from Group B
- A user outside both groups
A View Rule is not required for this solution.
Hope this helps!
If this response helped, please mark it as Helpful.
If it resolves your issue, please Accept it as Solution.
Kind Regards,
Abhishek Pal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi there @Momiji
create a role, assign it to both groups, and restrict the UI View to that role. It's easier to maintain and is the recommended pattern.
Kind Regards,
Azar
Serivenow Rising Star ⭐
Architect@ KPMG.