Who can open this board
A read-only sharing summary shown when you are connected and a board is selected. The badge reports the widest of link, team and organisation access - not just the board's headline setting - and says "Sharing unknown" rather than guessing if Miro returns no policy. Direct membership is deliberately left out of the badge and shown in the people list instead.
#Where you do it
Task | Where |
|---|---|
Insert a Miro board on a page | Confluence editor, /insert, "Miro Board (Capable)" |
Embed a board by pasting a link | Confluence editor |
Connect your Miro account | Any Miro macro's configuration panel, or the space's "Miro" page |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Connect Miro | - | Starts the Miro authorisation in a new browser tab (OAuth providers block sign-in inside an iframe). The app then polls its own status every 2.5 seconds while the consent tab is open, and re-checks whenever you return to |
Disconnect | - | Deletes your stored Miro token on Capable's server. Board browsing, sharing and people sections stop working; boards already embedded on pages keep rendering. |
Open Miro | - | Opens https://miro.com/app/dashboard/ in a new tab from the gallery's connection chip. |
#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.
Display mode, Width and Height do not appear in the configuration panel until a Board URL is set.
Typing in the Board URL field silently clears the stored board id and name, so the collapsed "Selected board" summary loses its title until Miro can be asked again.
The board does not respond to the mouse until you click it. A transparent "Click to interact" overlay stops the frame swallowing page scrolling, and it re-arms when the pointer leaves the macro.
Anonymous and unlicensed readers can see the board, because the view needs no server call, but get nothing that requires a Miro connection: no board names, no sharing summary, no member list, and no gallery. Every Miro-backed request requires a signed-in Atlassian account.
Board previews and board names behave differently: previews are derived from the board id and work without a connection, but names need a Miro call, so an unconnected viewer sees real thumbnails labelled with the board link instead of its title.
#Related
How it actually behaves.
