System for Cross-domain Identity Management, also known as SCIM, provides automated provisioning and user management for Miro Enterprise subscriptions through your Identity Provider (IdP).
Available for: Enterprise plan
Set up by: Company Admins
Important to know
- SAML based SSO must be properly set up and be functional in your Enterprise plan before you start configuring automated provisioning.
See the guide to configuring SAML SSO.
All assigned groups must exist in your Miro subscription as teams under identical names before linking.
Teams can be created and managed using Teams API.
If you need to have your groups and teams named differently, you may rename either or both of them after the sync is established.
Password changes are not supported.
There are no immediate plans to start supporting this change.
- If a user is a member of two or more Enterprise accounts, you cannot update their Username (email address): this is to avoid conflicts with the Sharing policies established.
To update the user, ensure that they are removed from the second account first. If you need assistance, reach out to Miro support.
Rules under which Miro SCIM operates
The SCIM-synced changes are primarily applied to newly assigned users. The status of those who are already under your subscription will be supplemented but might not be overwritten in that the changes are applied on the group/team level. For instance:
a) if a user is a member of Team1 on the Miro side and your IDP sends an update to add them to Team2, their status in Team1 remains unaffected.
b) if your IDP sends an update containing changes to User1, other team members are unaffected. As mentioned in Supported Features > Sync and push groups to overwrite the team status and re-sync all users at once try and initiate a new push.
- All users provisioned under SCIM are assigned the default license of your subscription:
a) For Enterprise subscriptions without Flexible Licensing Program: a Full license. If your subscription runs out of licenses the users start getting provisioned under Free Restricted license.
b) For Enterprise subscriptions with Flexible Licensing Program activated: Free or Free Restricted license depending on the default subscription license.
- If you need some of the users to be provisioned under a license different to the default one:
as stated above, all users are provisioned with the default license. However, you can immediately update all or some of them using the UserType attribute with a Full value. Users updated with the attribute will be upgraded to the Full license with no downtime on the user-end.
- All users provisioned under SCIM are also affected by the Domain control feature. This means that if a user is a member of only one security group in your Identity provider but your Domain control settings define 3 teams as the designated ones the user will also be added to those 3 teams.
- To protect the service Miro limits the number of API calls available every 30 seconds:
Request typeLimit level
First Rate Limit Level 1
Third Rate Limit Level 3
Fourth Rate Limit Level 4
Third Rate Limit Level 4
For details on limit levels please see here. If the number of requests exceeds the limit, Miro will return the standard 429 Too many requests.
Detailed Miro SCIM schema can be found here.
Miro supports the following provisioning features:
Create new users
New users assigned to Miro application in IdP will be created in your Miro Enterprise subscription as Enterprise Members. Users that are added to a user group that is synced to a Miro team with the same name will be added to the team as Team members
Push user profile updates
For the supported attributes and changes see below
Sync and push groups
Sync your IDP groups and their members to the teams within your Miro Enterprise subscription to automatically manage user membership. Ongoing sync will send specific updates regarding your group's users to the synced Miro team, while a push will overwrite the team's state treating the group as the source of truth (if there were any manual changes by your Company Admins on the Miro end)
Decouple the Group/Team names
Miro syncs Groups and Teams by name thus they must have the same exact name. However, after the initial sync is created you will be able to give either one or both of them the names that are convenient for you. You can see the example of the decoupling here
Remove users from group/team (not the Enterprise subscription, see below)
Removing a user from a group will remove them from the synced Miro team (during the next Group Push)
Deactivating/deleting a user or disabling a user's access to the application in the IDP will deactivate the user in your Miro Enterprise plan. Depending on the circumstances, deactivating a user may reassign their content to the oldest team admins:
- if you deactivate the user on the IDP end but keep them assigned to the Miro app, their team membership on the Miro end is not changed, and their content is not reassigned - they are simply moved from an Active to a Deactivated state (and users section, respectively) and stop consuming a license.
- if you trigger the deactivation by deleting the user in the IDP or deassigning them from the Miro app, while the user is a member of some synced teams then the user will additionally be removed from those Miro teams and their content in the said teams will be reassigned to the oldest team admins.
- if you trigger the deactivation by deleting the user in the IDP or deassigning them from the Miro app, when the user is not a member of any synced teams the user's team membership will not be changed and their content will not be reassigned.
Removing a user from the Enterprise subscription is not supported by default. Still, you can manually add the functionality using API to have the user completely removed from the subscription instead of setting them to the Deactivated status. In this scenario, the content is reassigned to respective Team members. It's impossible to set which Admins will get the ownership over automatically reassigned content. But this can be set when you manually deactivate a user in Miro settings.
Assigning a user back to the application or reactivating the user profile in the IDP will reactivate them in your Miro Enterprise subscription if they were previously provisioned and deactivated.
You can also remove users from your Enterprise plan by sending a direct Delete API call - please see the documentation here. Note that only direct calls will remove the users. Delete events initiated by your identity solution will be treated as a request to Deactivate.
⚠️ Note that:
- Email / The Primary Parameter / Unique Identifier / Username) is the only value required by Miro and must be in the form of an email.
- the email update is only possible for already synced users. In other words, the first sync must happen when their email in the IdP and Miro is the same, otherwise Miro won't recognise the user and a duplicate Miro profile under the new email will be created.
- the email update must happen in the user’s IdP profile, not in the assignments list.
- Unlike with other attributes, updating the user's Email will send them a notification: both the old and the new email address will receive a letter letting the user know that they are now to use their new email address to log into Miro.
SCIM Attribute (Claim)
|The attributes listed below are not required and will be accepted by Miro if present (other attributes sent to Miro will be ignored).|
givenName + " " + familyName;
Must be a text URL to the image.
Supported file types: jpg, jpeg, bmp, png, gif
roles[primary eq "True"].value (Azure)
"value" field has String type in SCIM standard but managerId
⚠️ Password changes are not supported and there are no immediate plans to start supporting this change.
⚠️ Username, UserType and roles.value cannot be updated for Deactivated users.
All attributes will be displayed in the exported CSV user list that can be downloaded from the Active Users section.
The option to download a list of users
Step 1: Enable SCIM option in Miro
To enable SCIM for your Miro Enterprise plan, go to the Company settings > Enterprise integrations, enable the SCIM Provisioning feature. There you can get the Base URL and the API Token for configuring your IdP.
SCIM in Miro settings
Step 2: Configure your Identity Provider
The setup will depend on the Identity Provider you use. Miro supports preconfigured Okta and Azure AD however you can use any Identity Provider of your choice for as long as it allows setting up SCIM.
OKTA - see the setup instruction here.
Azure AD- see the setup instruction here.
Possible issues and how to resolve them
1. Users do not get provisioned due to an allowlist error.
An example of the error from Okta identity provider
Please make sure that the user's domain address is added to your allowlist in the Security settings.
2. If you authenticate your end-users with one identity solution (IDP1) but would like to enable SCIM via a different one (IDP2), this is possible on two conditions:
- the IDP2 can do API calls with the bearer token.
- both identity providers are in sync (so SCIM-provisioned users exist in the IDP1 as well and therefore are able to authenticate with Miro).
For more information please reach out to Miro Support Team.