Board picker

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

In the macro config once you are connected: a searchable, sortable grid of your Miro team's boards, 24 at a time with Previous/Next. Picking a board fills in the Board URL and stores the board's id and name.

#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.

  • 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 itself.

  • 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.

How it actually behaves.