Connect Miro so Coworker can see your whiteboards and what is happening on them. Miro is a per-user (individual) connection, and one Coworker connection covers one Miro team.
What Coworker can do with Miro
Index the boards your Miro account can reach — name, description, link, owning team, sharing posture and member roster
Produce one report per board that saw activity: what changed on the canvas, who drove it, and where the board now stands. Quiet boards, and boards nudged only trivially, produce nothing.
Read boards on demand — list the boards you can access, open a board's full detail, read the items on it (sticky notes, shapes, text, cards, frames, connectors, images, embeds) and see who has access and with what role
Each board becomes a Document entity, and connected collaborators become Person entities with the strongest relationship that applies: OWNS when they created or own the board, EDITS when they created or last changed items on it, VIEWS when the board is merely visible to them. Board contents stay in the raw store as a compact structural snapshot rather than becoming hundreds of sticky-note entities.
Before you start
You need an active Miro account
Miro must not be blocked for your workspace by a Coworker admin
Know which Miro team you are connecting — one Coworker connection covers one team
Connect as a member
Go to the Work page at app.coworker.ai and click Data Sources.
Select Miro under Available sources.
Complete the Miro OAuth authorization.
Miro moves to Connected and your boards begin indexing.
Connect as an admin
Outside Miro Enterprise there is no organization-wide Miro credential, so there is no workspace-wide connection to make. An admin's levers are:
Connecting their own Miro account, exactly as a member does
Adding a second connection if you have a second Miro team — the first healthy credential pins a connection to one team, and credentials from another team are excluded rather than merged in
Turning off the "team-visible means network-visible" behaviour if your Coworker network is broader than your Miro team, which treats every board as restricted
Blocking Miro for the workspace from Source Settings
Good to know
Each board gets its own access policy built from who can actually open it: the connected users whose credentials listed the board, plus the board's own member roster narrowed to people who have connected Miro. Coverage widens as more of the team connects, and never over-shares in the meantime.
Link sharing is deliberately ignored as a visibility signal — "anyone with the link" is not the same as "anyone in this network". If a board's policy cannot be applied for any reason, the board stays private.
On Miro's free plan every board is team-visible, so all policies come out open. That is Miro's reality faithfully reflected, not a Coworker default.
Miro exposes no email addresses outside Enterprise plans, so people are identified by the address they connected with. Board members who have not connected appear as anonymous participants rather than being guessed at.
Miro rotates refresh tokens on every use, so you may occasionally need to reconnect. That affects how fresh your coverage is, never who can see what.
A board's modified date reflects content changes only. Renames, description edits and sharing or membership changes do not move it.