Skip to content
StitchOps

HR, payroll and benefits · US and Canada

Dayforce as the source for Okta: joiners, movers and leavers.

StitchOps uses Dayforce as the source for Okta. New hires are in Okta before day one, job and manager changes update their access, and leavers are removed on their last day, with no HRIS API fee or custom development.

HR Source pricing →

What's hard about Dayforce today.

Dayforce, formerly Ceridian, runs HR, payroll and workforce management in one system. Okta can sign people in to Dayforce, but reading hires, changes and terminations from it to drive Okta is a separate project, so movers, rehires and people on leave end up as tickets.

What StitchOps does in Dayforce.

Joiners in Okta before day one

When HR adds a new hire in Dayforce, StitchOps creates them in Okta before their start date, so Okta can give them the apps their role needs on day one.

Role changes that update access

When Dayforce shows a new job, department, manager or location, StitchOps updates the person in Okta, and Okta adds and removes app access to match.

Leavers removed on their last day

When a last day arrives in Dayforce, StitchOps deactivates the person in Okta, and Okta removes their access in every app it manages.

Email and username written back

Once Okta has the new person's email and username, StitchOps writes them back to their record in Dayforce, so HR and IT see the same details.

Rehires, leave and contractors

Rehires get their original account back, people on leave are suspended and restored, and contractors follow their own rules.

Okta sign in stays as it is

If Okta already signs people in to Dayforce, that stays. StitchOps adds the HR side, so Dayforce decides who exists in Okta and what they can reach.

Before and after.

The manual wayWith StitchOps
New hire added in DayforceIT waits for an email, then builds the account.In Okta before day one, with the apps the role needs.
Role or manager changeNew access by ticket, old access forgotten.Okta updated, access matches the new role.
Last dayAccess removed when someone remembers.Deactivated in Okta, every Okta app follows.
Employee returns from leaveAccount left active, or rebuilt.Suspended in Okta, then restored.

What Okta covers for Dayforce, and what StitchOps adds.

Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the Dayforce account lifecycle.

In the OIN with SAML or OIDC sign in only. No provisioning.

StitchOps covers 7 of 8 capabilities for Dayforce.

  • Single sign on

    Okta, from the OIN

    SAML or OIDC from the OIN listing.

    StitchOps

    Needed if your Dayforce plan doesn't include SSO. Enterprise password management signs users in to Dayforce with vaulted credentials. Users never need the password.

  • Shared accounts and MFA

    Okta, from the OIN

    Not part of the OIN listing.

    StitchOps

    Shares Dayforce logins and their MFA across a team, with credentials kept in your vault.

  • Joiners

    Okta, from the OIN

    No account creation in the OIN.

    StitchOps

    Creates the Dayforce account with the right role on day one, anywhere a person can log in and act.

  • Movers

    Okta, from the OIN

    No account updates in the OIN.

    StitchOps

    Changes Dayforce roles and access when someone changes jobs, anywhere a person can log in and act.

  • Leavers

    Okta, from the OIN

    No deprovisioning in the OIN.

    StitchOps

    Removes Dayforce access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.

  • Password rotation

    Okta, from the OIN

    Users who sign in with SAML or OIDC have no app password. Shared admin logins are not rotated.

    StitchOps

    Rotates shared admin logins in Dayforce on a schedule or after an offboarding.

  • Access reviews

    Okta, from the OIN

    No connector to read or remove Dayforce accounts.

    StitchOps

    Pulls the Dayforce user list on a schedule, compares it to your directory, and removes what you approve.

  • Audit evidence

    Okta, from the OIN

    Nothing logged inside Dayforce.

    StitchOps

    Step level evidence for every action StitchOps takes in Dayforce.

Okta coverage from the Okta Integration Network, read October 24, 2026. Ceridian Dayforce HCM on okta.com StitchOps for Okta →

Common questions.

Do we need a Dayforce API or SCIM connection?

No. StitchOps reads hires, changes and terminations from Dayforce the way your HR team sees them. If your team already has a connection in place, StitchOps can use it instead.

Is Dayforce the same as Ceridian Dayforce?

Yes. Ceridian renamed the company Dayforce in 2024. StitchOps works the same way with either name.

What login does StitchOps need in Dayforce?

A login that can see hires, job changes and terminations, kept in your vault (1Password or Keeper) or the StitchOps vault. StitchOps runs on a dedicated worker VM in your environment, and models never see the credentials.

How is HR Source priced?

HR Source is priced per HR system per year, by company size, with no Dayforce API or SCIM fee on top. Prices are on our pricing page, and Connect for each app is priced separately.

How long does it take to connect Dayforce?

If StitchOps can log in to Dayforce, it can often be connected in a day. A 30 day pilot can prove it in your own Okta before you sign.

Is Dayforce in the Okta Integration Network?

Yes. As of October 24, 2026, the OIN lists Ceridian Dayforce HCM and Dayforce HCM SAML with SWA, SAML sign in and no provisioning.

Can Okta deprovision Dayforce users?

Not through an OIN connector. StitchOps removes Dayforce accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.

For your IT team
Where it runs
An agent runs an unattended desktop session on a dedicated worker VM in your environment, on Windows or macOS. It connects outbound only over TLS 1.2 or later. No inbound ports are opened.
Credentials
Credentials stay in your vault (1Password or Keeper) or in the StitchOps vault, encrypted with AWS KMS and resolved on the worker at run time. Models never see the values.
Okta stays the source of truth
StitchOps creates, updates and deactivates people in Okta from your HR system, and Okta Lifecycle Management carries the change to every app. StitchOps is listed in the Okta Integration Network.
Logs and telemetry
Every run keeps step level logs with status, timing and redacted results. Telemetry is content free: no field values, no personal data, no screenshots.
Security reviews
SOC 2 Type 2 examination completed, with HIPAA and GDPR Article 5 attestations, by Sensiba LLP. Penetration tested by a third party. ISO 27001 certification being finalized. The security packet is shared under NDA.

Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.

See it run in your Dayforce.

Fifteen minutes on how Dayforce reaches Okta today. We show you joiners, movers and leavers running from it.