Hi @arulsubra, you may need global entity filters, not just the people_search access check.
So for a strict sandbox validation, test all three paths:
- People link is hidden from Career Hub nav.
/careerhub/search/people?... or /careerhub/people/search does not load for restricted users. - Direct profile links show only the intended reduced
otherProfile fields.
Recommended sandbox implementation sequence
- Identify the restricted population field, e.g.
location_country, employee_type, custom_info.talent_profile, business unit, etc. - Configure
career_hub_base_config > access_check > people_search. - Wire
top_nav People route to peopleSearch / people_search. - Configure
career_hub_profile_config otherProfile to hide personal-detail sections. - Test with:
- an allowed employee
- a restricted employee
- direct People Search URL
- direct employee profile URL
If the goal is no employee discovery at all, use people_search: default_access: false, remove/hide the nav item, and strip down otherProfile to only the minimum fields required by the customer’s policy.