Overview
To connect Dayforce (formerly Ceridian Dayforce HCM) to Happl, you'll need three details: your Company ID, and the user name and password of the Dayforce user Happl will connect with. Setting it up takes around 20 minutes. Steps One to Four are done in Dayforce, and the last step is done in Happl.
Before you start
The role you configure for this integration must be set as the user's Default role.
In Dayforce, go to System Admin > User
Find and click on the user you'll connect with (this is likely your own user)
Tick Is Default next to the role you'll be configuring for this integration
Note: the user you connect with signs in with a user name and password, so it must be exempt from SSO and MFA, and its password should be set so it doesn't expire.
Step One: Configure Feature Access
Click the menu icon in the top left of your screen, then go to System Admin > Roles
Go to Features. Make sure HCM Anywhere and Web Services are ticked
Expand Web Services and make sure Read Data is ticked
Note: Happl only reads data from Dayforce, so you don't need to tick the PATCH or POST options.
Step Two: Configure Authorizations
Go to Authorizations
Select Can Read for each of the following:
Dayforce authorization | What Happl uses it for |
Employee Contact Information | Contact details |
Employee Contact Information - Business | Work email (used to invite employees to Happl) |
Employee Contact Information - Personal | Home address |
Employee Financial Information | Pay-related data used alongside the pay authorizations |
Employee Key Information | Employee number and core identifiers |
Employee Historic Pay Information | Salary history |
Employee Pay Information | Salary, pay currency, pay frequency (used for salary-linked benefits such as life assurance and pension) |
Employee Personal Information | Name, date of birth, gender |
Employee Personal Information XrefCode | The unique ID Dayforce uses to match employee records |
Employee Profile – Security Settings – Role | Lets the integration user's role be read |
Employee Properties | Custom fields, only if Happl needs any of yours |
Employee Status Information | Employment status, start and termination dates |
Employee Work Assignment – Primary Records | Job title, department, location |
Employee Work Assignment – Secondary Records | Secondary jobs or positions |
User Information | User account details |
Step Three: Configure Web Services Field-level Access
Go to Web Services Field-level Access
Navigate to RESTful Services > Human Resources > Employee
Enable EffectiveStart, EffectiveEnd and XRefCode
Then enable the fields below for each type of data you want to send to Happl
Required for Happl
Data | What to enable | What Happl uses it for |
Names | Enable FirstName, LastName and CommonName | Employee name |
Managers | Right-click Employee managers and Select All | Line manager |
Employment status | Right-click Employment Statuses and Select All, then right-click Employment Status Group and Select All | Active status, leavers and termination dates |
Location | Right-click Locations and Select All | Work site / location |
Employment information | Enable RESTful Services > Human Resources > EmployeeWorkAssignment (and all child nodes) | Job title, department, employment type |
Pay information | Enable RESTful Services > Human Resources > EmployeeCompensation (and all child nodes) | Salary, pay currency, pay frequency (used for salary-linked benefits such as life assurance and pension) |
Emails and contact information | Enable Contacts and Addresses (and all child nodes) under RESTful Services > Human Resources > Employee | Work email (used to invite employees to Happl) and home address |
Gender | Enable Gender | Gender (needed by some insurers) |
Date of birth | Enable BirthDate | Date of birth (used for age-based benefits and insurer data) |
Start date or hire date | Enable StartDate, HireDate and OriginalHireDate | Start date, used for eligibility and waiting periods |
Recommended
Data | What to enable | What Happl uses it for |
Social Security Number | Enable RESTful Services > Human Resources > socialSecurityNumber | National ID number, e.g. National Insurance number or SSN (needed by some insurers and providers) |
Marital status | Enable MaritalStatus | Marital status, where a benefit or insurer needs it |
Groups | Enable RESTful Services > Configuration > Location (and all child nodes) and RESTful Services > Human Resources > OrgUnitInfos | Org units and groups |
Time off | Enable RESTful Services > Human Resources > Workforce Management > EmployeeTimeAwayFromWork (and relevant child nodes) | Time off records |
Custom fields (employee properties) | Enable RESTful Services > Human Resources > EmployeePropertyValue | Custom fields, only if Happl has agreed to use any with you |
Step Four: Configure Org-Level Access
Go to System Admin > User. The user you're connecting with needs Can See Self enabled
Expand the user by clicking the small down arrow next to it
Click Location Access, then + Add Location, and add the Company Level Location
Step Five: Enter your credentials in Happl
In Happl, go to Settings > Integrations and click Connect in the HRIS section
Select Dayforce from the list
Enter your Company ID, User Name and Password, then click Submit
If anything is missing after your first sync, contact the Happl team through the chat or at [email protected] and we'll help you check the setup.