Concept: Guidelines for Constrained Prospect Security by Country

Constrained prospect security by country provides a way to restrict which prospect and candidate profiles recruiters can access. It is designed for use cases where customers need to limit visibility based on the prospect's country of residence. This is especially useful for companies that operate in multiple countries and have regional recruiters who should only be able to view and manage prospects in their assigned region. Refer to Steps: Set Up Constrained Prospect Security by Country for step by step guidance to configure this feature.

Considerations:

Constrained prospect security by region applies only to prospects and candidates with prospect records. Constrained security will not apply if a job application exists without a prospect record.
Regions can be inactivated but not deleted. Keep this in mind from a maintenance perspective.
Only 1 default region is allowed, and default regions can't be inactive. To inactivate a default region, ensure it's not set to
Default
.
Assign roles to the default region to ensure that prospects from any unassigned country are accessible.
Allow 1 to 2 hours for changes to propagate before constrained security takes effect after you create or edit regions, assign roles, or add/remove location hierarchies to regions.
The
Candidate Data: Personal Information
domain has also been extended to work with constrained security groups. You can add all security group types that are allowed on the
Candidate Data: Job Application
domain.
To achieve constrained prospect access, remove unconstrained security groups from these domains:
Candidate Data: Job Application
Job Requisitions for Recruiting
Recruiting Agency Careers Self-Service
This feature is OX 2.0 enabled.
Customers who currently use candidate pools with prospects from various countries and regions in a single pool might want to re-evaluate their setup to achieve constrained security by country.