Design · Okta coverage
Balsamiq and Okta: SSO, SCIM and offboarding
Low fidelity wireframing tool for sketching interface layouts. There is no SCIM on any plan.
SCIM pricing for every app →What Okta covers for Balsamiq, 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 Balsamiq account lifecycle.
In the OIN with SAML or OIDC sign in only. No provisioning.
StitchOps covers 6 of 8 capabilities for Balsamiq.
| 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 Balsamiq logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Balsamiq account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Balsamiq roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Balsamiq access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | Not needed for users who sign in with SAML or OIDC. | Rotates shared admin logins in Balsamiq on a schedule or after an offboarding. |
| Access reviews | No connector to read or remove Balsamiq accounts. | Pulls the Balsamiq user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Balsamiq. | Step level evidence for every action StitchOps takes in Balsamiq. |
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 Balsamiq 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 Balsamiq 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 Balsamiq 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 Balsamiq 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
Not needed for users who sign in with SAML or OIDC.
StitchOps
Rotates shared admin logins in Balsamiq on a schedule or after an offboarding.
Access reviews
Okta, from the OIN
No connector to read or remove Balsamiq accounts.
StitchOps
Pulls the Balsamiq user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Balsamiq.
StitchOps
Step level evidence for every action StitchOps takes in Balsamiq.
Okta coverage from the Okta Integration Network, read October 10, 2026. Balsamiq on okta.com StitchOps for Okta →
SCIM and API tax
What Balsamiq charges to automate accounts.
Balsamiq 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 Balsamiq accounts through SCIM.
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
Enterprise tier ($18 a month+) adds SAML SSO only. No SCIM provisioning support documented across any plan. Project count pricing, not per user.
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 Balsamiq and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Balsamiq 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 Balsamiq account with the right role when your HR system or identity provider says someone starts.
Movers
Change Balsamiq roles, teams and access when someone changes department or manager.
Leavers
Remove Balsamiq access the same day someone leaves, and free the seat.
Access checks
List who can log in to Balsamiq on a schedule, with evidence for the audit.
Common questions.
Does Balsamiq support SCIM?
No. Balsamiq 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 Balsamiq the way an admin would.
Can Balsamiq accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Balsamiq 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 Balsamiq in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists Balsamiq with SAML sign in and no provisioning.
Can Okta deprovision Balsamiq users?
Not through an OIN connector. StitchOps removes Balsamiq accounts the day someone leaves, anywhere a person can log in and act, 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.