Dayforce

Overview

1Password SaaS Manager connects to Dayforce using API credentials associated with a role that has read-only access. The role must be configured with specific Feature, Field-Level, and Authorization settings to allow SaaS Manager to retrieve employee and departmental data.

Note

If the API user has multiple roles, make sure the integration role is set as the Default role under System Admin > User. This makes sure that API requests use the correct permissions. If the user only has one role, no action is needed.

Role configuration

In Dayforce, go to System Admin > Roles.

Configure Feature Security

Under the Features tab:

  • Expand HCM Anywhere > Web Services.
  • Enable Read Data (required for all API access).

See the Dayforce documentation for more information.

Configure Field-Level Access

Under the Web Services Field-Level Access tab:

  • Expand RESTful Services > Human Resources

    Expand Employee and enable. You must include XRefCode – this is required to retrieve employee identifiers.

    Expand and enable:

    • EmployeeManager

      EmployeeRole

      EmployeeEmploymentType

      PersonContact

      EmployeeWorkAssignment

  • Expand RESTful Services > Configuration and enable Departments.

See the full list of fields below and also the Dayforce documentation for more information.

Configure Employee Authorizations

Under the Authorizations tab, enable Can Read for the following:

  • Employee Contact Information – for addresses and contact details.
  • Employee Contact Information – Personal and/or Business – for email addresses and phone numbers.
  • Employee Status Information – for employment types.
  • Employee Profile – Security Settings – Roles – for employee roles.
  • Employee Profile – Security Settings – Locations – for work locations.
  • Employee Work Assignment – Primary/Secondary Records – for job titles and work assignments.

Create or assign the role

Go to System Admin > User.

Assign this configured role to a dedicated API user that SaaS Manager will use for authentication. This user should have no other permissions.

Make sure that the user account is active and has appropriate location access for your company-level data. To do this go to System Admin > User and search for the user you are using for SaaS Manager to connect with. Expand it and select the Location Access tab. Click + Add Location, and add the Company Level Location required.

See the Dayforce documentation for more information.

Gather Connection Details

When connecting from SaaS Manager, you’ll need:

From your SaaS Manager dashboard, navigate to Integrations > Dayforce. Select Connect.

Enter the above information into the appropriate fields in the setup screen, then select Connect.

Endpoints, attributes and fields accessed

SaaS Manager uses the following Dayforce API endpoints (read-only):

  • GET /api/{company}/v1/Employees
  • GET /api/{company}/v1/Employees/{XRefCode}?expand=Contacts,Addresses,EmployeeManagers,EmploymentTypes,Roles,Locations,OrgUnitInfos,WorkAssignments
  • GET /api/{company}/v1/Departments
  • GET /api/{company}/v1/Departments/{XRefCode}

Attribute mapping

SaaS Manager person attributeHow it's determined
IDEmployee XRefCode (unique identifier)
EmailBusiness email address from currently valid contact information
Personal emailPersonal email address from currently valid contact information
First nameEmployee's first name
UsernameLogin ID from Dayforce
Employee IDEmployee number from Dayforce
Phone numberFirst valid business phone or mobile number from contact information
Employee typeEmployment type short name (for example, Employee, Contractor) from currently valid employment types
Job titleBusiness title from primary work assignment, or job short name if business title not available
RolesAll currently valid role long names assigned to the employee
Start dateEmployee start date
Leaving dateTermination date if the employee has been terminated
LocationLong name of the primary or default location that is currently valid
ManagerManager XRefCode from currently valid employee manager assignment
StatusSet to "NotProvisioned" if start date is in the future, "Inactive" if terminated, otherwise "Active"
Personal addressPrimary residence address including street address, city, state/province, postal code, and country code
TeamBy default, based on the department from organizational unit information. Can be configured by SaaS Manager support to use other organizational levels (Corp, Region, District, Site, and so on)

Employee data fields accessed

XRefCode
FirstName
LastName
LoginId
DisplayName
StartDate
TerminationDate
EmployeeNumber
Contacts/Items/ContactInformationType
Contacts/Items/ElectronicAddress (for email)
Contacts/Items/ContactNumber (for phone)
Contacts/Items/EffectiveStart
Contacts/Items/EffectiveEnd
EmployeeManagers/Items/ManagerXRefCode
EmployeeManagers/Items/ManagerFirstName
EmployeeManagers/Items/ManagerLastName
EmployeeManagers/Items/EffectiveStart
EmployeeManagers/Items/EffectiveEnd
EmploymentTypes/Items/EmploymentType/ShortName
EmploymentTypes/Items/EffectiveStart
EmploymentTypes/Items/EffectiveEnd
Roles/Items/Role/LongName
Roles/Items/EffectiveStart
Roles/Items/EffectiveEnd
Locations/Items/Location/LongName
Locations/Items/IsPrimary
Locations/Items/IsDefault
Locations/Items/EffectiveStart
Locations/Items/EffectiveEnd
OrgUnitInfos/Items/OrgUnitDetail/OrgLevel
OrgUnitInfos/Items/OrgUnitDetail/XRefCode
OrgUnitInfos/Items/OrgUnitDetail/LongName
OrgUnitInfos/Items/Department
OrgUnitInfos/Items/OrgUnitDetail/EffectiveStart
OrgUnitInfos/Items/OrgUnitDetail/EffectiveEnd
WorkAssignments/Items/BusinessTitle
WorkAssignments/Items/Position/Job/ShortName
WorkAssignments/Items/Position/Department
WorkAssignments/Items/Location
WorkAssignments/Items/IsPrimary
WorkAssignments/Items/EffectiveStart
WorkAssignments/Items/EffectiveEnd
Addresses/Items/Address1
Addresses/Items/Address2
Addresses/Items/City
Addresses/Items/State/XRefCode
Addresses/Items/PostalCode
Addresses/Items/Country/XRefCode
Addresses/Items/ContactInformationType

Published: