DEV ENVIRONMENT — mentorly.dev
← All Integrations|
D
Dayforce Integration

Mentorly + Dayforce Integration

Run mentorship programs on the people you manage in Dayforce: run an employee listing report, import with Mentorly's template, and let them sign in with your identity provider.

How It Works

From Dayforce to a running program in three steps

1

Export

Export the people you want from Dayforce: name, work email, department, job title and manager.

2

Import

Paste the columns into Mentorly's member template (email, name, mentor, role, cohort, tags and your onboarding questions) and import. Mentorly matches on email, so nothing is duplicated. The import writes every system column as it is in the file, blank included, so for a re-import start from Mentorly's member export.

3

Sign in

Your people sign in with SAML 2.0 from your identity provider, and get their Mentorly invitation when you send it.

Getting your people out of Dayforce

In Dayforce, go to Reporting and Analytics, then Reporting, then Reports. Run Employee Listing by Department or Employee Listing by Manager and choose Excel in the output format; business email sits in the Current Employee Contact report under Contact Info. If no listing report has the columns you need, Report Marketplace (Reports, then Add, then Add Report from Marketplace) holds preconfigured reports built by Dayforce that you can add to your library and edit.

Signing in

Mentorly never asks for a Dayforce password. Sign-in comes over SAML 2.0 from the identity provider your company already runs (Okta, Microsoft Entra ID, Google Workspace and others), set up once by your IT team together with Mentorly. If your people reach Dayforce through single sign-on today, add Mentorly to the same identity provider and the login they use stays the same.

About a live connector

Mentorly does not connect to the Dayforce API today. Dayforce's REST API (GET /api/{client}/v1/Employees, with contacts and work assignments) runs as a web services user defined in Dayforce, and Dayforce recommends token-based authentication over sending that user's password with every call. Its developer site also documents field-level and org-level access for that user, which is where your team would limit what a Mentorly connector could read. Building that scheduled read is a project with your team, not an option in Mentorly.

Use Cases for Dayforce Customers

🇨🇦

Canadian Enterprises

Dayforce is common in Canadian organizations; its employee listing reports export the roster a bilingual mentorship program starts from.

📊

Unified HCM Data

Department, location and manager come out of one Dayforce report and go into the cohort and tags columns of the template (cohorts are created in Mentorly first).

🔄

Keeping It Current

After a hiring round, the new names go at the bottom of Mentorly's member export and the file goes back in; email is the key, so the rest of the roster stays as it was.

Frequently Asked Questions

How do I bring my Dayforce people into Mentorly?

Run Employee Listing by Department (or by Manager) under Reporting and Analytics, export to Excel, add business email from the Current Employee Contact report, paste into Mentorly's member template, and import.

Can my team sign in with their Dayforce login?

They sign in with the company login they already use, through your identity provider rather than through Dayforce. Dayforce credentials never reach Mentorly.

Does Mentorly connect to Dayforce directly?

No. Nothing moves from Dayforce to Mentorly unless an administrator exports it. A scheduled read would go through Dayforce's REST API as a web services user with token authentication, and setting that up is work done with your team.

Ready to bring your Dayforce people in?

See how a mentorship program runs on the people you already manage in Dayforce.