Miro is an online collaborative whiteboard platform used by distributed teams for brainstorming, project planning, and agile workflows. Integrating Miro with Glean enables users to search, discover, and access Miro board content from a designated list of teams within Glean, enhancing workflow efficiency by making critical information accessible directly within your enterprise knowledge platform.

​
Supported Features and Limitations

The Miro connector is designed to index and make searchable the content from Miro boards in specified teams. This section outlines supported data objects, key features, and known limitations to guide users in understanding the connector’s capabilities.

​
Supported Objects/Entities

Object/EntityDescription
Miro BoardsAll boards accessible by users who have explicitly authorized Glean for pre-indicated teams.

​
Supported API Endpoints/Features

  • List all team members (for identity and permissions mapping).
  • List boards available to the user in a given team.
  • Fetch board metadata and textual content via widgets (using Miro REST API v2, which removes widget count limitations).
  • Activity ingestion via audit logs API (only available in v1 and for select plans), for document update/delete events.

​
Limitations

  • Only boards visible to users who have authorized Glean for teams in the predefined list are indexed.
  • Comments within boards and some non-native widget content (such as third-party plugin widgets) are not indexed due to API constraints.
  • Full crawling of project-level permissions is limited, as there is no public API for Miro projects to determine hierarchical or inherited permissions.
  • Incremental crawling is primarily available via audit logs for customers with access to v1 API; otherwise, frequent full crawls are needed.
  • No webhook support—content updates are detected via crawls rather than event notifications.
  • Instant access to new or deleted content is dependent on crawl frequency and API rate limits.

​
Requirements

This section addresses the technical, credential, and permission requirements needed to configure the Miro connector for your Glean environment.

​
Technical Requirements

  • Miro enterprise (or business) plan is recommended for organization-wide access and project support.
  • Glean instance with support for app integrations and connectors.
  • API access enabled for the relevant Miro teams.

​
Credential Requirements

  • OAuth2 application credentials (Client ID and Client Secret) from an app registered in the Miro developer console.
  • The app should be registered under the Miro developer team, with appropriate redirect URIs set up as per Glean’s instance configuration.

​
Permission Requirements

  • Minimum required Miro admin roles to configure the connector: Company Admin and Content Admin are required to register, configure, and authorize the Glean app for each team.
  • The service account or user performing the configuration must have access to all targeted boards and teams to ensure complete indexing.
  • When accessing board content, the Glean connector only receives data accessible to the authorizing user, respecting Miro’s access controls.

​
Preliminary Source/System Setup

  1. Register a new app in Miro’s developer portal.
  2. Set the required OAuth scopes: boards:read, identity:read (and optionally auditlogs:read for full activity support where available).
  3. Add redirect URIs matching your Glean deployment.
  4. Install the Glean app to each designated Miro team either as an admin or allow team members to perform installation depending on team settings.
  5. (Optional) For multi-team setups, repeat installation and authorization steps per team as needed.

​
External References

​
Configuration and Setup Instructions

Follow these instructions to configure and launch the Miro connector in your Glean instance.

​
Prerequisites

  • A Glean admin account with permission to manage connectors.
  • Miro enterprise plan access and admin permissions.
  • OAuth application (Client ID and Secret) created in Miro for your organization’s Glean integration.

​
Authentication and credentials

  • Enter the Miro app’s Client ID and Client Secret in the Glean connector configuration UI.
  • Specify the team ID(s) for which the connector should index content—these should correspond to Miro teams for which the Glean app has been installed.
  • When prompted, authenticate using a Miro admin or a user with sufficient permissions. Each user seeking to index their accessible boards must complete the OAuth authorization for the Glean app for the relevant teams.

​
Step-by-Step Setup

  1. In the Miro developer portal, register a new app and note the Client ID and Client Secret.
  2. Configure the required redirect URIs in the app registration to point to your Glean instance’s callback URLs.
  3. Assign necessary OAuth scopes (typically boards:read, identity:read).
  4. In your Glean admin console, navigate to the connector setup and select Miro.
  5. Input the Client ID, Client Secret, and the list of team IDs you wish to index.
  6. For each relevant team, ensure the Glean app has been installed and authorized by an admin or allowed member.
  7. Prompt users to complete the OAuth authorization flow for their selected teams if per-user authentication is enabled.
  8. Start the initial crawl. Content indexing may take time depending on the size of your Miro instance; background processes will sync boards and permissions.
  9. If issues arise, confirm roles (Company and Content Admin) and review Glean/Miro logs for OAuth and API errors (such as 401 Unauthorized).