Documentation Index

Fetch the complete documentation index at: https://docs.revealdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Notes for Administrators on Miro Enterprise Integration

Prev Next

This article provides administrative requirements and configuration details for the Miro Enterprise integration with Reveal Hold.

Miro plan and feature requirements

The integration requires a Miro Enterprise plan with Enterprise Guard enabled. Cases and Legal Hold APIs are available only when Enterprise Guard is active.

Required Roles

The user installing the integration must have both of the following roles in Miro:

  • Company Admin

  • eDiscovery Admin

Application configuration

The Miro application used for Reveal Hold must be installed on the correct Miro team and include the following OAuth scope:

  • organization:cases:management

Authentication and token management

Authentication occurs during integration setup in Reveal Hold. An OAuth token is generated and used to manage cases and legal holds.

Important

Changes to admin roles, scopes, or team access may require re-authentication.

Preservation timing and expectations

Legal holds may take up to 24 hours to become fully active. Preservation applies only to boards accessed or modified after activation.

Common reasons preservation may not apply

Preservation may not apply when:

  • Custodian does not exist as a Miro user

  • Enterprise Guard is not enabled

  • Required OAuth scopes are missing

  • The application is installed on the wrong Miro team.

Footer Design