Skip to main content
Solved

Region-Based Access Control in Talent Acquisition – Is It Supported in Eightfold?

  • February 19, 2026
  • 1 reply
  • 8 views

Is it possible in Eightfold to manage Talent Acquisition access based on regions? Specifically, we would like to create regions (for example, grouped by country) and assign these regions to TA roles such as recruiters, TA leaders, etc., so that users only have visibility to positions within their assigned regions.

Best answer by dkreiger

Hi ​@Jasbir_336630, Yes. TA user visibility can be restricted by region. You can define “regions” as grouped geographies and then scope what each TA user group or role can see so they only access requisitions/positions (and related candidates) that match those geographic criteria.

How this is supported in Eightfold

Eightfold access control is structured across three key layers, with the most relevant for this use case being Data Access Segmentation:

  • Role-Based Security (RBAC): Controls what actions a user can take (view, edit, outreach, export, etc.)

  • Data Access Segmentation: Controls what data a user can see (including geographic visibility)

  • Confidential Access: Provides an additional layer for highly restricted items (e.g., executive searches)

Regional visibility model (recommended approach)

This is typically configured using User Groups + Access Criteria:

  • Create User Groups aligned to regional recruiting structures (e.g., EMEA Recruiters, APAC Recruiters, Americas TA Leaders)

  • Assign appropriate roles (Recruiter, TA Leader, etc.) to those groups

  • Apply Access Criteria to filter visibility based on geographic attributes (such as country or location), and/or other relevant fields

Eightfold supports the common model of “same role, different data access” (e.g., EU vs. AUS recruiters), which aligns directly with regional segmentation needs.

What fields can be used for regional rules?

Segmentation can be based on:

  • Standard fields like location, country, or business unit

  • Custom attributes, such as a defined “Region” field that groups multiple countries under a single label

Notes / considerations

  • If your goal is to restrict visibility to only requisitions/positions within a region, ensure access criteria are based on position/requisition geography fields, not just candidate attributes

  • For additional restrictions (e.g., executive roles), Confidential Access can be layered on top of RBAC and segmentation for tighter control

 

I hope this was helpful. Please let me know otherwise. 

1 reply

dkreiger
Community Manager
  • Community Manager
  • Answer
  • March 17, 2026

Hi ​@Jasbir_336630, Yes. TA user visibility can be restricted by region. You can define “regions” as grouped geographies and then scope what each TA user group or role can see so they only access requisitions/positions (and related candidates) that match those geographic criteria.

How this is supported in Eightfold

Eightfold access control is structured across three key layers, with the most relevant for this use case being Data Access Segmentation:

  • Role-Based Security (RBAC): Controls what actions a user can take (view, edit, outreach, export, etc.)

  • Data Access Segmentation: Controls what data a user can see (including geographic visibility)

  • Confidential Access: Provides an additional layer for highly restricted items (e.g., executive searches)

Regional visibility model (recommended approach)

This is typically configured using User Groups + Access Criteria:

  • Create User Groups aligned to regional recruiting structures (e.g., EMEA Recruiters, APAC Recruiters, Americas TA Leaders)

  • Assign appropriate roles (Recruiter, TA Leader, etc.) to those groups

  • Apply Access Criteria to filter visibility based on geographic attributes (such as country or location), and/or other relevant fields

Eightfold supports the common model of “same role, different data access” (e.g., EU vs. AUS recruiters), which aligns directly with regional segmentation needs.

What fields can be used for regional rules?

Segmentation can be based on:

  • Standard fields like location, country, or business unit

  • Custom attributes, such as a defined “Region” field that groups multiple countries under a single label

Notes / considerations

  • If your goal is to restrict visibility to only requisitions/positions within a region, ensure access criteria are based on position/requisition geography fields, not just candidate attributes

  • For additional restrictions (e.g., executive roles), Confidential Access can be layered on top of RBAC and segmentation for tighter control

 

I hope this was helpful. Please let me know otherwise.Â