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 Locations and Permissions: Locations and Location based Permissions
Locations Overview
This page shows all locations configured in your account. Every account starts with a default Headquarters location, which you can rename or expand by adding more locations.
From here you can:
- Add new locations with a defined name and address
- Use filters (Regions) to find specific locations
- Customize columns to display the information most relevant to your workflow
Locations form a core part of Harver’s permission system, recruiters only see Locations they are assigned to.
Add a new Location
When creating a new location, you can define all relevant details used for candidate assignment and recruiter permissions.
The most important fields are the following:
1. Location Name (mandatory)
Enter the name of the location as you want it to appear for recruiters and, if used in the candidate journey with Multi-Location Picker module, for candidates. This could be a store name, office location, or regional label.
2. Address (mandatory)
Search and select the full address for the location. This allows Harver to display it correctly throughout the platform and—if used—helps candidates pick the correct physical location.
3. Location ID / External Location ID (optional)
Add a custom Location ID.
This unique identifier can be appended to vacancy URLs so that candidates applying through that link are automatically pre-assigned to this specific location.
Location IDs can be used for several purposes:
-
Auto-assign candidates via URL parameters (Harver-First links)
When a Location ID is added to a vacancy URL and the journey does not use a Multi-Location Picker, candidates will be automatically assigned to the corresponding location — even if the vacancy is linked to multiple locations. -
Preselect the location when using a Multi-Location Picker
When a Location ID is included in the URL and the journey uses the Multi-Location Picker, the picker will automatically highlight and preselect the location from the URL. -
ATS integrations
Some ATS integrations rely on Location IDs for accurate synchronization and matching between Harver and the ATS. -
SSO-based recruiter assignment
Customers using Single Sign-On (SSO) may use Location IDs to automatically assign recruiters to specific locations based on identity attributes passed through SSO.
4. Users (optional)
Assign recruiters to the location.
Recruiters can only see and manage candidates who are assigned to the same location(s). You can add multiple recruiters as needed. You can also manage user permission in the User Management.
When a new Location is added, it s automatically set as Active.
Please note: Job Functions, Hiring Chance, Location Questions, and Availability Criteria are deprecated features. They remain visible only for backward compatibility, and we strongly recommend not using them in new setups.
Editing Locations
The Location details page allows you to manage everything related to a specific hiring location. From here, you can change the most improtant details:
1. Location Status
Enable or disable a location.
When Active, candidates can be assigned or apply to this location. When Inactive, candidates will not be able to apply, and the location will be excluded from the Candidate Journey (including location pickers).
2. Open Vacancies
View all vacancies currently linked to this location.
You can quickly switch each vacancy’s status between Active and Inactive directly from this page.
3. Location Name
Update the display name of the location.
This is visible internally and may also appear to candidates depending on your journey configuration.
4. Location ID / External Location ID (optional)
This is a unique identifier that can be added to vacancy URLs so candidates applying through those links are automatically assigned to the correct location.
Important:
This ID may also be used by ATS integrations, SSO configurations, or other automated processes.
Changing it can disrupt those connections, so update it only when you are certain it will not impact existing integrations or workflows.
5. Other fields and settings
Please note: Job Functions, Hiring Chance, Location Questions, and Availability Criteria are deprecated features. They remain visible only for backward compatibility, and we strongly recommend not using them in new setups.
Availability Criteria
Availability Criteria are used in multi-location hiring, where a single vacancy is linked to multiple locations and candidates select which locations they want to apply to through the Multi-Location Picker module.
By setting a minimum number of hours per week, you define the minimum availability requirement a candidate must meet for a given location.
When candidates use the Multi-Location Picker:
- They can filter the list of available locations by the minimum hours they are able to work.
- Only locations whose availability requirement matches or falls below the candidate’s availability will be shown as eligible options.
This helps candidates make informed choices and ensures that recruiters only receive applications from candidates who meet the expected availability for each location.
Users Assigned to a Location
On each location, you can see all recruiter users who have access to manage candidates for that specific location.
There are two types of assignments Direct or via a Region.
Directly Assigned Users
These users were explicitly added to the location. You will see an X icon next to their name. Clicking the X removes their access to this location immediately.
Users Assigned via a Region
These users appear with a (Region) label next to their name. Their access comes from the region the location belongs to. Since their permission is inherited from the region, you cannot remove them from the location directly. To remove their access, you must either: Remove the user from the region or Change the location’s assigned region.
More about Regions.
This ensures consistent and predictable permission management when regions are used.