How can we help you?

RolePoint

RolePoint provides organizations with a VIP referral experience for employees and candidates. Greenhouse Recruiting's integration with RolePoint allows your organization to let employees refer candidates to all open positions in Greenhouse, upload candidates to Greenhouse from Rolepoint, and view high-level statuses in RolePoint based on a candidate's stage in Greenhouse. In this article, we will cover:

Note: Greenhouse Recruiting offers its own built-in referral widget. To opt out of the feature please contact your Greenhouse Recruiting Customer Success Manager.

 

Configure User Setup Permissions in Greenhouse Recruiting

In order to enable the Greenhouse/RolePoint integration, you will need the developer permission Can manage ALL organization’s API Credentials.

Contact a Greenhouse user in your organization with Site Admin level permissions with the additional user-specific permission Can edit another user's advanced permissions to apply the API credential management permission to your account. Have the user with Site Admin level permissions edit your user account's permissions by navigating to the Configure icon configure.png > Users > Your Name.

1.png

The user with Site Admin level permissions should navigate to the Permissions panel on your user page and expand the Developer Permissions dropdown menu. 

Select Can manage ALL organization’s API Credentials so that a check is in the checkbox. When finished, click Save.

Screen_Shot_2019-06-19_at_10.04.39_AM.png

Repeat as necessary for any other user that should have access to set up the integration.

 

Create a Harvest API Key for the Greenhouse/Rolepoint Integration

To create a Harvest API key for the integration, click on the Configure icon configure.png in the upper right-hand corner. Navigate to Dev Center on the left-hand panel.

From the Dev Center page, click API Credential Management.

3.png

From the API Credential Management page, click Create New API Key to generate the API key for RolePoint.

4.png

From the Create new credential dialog box, give your API key a name and select Harvest from the Type dropdown menu. When finished, click Create.

5.png 

On the Manage API Key Permissions page, give the API Key the following permissions.

  • Applications
    • GET: List Applications
    • GET: Retrieve Application
    • PATCH: Update Application
    • POST: Advance Application
    • POST: Move Application
    • POST: Moves Application to Job
  • Candidates
    • GET: List Candidate
    • GET: Retrieve Candidate
    • PATCH: Edit Candidate
    • POST: Add Attachment
    • POST: Add Candidate
    • POST: Add Candidate Application
    • POST: Add Notes
    • POST: Add Prospect
    • PUT: Merge Candidates
  • Job Posts
    • GET: List Job Posts
    • GET: Retrieve Job Post
    • GET: List Job Posts for Job
  • Jobs
    • GET: List Jobs
    • GET: Retrieve Job
    • GET: Hiring Team
  • Sources
    • GET: List Sources
  • Users
    • GET: List Users
    • GET: Retrieve User

When finished, click Update

Your Harvest API key for the Greenhouse/RolePoint integration is created and configured. Provide your Harvest API key to your RolePoint implementation manager.

Screen_Shot_2019-10-11_at_4.27.45_PM.png 

 

Create RolePoint User Account In Greenhouse Recruiting

For certain requests, such as creating a note on the candidate activity feed, RolePoint is required to provide a User ID on which the note should be posted on-behalf-of. This User ID is for auditing purposes; therefore, you will also need to create a user called RolePoint using the following email:

ats-credentials+[yourcompany]@rolepoint.com

Click here for more information on how to create a new user in Greenhouse Recruiting 

When finished, provide the User ID to your RolePoint implementation manager. 

Screen_Shot_2019-10-11_at_4.36.23_PM.png 

 

Create RolePoint Source in Greenhouse Recruiting 

As RolePoint imports candidates into Greenhouse Recruiting, RolePoint would like to ensure that your referred candidates are accurately tracked. To do this, you can create a custom source (ie. RolePoint, Talent Connect, etc) for your referred candidates. 

 Screen_Shot_2019-10-11_at_4.43.45_PM.png

When finished, provide the name of the source to your RolePoint implementation manager.  

  

Jobs Feed

In order to display jobs in your referral portal for employees to refer candidates to, RolePoint syncs jobs information from Greenhouse twice a day. RolePoint typically pulls jobs that are open and posted on the company job board; however, RolePoint can utilize specific job attributes in Greenhouse to filter the jobs displayed in your referral portal. If you would like to add additional filters, please define them below:

  • ie. Job Folder = Approved
  • ie. Job Posting Status = Posted
  • ie. Req Type = Full-Time
  • ie. Job Board = Company Montreal, Company

RolePoint obtains the following information from Greenhouse Recruiting to display to your employees. If there are custom fields that we should use instead of the Greenhouse equivalent fields, please indicate them below in the right column:

Screen_Shot_2019-07-15_at_3.54.13_PM.png

 

Candidate/Referral Insert

With the Harvest API, RolePoint is able to import the referred candidate into either a specific job or as a prospect by submitting the following:

 
  • First Name
  • Last Name
  • Email Address
  • Telephone
  • Resume
  • Social URLs (Facebook, LinkedIn, etc – optional)
  • Endorsement Strength & Text (optional)
  • Source (RolePoint & Referrer Info)

  

Candidate Status

RolePoint will pull the current status of the candidate on an application from Greenhouse Recruiting. This status will be emailed to employees to update them on how their candidate is progressing. The standard statuses that RolePoint displays to employees are:

  • New
  • Contacted
  • Under Assessment
  • Hired
  • Archived

You will need to obtain a list of all possible dispositions in Greenhouse Recruiting and define which RolePoint status each disposition should be mapped to and/or add additional statuses that we should display to employee.

Screen_Shot_2019-07-15_at_3.55.03_PM.png 

*Not all statuses need to be used/mapped.