Permissions and access
Start from what you are seeing rather than from what you think is broken. Each page below names the symptom, explains why it happens, and says what to do about it.
Several of these are the product working as designed, which is worth knowing before anybody raises a ticket.
#At a glance
Symptom | Usually because |
|---|---|
Readers see a Miro sign-in screen or a "you don't have access" message inside the frame | Embedding does not grant access. The board itself is not shared with those people in Miro. |
Cannot find Display mode, Width or Height in the configuration panel | Those controls are hidden until a Board URL has been set. |
Cannot find a way to choose a different Miro team or organisation in the picker | A Miro token belongs to exactly one team, and Miro's organisation and team listing endpoints require Enterprise plus Company Admin, so the team is shown as a label. |
Logged-out or unlicensed readers see the board but no board name, sharing or gallery | Those readers get no server calls at all - the view is just the frame - and every Miro-backed request needs a signed-in Atlassian account. |
Admin cannot find any Miro settings | There are none. The app's settings entry shows only an Introduction section, and there is no space settings screen. |
"View on Marketplace" link is broken on an unlicensed site | The Miro app does not pass a Marketplace id into its licence screen, so the link resolves to an invalid address. |
#In this section
#Related
Most of these are expected behaviour.
