Productivity · Okta coverage
Resource Guru and Okta: SSO and SCIM
Resource scheduling for booking people and equipment on projects. There is no SCIM on any plan.
SCIM pricing for every app →What Okta covers for Resource Guru, 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 Resource Guru account lifecycle.
In the OIN with SWA password fill only. No SAML, OIDC or provisioning.
StitchOps covers 8 of 8 capabilities for Resource Guru.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | Password fill only (SWA). No SAML or OIDC. | Enterprise password management signs users in to Resource Guru with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Resource Guru logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Resource Guru account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Resource Guru roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Resource Guru 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 Resource Guru. | Changes the Resource Guru 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 Resource Guru accounts. | Pulls the Resource Guru user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Resource Guru. | Step level evidence for every action StitchOps takes in Resource Guru. |
Single sign on
Okta, from the OIN
Password fill only (SWA). No SAML or OIDC.
StitchOps
Enterprise password management signs users in to Resource Guru with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Resource Guru 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 Resource Guru 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 Resource Guru 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 Resource Guru 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 Resource Guru.
StitchOps
Changes the Resource Guru 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 Resource Guru accounts.
StitchOps
Pulls the Resource Guru user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Resource Guru.
StitchOps
Step level evidence for every action StitchOps takes in Resource Guru.
Okta coverage from the Okta Integration Network, read October 10, 2026. ResourceGuru on okta.com StitchOps for Okta →
SCIM and API tax
What Resource Guru charges to automate accounts.
Resource Guru does not offer SCIM provisioning on any plan. There is no SCIM tax to pay, and no plan that lets your identity provider create, change and remove Resource Guru accounts through SCIM.
Pricing notes
SSO/SAML available on Master plan ($10/person a month) for 30+ users. No SCIM documented on any plan per pricing page and help docs. Status changed from 'unknown' to 'none'.
Last verified 2026-06-12. 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 Resource Guru and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Resource Guru 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 Resource Guru account with the right role when your HR system or identity provider says someone starts.
Movers
Change Resource Guru roles, teams and access when someone changes department or manager.
Leavers
Remove Resource Guru access the same day someone leaves, and free the seat.
Access checks
List who can log in to Resource Guru on a schedule, with evidence for the audit.
Common questions.
Does Resource Guru support SCIM?
No. Resource Guru does not offer SCIM provisioning on any plan, so accounts are created and removed by hand, by file import, or by a tool that works in Resource Guru the way an admin would.
Can Resource Guru accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Resource Guru 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 Resource Guru in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists ResourceGuru with SWA sign in and no provisioning.
Can Okta deprovision Resource Guru users?
Not through an OIN connector. StitchOps removes Resource Guru accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Resource Guru passwords when someone leaves?
StitchOps logs in to Resource Guru, 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.