Permissions: --

Product tier: Available for Expert subscription tier with the HRIS Link add-on

This document will describe new default integration functionality added to HRIS Link. Click here for the full release notes for all Greenhouse applications. 

Changes before September 29, 2021

We recently started recording HRIS Link changes in this document. The updates below represent impactful changes that occurred between the last release communication (May 26, 2021) and today.

See the following sections for more information

Adding openings to an already open Requisition

Can this option be be enabled/disabled?

No, this is standard integration functionality for HRIS Link.

Note: This option only applies if requisitions are enabled in Workday.

How does this change the integration behavior for HRIS Link using Position management with job requisitions?

Historically HRIS Link didn’t support adding positions to open requisitions after initial job creation. If a user were to add positions to the HRIS requisition, the additional positions would not appear in Greenhouse as new openings on the corresponding Greenhouse job. With this update, HRIS Link allows users to add positions to open requisitions in their HRIS and see those positions added as new openings in Greenhouse. 

See the below table for an in-depth look at integration functionality. 

Link Workflow

HRIS Link Report Values

Outcome

Notes

Update Job

HRIS Link Job import report contains less job openings than were present on Greenhouse job

No job openings are removed from the Greenhouse job in question.

 

HRIS Link Job import report contains the same number of job openings that are present on a Greenhouse job.

No change to openings on the open job in Greenhouse

The integration will not update or edit Position IDs that were historically on the report.

HRIS Link job import report contains more job openings than are present on the Greenhouse job.

New job openings are added to the Greenhouse Requisition/Job. The job openings in the HRIS Link report payload that are already present on the Greenhouse Job are not altered.

If the existing greenhouse job is closed, we will not add any new job openings.

SupportingJob_Post_Location for HRIS Link job import

Is this a configuration option that can be enabled/disabled?

No, this is standard integration functionality for HRIS Link. 

How does the integration behave with the new report header?

If an organization provides the report header of Job_Post_Location, the integration will be able to apply a job post location-based on Greenhouse office external id. 

Note: This feature only works if your organization leverages a structured job post location based on your organization's office list.

Sending invitation email when creating user accounts with User Sync

Is this a configuration option that can be enabled/disabled?

No, this is standard integration functionality for HRIS Link. 

How does the integration behave with the new report header?

This update will only affect new user creation. When the “send_email_invite” report header is included and the values provided meet the report specifications, organizations will be able to trigger invitation emails to users upon creation of their Greenhouse accounts via HRIS Link.

Maintaining Office and Department Hierarchy with HRIS Link

Is this a configuration option that can be enabled/disabled?

No, this is standard integration functionality for HRIS Link. 

How does the integration behave with the new external_parent_id report header?

This update will only affect new department and office creation. HRIS Link will not maintain office or department hierarchy updates that happen after initial office/department creation with HRIS Link.

When creating an office or department, HRIS Link will audit the report to see if the report header external_parent_id is included in the report for the new office or department. If the new office or department has a valid “parent_external_id” included, the office or department will be created in Greenhouse subsidiary to the office/department with the corresponding external_parent_id in Greenhouse. 

HRIS Link for office and department import requiring external_id

How does this affect the HRIS Link integration?

Previously Greenhouse suggested that customers include external_ids for offices and departments that utilize HRIS Link. When HRIS Link expanded functionality to support hierarchy creation, the external_id report header became required for HRIS Link.

If a new office or department is created in the HRIS without an external_id and appears on the HRIS Link report, the integration will ignore said office or department on that integration run. '

Update to HRIS Link Partnership API key 

On September 23, 2021, the Greenhouse Technical Consulting team works with the Greenhouse Partnership team to create an API key that is automatically provisioned with the appropriate API key permissions for the HRIS Link integration. As the integration expands functionality with additional configuration options, the API key permissions need to be updated.  

In this case, Greenhouse updated the following API key permissions:

  • GET: List Job Post for Job
  • DELETE: Delete job
  • POST: Add hiring team member

How does this affect the HRIS Link integration?

If you are a current HRIS Link client, you will want to check the API key permissions for the Harvest API key that is used for the integration to ensure that the above API Key permissions are equipt.

If you have further questions about this update reach out to the Greenhouse Support team.