Skip to main content
Miro is a visual collaboration platform for whiteboarding and diagramming. Connect your Miro Enterprise organization to Oleria to see who has access across it: every member, the teams and user groups they belong to, the roles they hold, and what they’ve done recently. Oleria reads this data from the Miro Enterprise API.

​
What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your Miro organization:
  • Accounts - every organization member, including guests and deactivated users, with email, organization role, admin roles, license, and last activity.
  • Groups - Miro teams and user groups, their members, and which teams each user group is added to.
  • Roles - organization roles, admin roles, and a Team Admin role for each team, with the accounts that hold each one.
  • Activity - events from the Miro audit log, such as user, team, and group changes.
Oleria uses this data for dormant account detection and access reviews, refreshed on Oleria’s regular sync schedule.
This integration doesn’t read boards, projects, or board sharing, so it doesn’t populate resource-level Access Graph or Access Inventory data. Miro doesn’t expose installed apps, OAuth tokens, or service accounts through its API, so these appear only as the actor on audit log events. The Miro API returns the last 90 days of audit log activity.

​
Prerequisites

  • A Miro organization on the Enterprise plan. The organization APIs this integration uses aren’t available on other plans.
  • A Miro Company Admin to create and install the app below.
  • For the optional SCIM token: single sign-on (SSO) enabled in Miro.
  • Admin access on the Oleria platform to add a new integration.
The exact location of these settings can change over time. If the steps below don’t match what you see, refer to Miro’s own developer documentation.

​
Create a Miro app for Oleria

Oleria connects through an app that you create in your own Miro organization. Miro grants organization-level scopes only to an app that a Company Admin installs, so there is no shared Oleria app to approve.
1

Create the app

Sign in to Miro as a Company Admin. Go to Profile settings -> Your apps, and create a new app in a Developer team. Give it a name such as Oleria.
2

Choose the token type

In the app’s settings, turn on Expire user authorization token if you’ll connect with OAuth. Oleria refreshes expiring tokens automatically. Leave it off if you’ll use an access token, because an access token can’t be refreshed.
3

Grant the read scopes

In the app’s permissions, select these scopes:To let Oleria run remediation actions, also select:
Many teams start with only the read scopes, then add the write scopes once they’re ready to automate remediation in Miro.

​
Choose an authentication method

With OAuth, you approve the app in Miro during setup and Oleria refreshes the token automatically. Miro recommends expiring tokens. To use them, turn on Expire user authorization token as described in Choose the token type.
1

Add the redirect URIs

In the app’s settings, add both of these redirect URIs, using the URL you sign in to Oleria with. For example, if you sign in to Oleria at https://acme.oleria.io, add:
Both redirect URIs must match exactly, or Miro rejects the connection with a redirect URI mismatch. The second URI is used when you edit the integration later.
2

Copy the client ID and client secret

Copy the app’s Client ID and Client secret. You’ll paste them into Oleria in the next section.
Store the client secret securely. If you lose it, generate a new one in Miro and update the integration in Oleria.

​
Get an optional SCIM token

A SCIM token is optional. With it, Oleria also reads user names and departments, and can deactivate and reactivate users.
1

Copy the SCIM token

In Miro, go to Company settings -> Enterprise integrations -> SCIM, and copy the SCIM token. SCIM requires SSO to be enabled.

​
Connect Miro to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations, then select the Miro tile.
2

Complete the connection form

Select your authentication method and fill in the connection form:
3

Save the integration

Select Authenticate. With OAuth, Miro asks you to approve the app for your organization, then returns you to Oleria. Oleria validates the credentials and saves the integration.

​
Verify the integration

Confirm the new instance appears on the Connected tab of your Oleria Integrations page with a status of Healthy. Oleria syncs users, groups, roles, and activity from Miro on its regular sync schedule once the initial sync completes.
If you rotate the client secret, the access token, or the SCIM token, update it in Oleria by editing the integration. When you edit, leave a secret field blank to keep the value already stored.

​
Remediation actions

Beyond discovery, Oleria can act on Miro access to remediate risk. Each action needs the matching write scope from Create a Miro app for Oleria, or the SCIM token where noted.
Organization roles and admin roles have no Miro API for changes, so Oleria shows them but can’t assign or remove them. A non-team user must be added as a team member before they can become a team admin.

​
Contact us

For questions about this integration, contact us at support@oleria.com.