Public sector · HR, payroll and hiring
eHR staff accounts and Okta
eHR is the Los Angeles County human resources and payroll system. The Auditor Controller uses it to pay more than 103,000 county employees. Its identity documentation is not published.
More local government apps →What Okta covers for eHR, 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 eHR account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for eHR.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to eHR with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares eHR logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the eHR account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes eHR roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes eHR 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 eHR. | Changes the eHR 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 eHR accounts. | Pulls the eHR user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside eHR. | Step level evidence for every action StitchOps takes in eHR. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to eHR with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares eHR 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 eHR 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 eHR 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 eHR 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 eHR.
StitchOps
Changes the eHR 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 eHR accounts.
StitchOps
Pulls the eHR user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside eHR.
StitchOps
Step level evidence for every action StitchOps takes in eHR.
Okta coverage from the Okta Integration Network, read October 20, 2026. eHR has no OIN listing. StitchOps for Okta →
SCIM and Okta status
What eHR supports today.
Identity documentation for eHR is not published, so its SCIM status is listed as Not published.
- SCIM status
- Not published
- Okta Integration Network
- Not in the Okta Integration Network. Read October 20, 2026.
- Vendor
- Los Angeles County Department of Auditor Controller
- Type
- Statewide system built for one state
- Used in
- Local governmentCalifornia
Last verified 2026-10-20.Sources:Official pageOkta Integration Network
More local government apps →Every public sector app →What the SCIM tax is →
What StitchOps automates in eHR.
StitchOps creates, changes and removes eHR user accounts and roles, and pulls the user list for access reviews. The StitchOps worker runs inside your environment, and your data never leaves your network or key vault.
Joiners
Create the eHR account with the right role when your HR system or Okta says someone starts.
Movers and leavers
Change eHR roles when someone changes jobs, and remove access the day they leave.
Password rotation
Rotate shared and service logins in eHR on a schedule and after every offboarding, and update your vault in the same run.
Access review evidence
List who can sign in to eHR on a schedule, compare it to your directory, and keep step level evidence for auditors.
Common questions.
Does eHR support SCIM?
Identity documentation for eHR is not published, so its SCIM status is listed as Not published.
Can eHR accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes eHR accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is eHR in the Okta Integration Network?
No. As of October 20, 2026, the OIN has no listing for eHR. Okta can sign users in only through a custom app if eHR supports SAML or OIDC, and has no connector to manage eHR accounts.
Can Okta deprovision eHR users?
Not through an OIN connector. StitchOps removes eHR accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate eHR passwords when someone leaves?
StitchOps logs in to eHR, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.