HR, payroll and benefits · US

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

StitchOps uses Namely 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.

Book a free workflow audit Get a demo

HR Source pricing →

What's hard about Namely today.

Namely brings HR, payroll and benefits together for mid size companies. Okta still has to hear about every hire, change and termination, and without a connection that means tickets and spreadsheets.

What StitchOps does in Namely.

Joiners in Okta before day one

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

Custom fields carried over

Department, title, location and the custom fields your Okta rules depend on are read from Namely and kept current in Okta.

No API fee, no custom development

StitchOps does not need a paid Namely 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 NamelyIT 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.

Custom field your Okta rules useUpdated by hand, often missed.Read from Namely, kept current.

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

In the OIN with sign in and partial provisioning.

StitchOps covers 5 of 8 capabilities for Namely.

What Okta covers for Namely, and what StitchOps adds
Capability	Okta, from the OIN	StitchOps
Single sign on	SAML or OIDC from the OIN listing.	Needed if your Namely plan doesn't include SSO. Enterprise password management signs users in to Namely with vaulted credentials. Users never need the password.
Shared accounts and MFA	Not part of the OIN listing.	Shares Namely logins and their MFA across a team, with credentials kept in your vault.
Joiners	Creates accounts through the OIN connector.	Needed if your Namely plan doesn't include SCIM. Creates the Namely account with the right role on day one, anywhere a person can log in and act.
Movers	Updates accounts through the OIN connector.	Needed if your Namely plan doesn't include SCIM. Changes Namely roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers	No deprovisioning in the OIN.	Removes Namely access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation	Users who sign in with SAML or OIDC have no app password. Shared admin logins are not rotated.	Rotates shared admin logins in Namely on a schedule or after an offboarding.
Access reviews	No connector to read or remove Namely accounts.	Pulls the Namely user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence	Nothing logged inside Namely.	Step level evidence for every action StitchOps takes in Namely.

Single sign on
Okta, from the OIN
SAML or OIDC from the OIN listing.
StitchOps
Needed if your Namely plan doesn't include SSO. Enterprise password management signs users in to Namely with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Namely logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
Creates accounts through the OIN connector.
StitchOps
Needed if your Namely plan doesn't include SCIM. Creates the Namely account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
Updates accounts through the OIN connector.
StitchOps
Needed if your Namely plan doesn't include SCIM. Changes Namely 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 Namely 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 Namely on a schedule or after an offboarding.
Access reviews
Okta, from the OIN
No connector to read or remove Namely accounts.
StitchOps
Pulls the Namely user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Namely.
StitchOps
Step level evidence for every action StitchOps takes in Namely.

Also in the OIN listing

Attribute Sourcing
Attribute Writeback
Identity Security Posture Management

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

Common questions.

Do we need a Namely API or SCIM connection?

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

Can StitchOps use the custom fields we keep in Namely?

Yes. StitchOps can carry the Namely fields your Okta rules depend on, such as department, location or employee type, so group based access stays right.

What login does StitchOps need in Namely?

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 Namely 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 Namely?

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

Is Namely in the Okta Integration Network?

Yes. As of October 24, 2026, the OIN lists Namely with SAML sign in and provisioning to create and update users. The listing also offers Attribute Sourcing, Attribute Writeback and Identity Security Posture Management.

Can Okta deprovision Namely users?

Not through an OIN connector. StitchOps removes Namely 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 October 24, 2026. Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.

See it run in your Namely.

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