Skip to content
StitchOps

HR, payroll and benefits · US

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

StitchOps uses ADP RUN as the source for Okta. New hires are in Okta before day one, role 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 ADP RUN today.

ADP RUN is built for small businesses, and IT is often one person or an outside provider. Hires and terminations reach IT by text or email, so new starters wait for logins and people who leave can keep them for weeks.

What StitchOps does in ADP RUN.

Joiners in Okta before day one

When HR adds a new hire in ADP RUN, 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 ADP RUN 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 ADP RUN, 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 ADP RUN, so HR and IT see the same details.

Built for a small IT team

StitchOps runs the setup and the daily work. Your team agrees the rules and sees a log of every change made in Okta.

No API fee, no custom development

StitchOps does not need a paid ADP RUN API, a SCIM upgrade or a custom integration. It reads changes the way your HR team sees them, or uses a connection you already have.

Before and after.

The manual wayWith StitchOps
New hire added in ADP RUNIT 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.
Outside IT providerTold about leavers when someone remembers.Leavers handled on the last day, logged.

What Okta covers for ADP RUN, 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 ADP RUN account lifecycle.

In the OIN with SWA password fill only. No SAML, OIDC or provisioning.

StitchOps covers 8 of 8 capabilities for ADP RUN.

  • Single sign on

    Okta, from the OIN

    Password fill only (SWA). No SAML or OIDC.

    StitchOps

    Enterprise password management signs users in to ADP RUN with vaulted credentials. Users never need the password.

  • Shared accounts and MFA

    Okta, from the OIN

    Not part of the OIN listing.

    StitchOps

    Shares ADP RUN 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 ADP RUN 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 ADP RUN 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 ADP RUN 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

    No password rotation in ADP RUN.

    StitchOps

    Changes the ADP RUN password on a schedule and the day someone leaves, and updates your vault in the same run.

  • Access reviews

    Okta, from the OIN

    No connector to read or remove ADP RUN accounts.

    StitchOps

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

  • Audit evidence

    Okta, from the OIN

    Nothing logged inside ADP RUN.

    StitchOps

    Step level evidence for every action StitchOps takes in ADP RUN.

Okta coverage from the Okta Integration Network, read October 24, 2026. RUN Powered by ADP on okta.com StitchOps for Okta →

Common questions.

Do we need a ADP RUN API or SCIM connection?

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

We use an outside IT provider. Can they manage this?

Yes. Your provider can see the log of every change StitchOps makes in Okta, and agree the rules with you. Nobody has to key in hires or terminations.

What login does StitchOps need in ADP RUN?

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 ADP RUN 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 ADP RUN?

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

Is ADP RUN in the Okta Integration Network?

Yes. As of October 24, 2026, the OIN lists RUN Powered by ADP with SWA sign in and no provisioning.

Can Okta deprovision ADP RUN users?

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

How do you rotate ADP RUN passwords when someone leaves?

StitchOps logs in to ADP RUN, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.

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 ADP RUN.

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