Timeline:
2-4 weeks
Website -
https://www.ceridian.com/
Partnership Required:
Optional. Ceridian is currently not accepting new screening partners, however, their API is now open allowing for new connections.
deverus Required for IM Config:
See attached:
deverus Required for IM Config:
No
Require SHM:
Yes
Standard Operating Procedure
Once the IM account is created, we provide the API Private Key from IM to Ceridian or whomever is working through the Ceridian Onboarding Guide.
From Ceridian, we need API Credentials and the customer instance name (which is the Company ID):
Data Required for IM Configuration
Username (for the API User Role)
Password (for the API User Role)
Provider Reference (where does this come from? In ESS setups, it’s just ‘ESS’ - assuming it’s got to come from Ceridian or whomever is working through the guide)
Client Name
Customer Instance Name (same as Company ID)
Synchronize Packages and Locations? (should be set to Yes)
Default Location (not required)
Mapping
Not Required.
deverus runs periodically to sync packages and locations on the Ceridian side, which is displayed in the form of a pick-list.
Other Platform Requirements -
SwiftHire Mobile -
SwiftHire Settings are configured - Recommended at client-type level
All user profiles have SwiftHire settings configured in their respective HR Modules
Active default user at client level(s)
Active package(s) - Recommended at client-type level
If multiple locations, Branch Administration is enabled at Primary Branch
All associated clients/locations are nested under this Branch Administration
IM Account Fields -
(API) Username:
(API) Password:
Provider Reference:
Client Name:
Customer Instance Name:
Synchronize Packages and Locations?:
Default Location:
Ceridian Onboarding Guide: