Miro Capabilities
Last updated: October 8, 2024
After this article...
You'll understand the capabilities our Miro integration provides, and how Lumos interacts with the Miro API.
View users
The mapping between Miro user statuses and Lumos user account statuses is below.
Miro User Status | Lumos Account Status |
active | Active |
inactive | Suspended |
deleted (removed from organization) | Deprovisioned |
Miro API endpoint: https://developers.miro.com/reference/enterprise-get-organization-member
View a user's entitlements
Lumos can retrieve the following user entitlements from Miro.
Role - The user's role in the Miro organization (Organization Internal Admin, Organization Internal User, Organization External User, Organization Team Guest User)
License - The user's current license in the Miro organization (Full, Occasional, Free, Free Restricted, Full Trial)
Miro API endpoint: https://developers.miro.com/reference/enterprise-get-organization-member ("role" and "license" fields, respectively)
View a user's last activity
In Lumos, theΒ Last Activity value for Miro represents the last time a user accessed a Miro board.
This is important, since any user who may not have accessed a board recently is likely not using a license and you may be able to reclaim it in Lumos!
If you aren't seeing Last Activity for Miro, you will need to reconnect the integration. Seeπ Connecting Miro
Miro API endpoint: https://developers.miro.com/reference/enterprise-get-organization-member (the "lastActivityAt" field)
Suspend a user
AppStore | Offboarding | Access Reviews | License Management |
N/A | β | β | β |
This feature is only available if you connected Miro via the "Default w/ SCIM" flow and is not supported if you integrated Miro in a read-only capacity. See π Connecting Miro
In Lumos, suspending a Miro user marks their Account Status as "Deprovisioned".
In Miro, this action deactivates the user. This removes all licenses associated with the user and prevents them from logging in.
Users with theΒ Role "Organization External User" or "Organization Team Guest User" cannot be suspended. Any attempt to suspend these users in Lumos will fail.
This action does not reclaim a license in Miro.
Miro API endpoint: https://developers.miro.com/docs/users#update-user-attribute-by-id (we pass a payload of "{"op": "Replace", "path": "active", "value": False}" to deactivate the user.
Deprovision a user
AppStore | Offboarding | Access Reviews | License Management |
N/A | β | β | β |
This feature is only available if you connected Miro via "Default w/ SCIM" flow and is not supported if you integrated Miro in a read-only capacity. See π Connecting Miro
In Lumos, deprovisioning a Miro user marks their Account Status as "Deprovisioned".
In Miro, this action deletes the user from your Miro organization. After a user is deleted from Miro, the ownership of all boards that belong to the deleted user is transferred to the oldest team member who currently has an admin role.
Users with the Role "Organization External User" or "Organization Team Guest User" cannot be deprovisioned via the Miro API. Any attempt to deprovision these users in Lumos will fail.
This action reclaims a license in Miro.
Miro API endpoint: https://developers.miro.com/docs/users#delete-user-by-id