Collaboration · SCIM pricing
Miro SCIM pricing
Online whiteboard for brainstorming, diagrams and workshops. SCIM costs extra.
SCIM pricing for every app →What Okta covers for Miro, 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 Miro account lifecycle.
In the OIN with SAML or OIDC sign in and provisioning.
StitchOps covers 1 of 8 capabilities for Miro.
| 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 Miro 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 Miro on a schedule or after an offboarding. |
| Access reviews | The connector lets Okta read and remove Miro 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 Miro 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 Miro on a schedule or after an offboarding.
Access reviews
Okta, from the OIN
The connector lets Okta read and remove Miro 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. Miro (formerly RealtimeBoard) on okta.com StitchOps for Okta →
SCIM and API tax
What Miro charges to automate accounts.
Miro includes SCIM provisioning only on Enterprise. That plan is sold by quote, so the price jump is not published. The plan most teams buy is Starter, $8 per user a month.
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
SCIM automation is Enterprise only.
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 Miro and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Miro 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 Miro account with the right role when your HR system or identity provider says someone starts.
Movers
Change Miro roles, teams and access when someone changes department or manager.
Leavers
Remove Miro access the same day someone leaves, and free the seat.
Access checks
List who can log in to Miro on a schedule, with evidence for the audit.
Common questions.
Does Miro support SCIM?
Yes, but only on Enterprise, sold by quote. On the plan most teams buy, SCIM is not available.
Which Miro plan includes SCIM?
Enterprise. It is sold by quote.
Can Miro accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Miro 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 Miro in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists Miro (formerly RealtimeBoard) with SAML, SWA sign in and provisioning to create, update and deactivate users.
Can Okta deprovision Miro users?
Yes. The OIN connector deactivates Miro 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.