Locations are a core component of Harver’s permission and visibility model. They function as user groups that determine which candidates a recruiter can see and manage. Recruiters assigned to a specific location can only view candidates who are also assigned to that same location.
You can find more information about creating and managing locations here: [TODO]
What Are Locations?
Locations represent logical groups within an account. While they can reflect real-world geographic locations (e.g., Paris, New York, Headquarters or an actual physical store location), they are primarily used to control access and segment candidates inside Harver.
At least one location is required in every account to ensure that vacancies and candidates can always be associated with a valid user group.
Default Location: Headquarters
When a new account is created, Harver automatically adds a default location named “Headquarters”.
You can rename, delete, or add additional locations as needed. This location ensures that the account always has a valid base for permissions and candidate assignment.
Why Locations Matter
Locations influence three key areas of the platform:
-
Who can see which candidates
A recruiter can only see candidates who share at least one location assignment with them.
This enables data partitioning, useful for multi-region customers or distributed hiring teams. -
How candidates are assigned
Candidates inherit their location from the vacancy they apply to.
If only one location is linked to the vacancy, the candidate is assigned to that location automatically—without needing to choose anything in the flow. -
How vacancies are controlled
When creating a vacancy, you must select at least one location.
This requirement ensures every candidate who applies has a valid location assignment.
Using a Single Location for Simplicity
If your customer does not require complex visibility rules, the simplest setup is to use one single location for the entire account (e.g., Headquarters).
When all recruiters and all vacancies share the same location:
- All candidates are automatically assigned to that location
- All recruiters can see all candidates
- No location picker is shown to candidates
- Permissions remain simple and unobtrusive
This setup creates the cleanest and most frictionless experience for both recruiters and administrators.
Multiple Locations for Structured Visibility
If customers have different recruiting teams or regions, they can create additional locations such as:
- Retail – Region West
- Corporate Roles
- Manufacturing Plant A
- Seasonal Hiring – EU
Recruiters assigned to only one of these locations will see only the candidates associated with their location or team, ensuring compliance and reducing clutter.
A Region is a group of Locations.
Multi-Location Recruitment: Locations, Regions, and User Roles
Many retail and multi-location customers operate multiple physical stores or offices, each hiring candidates for their own site. In these environments, a candidate’s physical distance from a store often matters, and hiring responsibilities are distributed across different local roles.
Harver’s Locations and Regions structure is designed to support this type of recruitment efficiently and securely.
What is a Location for retail/hospitality?
A Location represents a single physical site (e.g., a store, restaurant, warehouse, or office) with a specific address.
Locations are used to:
- Assign candidates to the exact store they will work at
- Allow local managers (“Location Managers”) to see only candidates for their store
- Segment hiring operations across hundreds of locations
Examples:
- Store #148 – Amsterdam, Damrak 12
- Store #23 – Rotterdam Central
Each candidate applying for a job must be associated with at least one Location.
What is a Region for retail/hospitality?
A Region is a group of Locations. A user assed to a reagion has access to all locations linked to that region.
Recruiters with Region(s) assigned often referred to as Reagion Managers.
A region can include:
- multiple locations overseen by a regional team
- or hundreds of stores for large enterprises
Regions help customers organize hiring responsibilities and provide a layer for regional oversight.
Examples:
- North Region – NL (42 stores)
- Paris Metro Region (12 locations)
- Midwest Region – US (380 stores)
How Candidates get assigned to Locations
Candidates can be assigned to Locations in two different ways, depending on whether the Location Picker module is used in the Candidate Journey.
1. Automatic assignment (without Multi-Location Picker)
If the vacancy has only one Location assigned, and there is no Location Picker module in the journey, then:
- The candidate is automatically assigned to that Location when they apply.
- The assignment is invisible to the candidate, it happens in the background.
- This setup is ideal for simple accounts or single-location hiring.
Example: A vacancy is linked to Headquarters only → every candidate will be assigned to Headquarters automatically.
If the vacancy has multiple Location assigned, and there is no Location Picker module in the journey, then:
- The candidate is automatically assigned to all Location of the vacancy when they apply.
- The assignment is invisible to the candidate, it happens in the background.
- This setup is ideal for simple accounts or for multi-location customers where multiple stores or recruitment teams share the same vacancy and need access to a shared candidate pool.
Example: A vacancy is linked to both Team A and Team B → every candidate will be assigned to Team A AND Team B automatically. Reacruiters from both teams can see all candidates who apply.
2. Candidate selection via the Multi-Location Picker mosule
If the vacancy has multiple Locations assigned, and the journey includes a Location Picker module, then:
- The candidate will be presented with a Location selection step.
- They choose the store, office, or site they want to apply to.
- Harver assigns the candidate to the Location they selected.
Example: A vacancy is linked to Store A, Store B, and Store C. The candidate sees the picker → selects Store B → gets assigned to Store B.
For more information on the Multi-Location Picker pelase visit Multi-Location Picker