To setup a Ceridian user data integration, there are a few steps an admin for your Ceridian account must complete.
- Password Policy
Create a password policy specific to this Beekeeper and Ceridian integration. You'll need to make sure there is no password expiration or password reset -- each would change the password you initially set for the Beekeeper/Ceridian integration and prevent the integration from working.
To set up the policy, go to System Admin > Password Policy and select the Add button.
Name the policy something easy to identify having been created for this Beekeeper/Ceridian integration. The screen capture below shows a sample Beekeeper Policy, highlighting key fields.
Create a role specific to this Beekeeper and Ceridian integration. Go to System Admin > Roles SL and select the Add button. Give the role a name easy to remember as associated with this Beekeeper integration. Make sure to set the Password Policy to the policy you created for this integration in the previous step.
- Roles > Features
Next, from the top of the New Role screen, select the Features tab. Check and expand HCM Anywhere, then check and expand Web Services, then check Explorer, Path/Post Employee HR Data, and Read Data. See the screen capture below for an example.
Roles > Authorizations
Next, while still in the New Role screen, select the Authorizations tab at the top. There are many fields you may choose to use in your integration. Please discuss with your Customer Success Manager if you are unsure which are needed for your app's use cases. At a minimum, we recommend checking "Can Read" permissions for following Names:
- Employee Contact Information
- Employee Contact Information - Business
- Employee Own Contact Information
- Employee Own Contact Information - Business
- Employee Number
- Employee Properties
- Employee Personal Information
- Employee Personal Information xRefCode
- Employee Status Information
- Employee Work Assignment - Primary Records
- Forms - Employee Status Information
- Forms - Employee Work Assignment - Primary Records
- User Information
- Roles > Web services field-level access
Next, while still in the New Role screen, select the Web Services Field-Level Access tab at the top. Check and enable the SOAP Services. Check and enable Employee. Again, there are many fields you may choose from and your Customer Success Manager can help you choose appropriately. At a minimum, we recommend the following fields:
- Set up integration user and assign role
With the role now created, you will need to create a single unique user to be used for this integration. This user, and only this user, should be assigned to the Role you created in the previous steps.
In the System Admin > User area, at the top of the page, select New and fill in the User Name field with the name you choose for this user. We recommend something easy to connect to this integration, like BeekeeperUser.
Set the user's culture to "English US" and Numeric Culture to "English US", and create a password using the password field. You'll need to share this username and password with Beekeeper later. Check the Approved box, then assign the role created previously to this user by selecting the Add User Role button.
- Locations access
While still in the New User screen, go to the Location access tab. Make sure to at least select the highest level location for your organization. Optionally, you may select only those organizational location you wish to provide access to this integration. The drop down will list the available locations to choose from. If you do select more than one location option, be sure to check "primary" for one of them. Click the "Save" button to complete the User setup.
- Info needed by Beekeeper
Please ask your CSM to provide you with a secure box link where you can share the following info:
- The service URL (ie. https://integration.dayforcehcm.com/DataSvc/DayforceService.svc)
- Client Company Name (ie. MyCompanyDSPP)
- Integration user name (ie. BeekeeperUser)
- Integration user password (ie. BeekeeperPassword123)
If you have any questions or problems, please reach out to your Customer Success Manager or Customer Success Engineer for help!