Miro setup

You'll do the setup in two places: Miro to create and configure the app, and the Glean Admin console to save the required values.

Requirements

Technical requirements

• A Miro Enterprise plan.
• Access to the Glean Admin console.
• The list of Miro teams you want the connector to index.

Credential requirements

• A Miro OAuth2 application with a Client ID and Client Secret.
• The access token and refresh token used for the connector authorization flow.
• Your Miro Company ID.

Permission requirements

• You must be a Miro Company Admin to set up the connector.
• The user who creates the app should also have the Content Admin role.
• The app must be installed in each Miro team you want Glean to index.

Step 1: Create a developer team and app in Miro

1. Create a developer team if you do not already have one.
2. In that developer team, create a new app for Glean.
3. Set the app name to Glean.
4. Turn on Expire user authorization token for stronger token security.

Step 2: Configure app permissions

1. In the Miro app settings, grant the permissions required by the Glean connector.
2. Verify that the app can read board content and identity information for the teams you plan to index.

Step 3: Install the app in the teams you want to index

1. Install the app in one of your Miro teams.
2. Repeat the installation for each team whose boards Glean should index.

Step 4: Find your Company ID

1. In Miro, go to Settings → Company Profile.
2. Copy the Company ID from the URL.

The URL looks like this:

https://miro.com/app/settings/company/{company_id}/settings

Copy only the ID value, not the full URL.

Step 5: Enter the values in Glean

1. In the Glean Admin console, go to Connectors and select Add connector.
2. Select Miro.
3. Enter a connector name.
4. Paste the access token, refresh token, Client ID, and Client Secret into the corresponding fields.
5. Paste the Company ID into the appropriate field.
6. Select Save.

What happens next

After you save the connector, Glean begins crawling the boards and permission metadata it can access in the configured Miro teams. Freshness depends on your API access level and crawl cadence, because this connector does not rely on webhooks.

See also

• Miro overview