Reach Platform HRIS Integration Details

Paradigm Reach platform customers are able to integrate their HRIS platforms with their Paradigm Reach accounts to automate user management. Paradigm has partnered with Merge, a unified API for HRIS integrations, so we can support integrations with 27+ of HRIS platforms.  

Why you should integrate your HRIS with Reach 

  1. Save Paradigm Reach admins hours each week in manual user management 
  2. Reduce data entry errors 
  3. Increase confidence the right users are being provisioned in Reach and enrolled in the correct Assignments
  4. Ensure data is being synced securely and efficiently
  5. Enroll team members in learning journeys automatically based on HRIS triggers

Supported Use Cases: User Provisioning

Automatically add new employees to Reach on their start date

  • When Reach recognizes a new employee in your HRIS platform, that user will automatically be added to Reach on their start date. 
  • By default, Reach will also automatically invite the new user to Reach so they are able to login right away, but you can select to add them to Reach only and not give them access to Reach yet. Please note that users must be invited to Reach in order to be enrolled in Assignments. 
  • You will have the option to sync all of the users in your HRIS to Reach, or only add users with specific employment types. For example, if you only have your full-time employees in Reach and not contractors, you can select to only sync your full-time employees. 

Automatically update user metadata in Reach based on changes in HRIS

  • If your employees move locations, get promoted, or change departments, once you update their user record in your HRIS, Reach will automatically update their user record in Reach accordingly. 
  • If you have dynamic groups set up based on the updated criteria, their group and assignment enrollments will update automatically. 

Automatically deactivate users on their termination date 

  • If an employee leaves your organization, once their employment status is no longer active in the HRIS, Reach will deactivate the user. 
  • If they ever return, we’ll reactivate them automatically, as long as you reactivate the previous employee and not create a new employee record in your HRIS. 

đź’ˇPlease note that once the integration is setup, you will be unable to manually manage users. 


Which Merge common fields are being synced from HRIS?

We read and utilize the following data fields from Merge’s common model for HRIS integrations: 

Employee.display_full_name Populates Name field in Reach 
Employee.work_email

Populates Email field in Reach

Employee.employment_status

We only sync Active employees 

Employee.start_date We only add employees to Reach when their start date is today or in the past. This field also populates the Hire Date field in Reach. 
Employee.manager

Helps populate Manager Status field in Reach.

We check to see if the user in question's employee ID is populated in any other employee's manager field. If yes, then their manager status in Reach = Y, if no, then their manager status in Reach = N. 

Employment.employment_type Can configure integration to only sync employees with specific employment types. As part of the configuration process, we'll present to you the employment types we see from your HRIS and you can select all or some of the employment types to sync. 
Employment.job_title

Populates Job Level field in Reach

Optional: You can map a Job Level field from your HRIS rather than Job Title. This can simplify the mapping process. 

Group.name

Populates Department field in Reach. As part of the mapping process, you'll be able to see the different group types your HRIS is sending us so you can select the correct one to utilize for Department data. 

Location.location_type (must equal WORK)
  • Location.name
  • Location.city
  • Location.state
  • Location.country

 

Populates Location field in Reach

Please note that Reach only has read permissions enabled from the HRIS provider and not write permissions back to customer’s HRIS.


Which HRIS Providers does Reach integrate with? 

ADP Workforce Now AlexisHR BambooHR
Breathe Dayforce CharlieHR
ChartHop Freshteam Gusto
Hibob HR Partner Humaans
IntelliHR Justworks Kallidus
Lucca Namely Officient
Paychex Paylocity PeopleHR
Personio UKG Pro UKG Pro Workforce Management
UKG Ready Workday TriNet Zenefits

Click here to view provider-specific integration details for supported and unsupported HRIS platforms.


How do you set up the integration? 

Setting up the HRIS integrations with Paradigm Reach is a multi step process. 

  1. Invite HRIS Admins

  2. Link your HRIS platform to Merge*
  3. Select Team Members
  4. Map Data Fields
  5. Complete

Click here to view the complete step-by-step set up process.

*Depending on your specific HRIS, there may be steps you'll need to take in your HRIS or with your HRIS rep prior to linking your HRIS to Merge. 


How often do syncs take place? 

At least once every 24 hours. Our system checks for updates in your HRIS system every 6 hours, so if there are updates within the default 24 hour window, additional syncs can take place. 


What are Merge’s security policies and practices? 

Merge holds several security related certificates, including: 

  • SOC2 Type II
  • ISO 27001 
  • HIPAA 
  • CCPA
  • GDPR 

Which HRIS use cases are not supported at this time? 

  1. Once connected, you will not be able to manage any users manually in Reach. All user management will be automated via the integration. 
  2. If you had dynamic groups setup prior to the integration being connected, you will need to recreate those dynamic groups to ensure they still work. 
  3. Currently, organizations can only connect one HRIS account to their Reach account, so if you are utilizing multiple HRIS accounts, we won’t be able to support your use case right away. Similarly, you will not be able to manually add or update users (including CSV imports) once the integration is enabled. This also means you will not be able to use the HRIS integration some of your Reach users and CSV import for other users in your Reach account. 
  4. If you only want a subset of employees in your organization’s Reach account and that filtering is by location, department, or criteria other than employment type, we won’t be able to support your use case right away. 
  5. While we will be supporting dozens of HRIS providers, not all of them will be supported right away. Additionally, some of them may require additional steps on the HRIS side to link to Merge and then Reach. Click here to view provider-specific integration details for supported and unsupported HRIS platforms.
  6. For now, this integration is a one way integration from the HRIS account to Reach. We will not be sending any data back to your HRIS account. 

Helpful Merge Documentation