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.
Connect Greenhouse
Hire2Retire uses Greenhouse's Partner Integration OAuth flow to authorize access. To configure the Hire2Retire integration, users can link their Greenhouse account with Hire2Retire.
Note: The Greenhouse user who authorizes the connection must have Site Admin permissions. For more details, refer to this guide.
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; this guide uses Entra ID as an example.
Create connections with both applications. To connect Greenhouse with Hire2Retire, users need to link their account in the following steps:
In Hire2Retire, go to the Identity tab and select the Greenhouse card.
Choose Partner Integration, name the connection, and click Link Account.
Log in to Greenhouse and review the requested permissions.
Check Authorize using a service account, then click Authorize.
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 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. This example configures 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 within 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. This example configures an email to be sent when the account is created.
You can also configure the workflow to create tickets in your ServiceDesk system.
Once you deploy the workflow, Hire2Retire will run the workflow as configured.
You can view the details of onboarded or terminated users on Identity Platforms for Greenhouse candidates.
Additional resources
For additional information or troubleshooting not covered here, use the following resources:
- Pricing: https://www.robomq.io/pricing/
- Sales email: sales@robomq.io
- Support email: support@robomq.io
- Support portal: https://robomq.atlassian.net/servicedesk/customer/portal/2
- Documentation: https://docs.robomq.io/Application/Greenhouse_API_Integration/