What Capable Miro is
Miro Embed ("Miro for Confluence") is a Confluence Cloud app that puts a live Miro board straight onto a Confluence page, and gives each space a gallery of the boards already embedded there. It adds one macro, "Miro Board (Capable)", a per-space "Miro" page, and an admin entry in Confluence settings. You can embed a board just by pasting its link, with no Miro sign-in at all; connecting your Miro account is optional and only adds board browsing, real board names, and read-only sharing and people information. Everything the app does with Miro is read-only: it can list your boards, look one up and list its members, and nothing else. It cannot change a board, its sharing, or invite anyone. Boards render for logged-out and unlicensed readers too, but readers only see a board if the board's own Miro sharing already lets them in - embedding a board never grants access to it. Customers coming from the older re:solution Connect app keep both their existing macros and their Miro connection: the app uses the same macro key and imports the old OAuth tokens automatically on install.
#At a glance
Macros | Miro Board |
|---|---|
Sold as | A standalone app, and a capability inside the Capable Suite |
#A few things worth knowing
Embedding a board does not grant access to it. Readers see the board only if the board's own Miro sharing lets them; otherwise they get Miro's sign-in or permission screen inside the frame. Nothing in Confluence can change that.
The whole Miro surface is read-only. There is no "update sharing" control and no invite flow - the only Miro write was removed so the proxy could be read-only and the app could drop Miro's boards:write permission. Change sharing in Miro its
"People with access" can never show email addresses or avatars, on any Miro plan, and roles are informational only. Miro does not return member emails to apps, and the invite and role-change features were removed along with the Confluence e
#Related
The short version.
