Hire2Retire integration – Greenhouse Support

Hire2Retire is an employee lifecycle management solution. It helps manage user accounts in Identity Providers (IdPs), including Active Directory, Azure Active Directory, Google Workspace, and Okta, based on employee data in HRIS or ATS systems.

Hire2Retire’s integration with Greenhouse Recruiting enables the organization to manage user accounts in Identity Providers for any candidates in Greenhouse. When an Application’s status is changed to “Hired” (or any appropriate status configured on Hire2Retire) in GreenHouse, an account for the candidate will be created in the Identity Provider. If the Candidate or Application is updated, the changes are also synced to the Identity Provider system. When the offer is rescinded or revoked, the Identity account is terminated and then eventually deleted. Additionally, if the candidate is not hired in the HR system, the account in the Identity system gets terminated after the time configured on Hire2Retire. An early account creation helps internal teams prepare for the new hire and keep the identity updated as per the ATS system.

Create a Harvest API key

To configure the Hire2Retire integration, you’ll need to create a Harvest API key.

Follow the steps in this article to create the key and verify that the permissions below are selected when configuring the Hire2Retire integration.

Credentials

In the Create New Credential box, make the following selections:

API Type: Harvest
Partner: Hire2Retire or Unlisted Vendor
Description: Hire2Retire Harvest API Key

Permissions

Verify that the following permissions are selected for the Hire2Retire integration:

Applications
- GET: Retrieve Applications
- GET: List Applications
Candidates
- GET: Retrieve Applications
- GET: List Applications
Jobs
- GET: Retrieve Jobs
Custom Fields
- GET: Get custom fields

Use the Hire2Retire integration with Greenhouse Recruiting

Select Greenhouse as the ATS system and Cloud Only(Entra ID) as the Identity system. You can choose any of the supported Identity systems, we are using Entra ID for this guide.

Create connections with both applications. Follow the steps mentioned above in this document to create a Greenhouse API key.

Select the Greenhouse fields you want to be mapped in the Identity Profile. Select the report type and polling interval.

Configure the attributes on Entra ID using Greenhouse attributes and Hire2Retire’s powerful Data Mapping and Transformation capabilities. You can also link your workflow with an HCM workflow so that the users created for ATS candidates are further managed by the HCM workflows when they are onboarded as employees.

Configure the lifecycles that you want to be managed by Hire2Retire. We are configuring Onboarding, Profile Updated, and Rescind.

In the screenshot above, the password details for the Identity user are configured, and if the candidate is not hired in the HCM in 30 days, their Identity account will be terminated.

In the Screenshot above, the Group retention policy for the profile update of the identity users is defined.

The Application status in Greenhouse, for which the user is hired or rescinded in the identity, can be defined on the Employment Status page.

Hire2Retire can also assign group memberships based on attributes.

Hire2Retire can send emails for different lifecycles Configure the Emails to be sent, here we are configuring an email to be sent when the account is created.