Hi Pranjal,
So if i understand your requirement right, you want to Hide groups, even if the user has pps_resource role, right?
If this is the right understanding, below are 2 options, based on your risk appetite and known reason and rationales, you can pick any.
Project Workspace uses UI Builder + Workspace data providers, hence ACLs and UI Policies DO NOT fully control this list, the most effective solutino is data-level filtering.
Solution OPTION 1 (My personal recommendation): Filter at Resource Data Level
Project Workspace pulls resources from Resource Management tables, Groups appear because, Group records are treated as generic resources, Filter out records where resource is a group.
How to do it
Create a Before Query Business Rule on Resource table used by workspace
(Usually resource_allocation or related view table)
current.resource IS NOT INSTANCE OF sys_user_group
OR to be more safe
resource.sys_class_name != 'sys_user_group'
OPTION 2: Workspace Data Provider Filter (Advanced / Clean) -
best if you want zero backend impact and you have required UI Builder access
If you want a workspace-only solution (no global impact)
Where UI Builder, Project Workspace, Locate Resource List component, Find Data Provider / Query add filter Resource.sys_class_name != sys_user_group
OPTION 3: Hide via Client Script (NOT Recommended),
although client script is an option, but too risky and because I don’t recommend, hence wont even provide any procedure, you can check that online or through chatgpt if needed, even others you can google search or check for step by step procedure for recommended options on chatgpt or gemini.
