HR · Okta coverage
Recruitee and Okta: SSO, SCIM and offboarding
Applicant tracking and collaborative hiring software. SCIM support is not published.
SCIM pricing for every app →What Okta covers for Recruitee, 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 Recruitee account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for Recruitee.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to Recruitee with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Recruitee logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Recruitee account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Recruitee roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Recruitee 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 Recruitee. | Changes the Recruitee 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 Recruitee accounts. | Pulls the Recruitee user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Recruitee. | Step level evidence for every action StitchOps takes in Recruitee. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to Recruitee with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Recruitee 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 Recruitee 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 Recruitee 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 Recruitee 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 Recruitee.
StitchOps
Changes the Recruitee 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 Recruitee accounts.
StitchOps
Pulls the Recruitee user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Recruitee.
StitchOps
Step level evidence for every action StitchOps takes in Recruitee.
Okta coverage from the Okta Integration Network, read October 10, 2026. Recruitee has no OIN listing. StitchOps for Okta →
SCIM and API tax
What Recruitee charges to automate accounts.
Recruitee does not publish whether SCIM provisioning is included or which plan it needs. Ask the vendor before you count on it, or price it with your own contract in the calculator.
SSO sits on the same plan as SCIM or above it. If you need SSO anyway, that upgrade is not avoidable, and the calculator counts it that way.
Pricing notes
Tellent Recruitee shows tier names (Start, Advance, Optimize) only; specific pricing not published. SAML SSO available on Optimize tier; SCIM not publicly documented. Could not fully verify SCIM availability on 2026 to 06 to 12.
Last verified 2026-06-12 (estimate). Source · SCIM pricing for every app · Method
Pricing data includes the SCIM Tax Index (Iden), CC BY 4.0, https://scimtax.org/. Modified and extended by StitchOps.
Estimate Recruitee and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Recruitee accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the Recruitee account with the right role when your HR system or identity provider says someone starts.
Movers
Change Recruitee roles, teams and access when someone changes department or manager.
Leavers
Remove Recruitee access the same day someone leaves, and free the seat.
Access checks
List who can log in to Recruitee on a schedule, with evidence for the audit.
Common questions.
Does Recruitee support SCIM?
Recruitee does not publish it. Ask the vendor which plan includes SCIM provisioning before you rely on it.
Can Recruitee accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Recruitee 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 Recruitee in the Okta Integration Network?
No. As of October 10, 2026, the OIN has no listing for Recruitee. Okta can sign users in only through a custom app if Recruitee supports SAML or OIDC, and has no connector to manage Recruitee accounts.
Can Okta deprovision Recruitee users?
Not through an OIN connector. StitchOps removes Recruitee accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Recruitee passwords when someone leaves?
StitchOps logs in to Recruitee, 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.