# Legacy Connect token import

It is safe to repeat and is retried hourly until it succeeds.

---

## Where you do it

| **Task**                             | **Where**                                                               |
| ------------------------------------ | ----------------------------------------------------------------------- |
| Insert a Miro board on a page        | Confluence editor, /insert, "Miro Board (Capable)"                      |
| Connect your Miro account            | Any Miro macro's configuration panel, or the space's "Miro" page        |
| Check who can open an embedded board | Macro configuration, "Who can open this board" and "People with access" |

---

## 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 |
| Switch team  | \-        | Re-runs the authorisation and replaces the stored connection, because a Miro token belongs to exactly one Miro team. The app watches for the team to change for up to 60 seconds.                                            |
| 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.                                                               |

---

## Worth knowing

* One Miro connection per person, and it is one Miro team. There is no team or organisation filter and none can be added below Miro Enterprise: a token binds to one team, and Miro's organisation and team listing endpoints require Enterprise plus Company Admin. The team is shown as a label, not a dropdown.
* Disconnecting removes the token from Capable but does not revoke the authorisation at Miro. To remove it there too, remove the app in Miro's own settings.
* Uninstalling the Confluence app does not delete stored Miro tokens - the uninstall step only deregisters the site's authentication key.
* Board sharing is read live from Miro and never cached in the macro, so a disconnected or anonymous viewer sees no sharing badge, and someone who pasted a URL for a board in a team they have not connected cannot see its sharing or members at all.
* A dead or revoked Miro token is reported as "Your Miro connection has expired" and treated as not connected, so the app offers Connect. A network or infrastructure failure is kept separate and shows "Miro status unavailable" - the app will not claim you are disconnected unless it knows.
* When that read fails the import falls back to a per-site map and retries hourly, so an upgrading customer could in principle be asked to reconnect Miro.

---

## Related

[Get started pageAnother part of how this works.](https://help.gocapable.com/miro/get-started-page.html)

[Miro space page ("Miro" in the space sidebar)Another part of how this works.](https://help.gocapable.com/miro/miro-space-page-miro-in-the-space-sidebar.html)

[How it worksThe rest.](https://help.gocapable.com/miro/how-it-works.html)

---

_How it actually behaves._