HR, payroll and benefits · US
isolved as the source for Okta: joiners, movers and leavers.
StitchOps uses isolved 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 isolved today.
isolved is often provided through a payroll partner, so each company's setup is a little different. Connecting it to Okta can mean asking the partner for an API or a file feed, and until then hires and terminations reach IT by email.
What StitchOps does in isolved.
Joiners in Okta before day one
When HR adds a new hire in isolved, 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 isolved 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 isolved, 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 isolved, so HR and IT see the same details.
Works however your isolved is set up
StitchOps reads changes from your isolved the way your HR team sees them, whichever partner provides it.
No API fee, no custom development
StitchOps does not need a paid isolved 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.
What Okta covers for isolved, 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 isolved account lifecycle.
In the OIN with SWA password fill only. No SAML, OIDC or provisioning.
StitchOps covers 8 of 8 capabilities for isolved.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | Password fill only (SWA). No SAML or OIDC. | Enterprise password management signs users in to isolved with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares isolved logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the isolved account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes isolved roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes isolved access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in isolved. | Changes the isolved password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove isolved accounts. | Pulls the isolved user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside isolved. | Step level evidence for every action StitchOps takes in isolved. |
Single sign on
Okta, from the OIN
Password fill only (SWA). No SAML or OIDC.
StitchOps
Enterprise password management signs users in to isolved with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares isolved 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 isolved 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 isolved 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 isolved 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 isolved.
StitchOps
Changes the isolved 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 isolved accounts.
StitchOps
Pulls the isolved user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside isolved.
StitchOps
Step level evidence for every action StitchOps takes in isolved.
Okta coverage from the Okta Integration Network, read October 24, 2026. iSolved HCM on okta.com StitchOps for Okta →
Common questions.
Do we need a isolved API or SCIM connection?
No. StitchOps reads hires, changes and terminations from isolved the way your HR team sees them. If your team already has a connection in place, StitchOps can use it instead.
Our isolved comes from a payroll partner. Does that matter?
No. StitchOps logs in the way your HR team does, so it works the same way whichever partner provides your isolved.
What login does StitchOps need in isolved?
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 isolved 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 isolved?
If StitchOps can log in to isolved, it can often be connected in a day. A 30 day pilot can prove it in your own Okta before you sign.
Is isolved in the Okta Integration Network?
Yes. As of October 24, 2026, the OIN lists iSolved HCM with SWA sign in and no provisioning.
Can Okta deprovision isolved users?
Not through an OIN connector. StitchOps removes isolved accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate isolved passwords when someone leaves?
StitchOps logs in to isolved, 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 isolved.
Fifteen minutes on how isolved reaches Okta today. We show you joiners, movers and leavers running from it.