Analytics · Okta coverage
Heap and Okta: SSO, SCIM and offboarding
Product analytics that captures every interaction. SCIM provisioning is available through the OIN; the plan it needs is not published.
SCIM pricing for every app →What Okta covers for Heap, 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 Heap account lifecycle.
In the OIN with SAML or OIDC sign in and provisioning.
StitchOps covers 1 of 8 capabilities for Heap.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | SAML or OIDC from the OIN listing. | Not needed. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Heap logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | Creates accounts through the OIN connector. | Not needed. |
| Movers | Updates accounts through the OIN connector. | Not needed. |
| Leavers | Deactivates accounts through the OIN connector. | Not needed. |
| Password rotation | Not needed for users who sign in with SAML or OIDC. | Rotates shared admin logins in Heap on a schedule or after an offboarding. |
| Access reviews | The connector lets Okta read and remove Heap accounts for reviews. | Not needed for reviews of assigned access. |
| Audit evidence | Okta logs the changes its connector makes. | Not needed. |
Single sign on
Okta, from the OIN
SAML or OIDC from the OIN listing.
StitchOps
Not needed.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Heap 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
Not needed.
Movers
Okta, from the OIN
Updates accounts through the OIN connector.
StitchOps
Not needed.
Leavers
Okta, from the OIN
Deactivates accounts through the OIN connector.
StitchOps
Not needed.
Password rotation
Okta, from the OIN
Not needed for users who sign in with SAML or OIDC.
StitchOps
Rotates shared admin logins in Heap on a schedule or after an offboarding.
Access reviews
Okta, from the OIN
The connector lets Okta read and remove Heap accounts for reviews.
StitchOps
Not needed for reviews of assigned access.
Audit evidence
Okta, from the OIN
Okta logs the changes its connector makes.
StitchOps
Not needed.
Okta coverage from the Okta Integration Network, read October 10, 2026. Heap on okta.com StitchOps for Okta →
SCIM and API tax
What Heap charges to automate accounts.
Heap 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.
Pricing notes
Added from Okta deal app lists. SCIM availability and pricing not yet verified.
Last verified 2026-10-10 (estimate). SCIM pricing for every app · Method
Estimate Heap and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Heap 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 Heap account with the right role when your HR system or identity provider says someone starts.
Movers
Change Heap roles, teams and access when someone changes department or manager.
Leavers
Remove Heap access the same day someone leaves, and free the seat.
Access checks
List who can log in to Heap on a schedule, with evidence for the audit.
Common questions.
Does Heap support SCIM?
Heap does not publish it. Ask the vendor which plan includes SCIM provisioning before you rely on it.
Can Heap accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Heap 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 Heap in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists Heap with SAML, SWA sign in and provisioning to create, update and deactivate users.
Can Okta deprovision Heap users?
Yes. The OIN connector deactivates Heap accounts when a user is removed in Okta.
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.