Productivity · Okta coverage
Fathom and Okta: SSO, SCIM and offboarding
AI meeting recorder and notes. SCIM provisioning is available through the OIN; the plan it needs is not published.
SCIM pricing for every app →What Okta covers for Fathom, 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 Fathom account lifecycle.
In the OIN with SAML or OIDC sign in and provisioning.
StitchOps covers 2 of 8 capabilities for Fathom.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | SAML or OIDC from the OIN listing. | Needed if your Fathom plan doesn't include SSO. Enterprise password management signs users in to Fathom with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Fathom logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | Creates accounts through the OIN connector. | Needed if your Fathom plan doesn't include SCIM. Creates the Fathom 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 Fathom plan doesn't include SCIM. Changes Fathom roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | Deactivates accounts through the OIN connector. | Needed if your Fathom plan doesn't include SCIM. Removes Fathom 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 Fathom on a schedule or after an offboarding. |
| Access reviews | The connector lets Okta read and remove Fathom accounts for reviews. | Needed if your Fathom plan doesn't include SCIM. Pulls the Fathom user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Okta logs the changes its connector makes. | Needed if your Fathom plan doesn't include SCIM. Step level evidence for every action StitchOps takes in Fathom. |
Single sign on
Okta, from the OIN
SAML or OIDC from the OIN listing.
StitchOps
Needed if your Fathom plan doesn't include SSO. Enterprise password management signs users in to Fathom with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Fathom 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 Fathom plan doesn't include SCIM. Creates the Fathom 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 Fathom plan doesn't include SCIM. Changes Fathom roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
Deactivates accounts through the OIN connector.
StitchOps
Needed if your Fathom plan doesn't include SCIM. Removes Fathom 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 Fathom on a schedule or after an offboarding.
Access reviews
Okta, from the OIN
The connector lets Okta read and remove Fathom accounts for reviews.
StitchOps
Needed if your Fathom plan doesn't include SCIM. Pulls the Fathom user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Okta logs the changes its connector makes.
StitchOps
Needed if your Fathom plan doesn't include SCIM. Step level evidence for every action StitchOps takes in Fathom.
Also in the OIN listing
- Group Push
Okta coverage from the Okta Integration Network, read October 24, 2026. Fathom on okta.com StitchOps for Okta →
SCIM and API tax
What Fathom charges to automate accounts.
Fathom 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.
Last verified 2026-10-10 (estimate). SCIM pricing for every app · Method
Estimate Fathom and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Fathom 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 Fathom account with the right role when your HR system or identity provider says someone starts.
Movers
Change Fathom roles, teams and access when someone changes department or manager.
Leavers
Remove Fathom access the same day someone leaves, and free the seat.
Access checks
List who can log in to Fathom on a schedule, with evidence for the audit.
Common questions.
Does Fathom support SCIM?
Fathom does not publish it. Ask the vendor which plan includes SCIM provisioning before you rely on it.
Can Fathom accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Fathom 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 Fathom in the Okta Integration Network?
Yes. As of October 24, 2026, the OIN lists Fathom with SAML sign in and provisioning to create, update and deactivate users. The listing also offers Group Push.
Can Okta deprovision Fathom users?
Yes, if your Fathom plan includes the provisioning the OIN connector needs. If it doesn't, StitchOps removes Fathom accounts the day someone leaves and saves evidence of each removal.
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.