> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/hris/ceridian-dayforce.md).
# Ceridian Dayforce
Sync Dayforce HCM data to automate employee lifecycle and payroll-driven IT workflows
Ceridian Dayforce is a comprehensive cloud HCM platform that combines HR, payroll, benefits, workforce management, and talent management in a single application. Connecting Dayforce to Harmony enables automated IT provisioning triggered by HR events, intelligent workforce analytics, and seamless employee lifecycle management.
Harmony connects directly to Dayforce's bulk employee export API, bringing in significantly more employee detail than middleware-based approaches. Employee records sync automatically into Harmony, keeping agent profiles, team assignments, and contact data accurate without manual data entry.
### What the Ceridian Dayforce integration enables
| Capability | Description |
| --------------------- | ----------------------------------------------------------------- |
| Employee Data Sync | Sync employee profiles, departments, and organizational structure |
| Onboarding Automation | Automate IT setup when new hires are added |
| Offboarding Workflows | Secure access removal during employee terminations |
| Lifecycle Automation | Automate IT tasks for role changes, transfers, and promotions |
### Prerequisites
* **Dayforce Administrator Access**: Admin role that can create roles and users in Dayforce
* **Dayforce Subscription**: Active Dayforce HCM subscription
* **API User**: A dedicated Dayforce user with web services (API) access. Harmony signs in to the Dayforce API with this user's username and password
* **Harmony Account**: Active Harmony workspace
### Connect Ceridian Dayforce to Harmony
#### Step 1: Create an API User in Dayforce
1. Log in to Dayforce as an administrator
2. Go to **System Admin** > **Roles** and click **Add** to create a role for the Harmony integration
3. On the role's **Features** tab, check **HCM Anywhere** > **Web Services** > **Read Data**
4. On the **Authorizations** tab, check **Can Read** for the employee data Harmony syncs, including **Employee Contact Information**, **Employee Personal Information**, **Employee Properties**, and **Employee Status Information**
5. On the **Web Services Field-Level Access** tab, expand **RESTful Services** > **Human Resources** > **Employee** and check the fields Harmony reads: names, contacts, employment statuses, managers, home organization, employee properties, and **XRefCode**
6. Under **System Admin** > **User**, create a user for the integration, check **Approved**, and assign it only this role. Give the role a password policy with no password expiration, or the connection stops working when the password expires
7. On the user's **Location Access** tab, click **Add Location**, select the company-level location so the user can read every employee, and check **Primary**
8. Note your **Company ID** - you can find it on your Dayforce login page
#### Step 2: Navigate to Integrations
1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **Ceridian Dayforce** under **HRIS** (or search for it by name) and click its card
#### Step 3: Enter API Credentials
1. Enter your **Company ID**
2. Enter the API user's **Username** and **Password**
3. Click **Connect**
### What Harmony Syncs
Harmony connects directly to Dayforce's bulk employee export API to pull in complete, up-to-date employee information. Terminated employees are handled correctly during sync, so their records are processed without errors.
**From Dayforce:**
* Employee profiles (name, business email)
* Employment details (department, full-time or part-time)
* Employment status (active, inactive, terminated), including pre-start hires with their start date
* Manager
* Phone numbers
* Employment dates (start date, termination date)
* Position Level (pulled from Employee Properties in Dayforce and displayed as the employee's level; shows as `--` or `N/A` when no value is set)
Position Level data is included in the standard bulk sync, so it stays up to date alongside the rest of your employee information. No manual entry is required - the field is populated automatically for any employee who has a Position Level set in Dayforce.
### Use Cases
Automated Pre-Boarding
Start IT provisioning before day one using Dayforce pending employee status
Payroll-Driven Access
Use payroll events to automatically adjust IT access and licenses
Seamless Offboarding
Automate complete access removal when employees are terminated in Dayforce
Department Reorganization
Automatically update IT access and group memberships when departments change
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.harmony.io/integrations/hris/ceridian-dayforce.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.