--- title: "Docebo Connect for Ceridian Dayforce" slug: "docebo-connect-for-ceridian-dayforce" updated: 2026-04-27T14:06:59Z published: 2026-04-27T14:06:59Z canonical: "developer.docebo.com/docebo-connect-for-ceridian-dayforce" --- > ## Documentation Index > Fetch the complete documentation index at: https://developer.docebo.com/llms.txt > Use this file to discover all available pages before exploring further. # Docebo Connect for Ceridian Dayforce ## Introduction Docebo Connect is a Docebo module acting as a connector between your platform and third-party SaaS systems, helping you to integrate your platform with more than 400 third-party external systems, reducing the integration effort. Docebo Connect offers a large catalog of connectors for the most popular SaaS systems, to manage automated workflows (called recipes) shared among systems in order to exchange and share data on the basis of triggers. > [!NOTE] > Please note > > Docebo Connect takes advantage of the APIs and business logic already existing in the integrating systems and does not create new ones. In addition, Docebo Connect does not manage SSO flows with Identity Providers (such as SAML, OpenID Connect, etc), JavaScript integrations (such as Google Analytics or Google Tag Manager) or iframe integrations (such as Docebo OEM or Salesforce Canvas). The Docebo Connect for Ceridian Dayforce integration is designed to automate the provisioning of users from Ceridian Dayforce (HRIS) to Docebo. This integration ensures that when a user is created or updated in Dayforce, the corresponding user in Docebo is automatically created or updated with the relevant data. This process ensures data consistency, reduces manual effort, and streamlines workforce management within the Docebo environment. For more information on the definition of terms and concepts used throughout this article, please read [Docebo Connect Glossary of Terms](https://developer.docebo.com/docs/docebo-connect-glossary-of-terms). ## Activating Docebo Connect To activate Docebo Connect on your platform or sandbox, please reach out to your Docebo account manager. > [!NOTE] > Please note > > Depending on the integration requirements, there may be associated costs. ## Before you start ### Cloning and updating recipes All the recipes for this integration can be found in the project's folder. This folder should be considered a “special folder” as all the recipes contained within are subject to automatic updates. As such, any customizations you make to recipes located within the folder can be overwritten by Docebo. In order to prevent such an occurrence, it is strongly advised to create a new project folder for any recipes you wish to use in production and copy or clone the recipes from the project's folder inside. Prior to configuring and using the integration, you need to make clones of all the recipes used in this integration. For more information on how to clone and edit a cloned recipe, please see [Docebo Connect usage: Copying recipes](/v1/docs/docebo-connect-usage-copying-recipes). The list of recipes that need to be cloned can be found in the Recipes chapter of this article. All recipes that call a sub-recipe will require editing, the called sub-recipes can be found in a list inside the recipe description. ### Configuring Ceridian Dayforce Before you begin, ensure your Dayforce user role used for the Docebo Connect connection has the necessary permissions. First, navigate to the *Roles* section by accessing the **Hamburger menu** and navigating to **System Admin** > **Roles** > **Features**. ![Docebo system admin menu displaying various settings and options for user management.](https://cdn.document360.io/75d583ae-622e-4bde-98e6-0ddd0e7a16bb/Images/Documentation/1(5).png) There, navigate to **HCM Anywhere** > **Web Services**. ![Ceridian Administrator interface displaying features and options for managing employee data.](https://cdn.document360.io/75d583ae-622e-4bde-98e6-0ddd0e7a16bb/Images/Documentation/2(5).png) Next, select **PATCH/POST HR Bulk Job**. ![Feature assignment interface for Ceridian Administrator with various options listed.](https://cdn.document360.io/75d583ae-622e-4bde-98e6-0ddd0e7a16bb/Images/Documentation/3(5).png) Next, you must also enable additional permissions. Navigate to **Hamburger menu** > **System Admin** > **Roles** and access the **Web Services Field-Level Access** tab. There, go to **RESTful Services** > **Human Resources**. ![Overview of web services field-level access settings and user role assignments.](https://cdn.document360.io/75d583ae-622e-4bde-98e6-0ddd0e7a16bb/Images/Documentation/4(4).png) and enable: - `EmployeeExportBulkResponse` - `EmployeeExportBackgroundJobStatus` (and relevant child nodes) - `EmployeeExportParameters` (and relevant child nodes) ![Ceridian Administrator interface displaying web services and field-level access permissions.](https://cdn.document360.io/75d583ae-622e-4bde-98e6-0ddd0e7a16bb/Images/Documentation/5(3).png) ## Lookup Table Click on the **gear** icon and locate *Docebo Connect*, then click on **Manage**. Next, click on the **Lookup Table** tab and then click on the **integration-settings** table. Please make sure that the table in the platform matches the table presented here, if any of the following rows are missing, please add them by typing the values in the relevant text boxes and then pressing the **check mark** icon to save the row. Add the following rows if not exist: | Integration | Key | Value / Description | | --- | --- | --- | | `DAYFORCE` | `NOTIFICATION_MAIL_ID` | The email ID of the user to receive notification if any error occurs in a job | | `DAYFORCE` | `LAST_SYNC_DATE` | Used by the integration to store the last time a synchronization job was executed successfully, in order to retrieve only the set of Dayforce objects that are in need of synchronization. Used to populate the `DeltaDate` parameter. An empty value forces the Integration to perform a complete migration. | | `DAYFORCE` | `USER_ADDITIONAL_FIELD_NAME_MANAGER_XREF` | The name of the *User additional field* created in Docebo for the *Manager Xref* to be added | | `DAYFORCE` | `USER_ADDITIONAL_FIELD_NAME_EMPLOYEE_XREF` | The name of the *User additional field* created in Docebo for the *Employee Xref* to be added to be added | | `DAYFORCE` | `IMPORT_ACTIVE_USERS_ONLY` | Boolean `true`/`false` This setting instructs the integration to perform or skip the import of terminated or deactivated Dayforce Employees during the migration flow. | | `DAYFORCE` | `MOVE_TO_BRANCH_FLAG` | Boolean `true`/`false` This setting instructs the integration to try to place Docebo users created or updated in an existing Docebo branch as a result of a Dayforce synchronization. The default behavior is to place the user in the Docebo branch with the Docebo branch code equal to the *Dayforce Employee Department*. | | `DAYFORCE` | `DEFAULT_BRANCH_NAME` | This setting holds the Docebo branch code where Docebo users should be created when imported from Dayforce under one of the following conditions: - Move to branches = `true` **AND** a corresponding existing Docebo branch is not found to create or move that User into - Move to branches = `false` | ![Integration settings table displaying various fields and their corresponding values.](https://cdn.document360.io/75d583ae-622e-4bde-98e6-0ddd0e7a16bb/Images/Documentation/6(3).png) ## Recipe descriptions ### User Sync - Dayforce to Docebo LMS This recipe orchestrates the entire user synchronization process, from retrieving data from Dayforce to provisioning and mapping users in Docebo. #### Trigger This recipe is triggered every hour #### Calls to other recipes - Create and retrieve user additional field ID from Docebo LMS - Retrieve branch ID - Retrieve and process employee data ### Retrieve and process employee data This recipe is responsible for retrieving employee details from Dayforce, using pagination to handle large datasets. It can retrieve all employees for a full migration or only updated employees for an incremental flow. #### Trigger Triggered via function call #### Calls to other recipes - Create/Update users from Dayforce to Docebo LMS - Retrieve User details ### Create/Update users from Dayforce to Docebo LMS This recipe handles the actual provisioning of users from Dayforce to Docebo. Users are created with a specific username format. #### Trigger Triggered via function call #### Calls to other recipes - None ### Retrieve User details This recipe obtains all users from Docebo (for full migration) or only updated users (for incremental flow) to facilitate the user-manager mapping process. #### Trigger Triggered via function call #### Calls to other recipes - User-Manager mapping ### User-Manager mapping This recipe maps users to their direct managers by obtaining the Manager Xref user additional field and matching it with the user's username in Docebo. #### Trigger Triggered via function call #### Calls to other recipes - None ### Create and retrieve user additional field ID from Docebo LMS This utility recipe is responsible for obtaining a user's additional field ID based on a provided name. If the field does not exist, it is automatically created. #### Trigger Triggered via function call #### Calls to other recipes - None ### Retrieve branch ID This utility recipe obtains a branch ID based on the provided branch name. #### Trigger Triggered via function call #### Calls to other recipes - None A branch in Docebo is a way to organize users in a hierarchical structure that mirrors a company's organizational chart. Each branch or sub-branch can represent a department, team, or any other unit. Users can only be assigned to a single branch, and this structure can be used to manage permissions, enrollments, and content visibility.