Skip to content

Miro

Updated May 26, 2025

Miro is a virtual whiteboard. We can insert images or videos, we can use pre-made templates, and it integrates with other apps such as Slack or Google Drive. It is also a collaborative whiteboard: we can share a board with collaborators, add comments, tag specific people.

Product information

Product website

https://miro.com/

Login page

https://miro.com/login/

Sharing a board

You should always ahre the Guest link with everyone you need to join a board, paid seat or not.

Tutorials

Number of seats

We have a set number of paid seats, more can be added if it is justified.

Every team member can have a free account to use for ad-hoc needs, and they can also have an editor access to relevant boards from the MobilityData team if needed.

More information

Why are we using this?

  • We collaborate remotely
  • It is simple to use
  • It creates beautiful visuals

For what kind of tasks are we using this at MobilityData?

  • Visual thinking. Example: pathway design
  • UX design: User flows, site maps. Example: validator user flow
  • Collaboration (internal, and also with other stakeholders)
  • Workshops, digital brainstorms, interactive presentations. Example: a technical presentation

What is our plan?

  • We have a team plan. With this plan, we can:
    • Invite external stakeholders to a board (without having them needing to login)
    • Create as many boards as we want
    • Create projects: think of them as folders, containing a selection of boards
  • Team VS free plan comparison

How are the accesses managed?

The different access levels are managed by the roles1. Roles are defined at two different levels:

Level 1: Individual boards Level 2: Projects
Think of it like a Google Doc file. The accesses for individual boards are:
  • Owners can define who has access to a board, delete or duplicate it
  • Editors can edit the content and share it with other users
  • Commenters can only add comments
  • Viewers can only view
 Think of a Google Drive folder, containing several Google Doc files. The accesses for projects are:
  • Owners can edit or delete the project, add/remove boards from the project, make the project visible/invisible to the entire team and define specific users' access.
  • Editors can add/remove and edit boards in the project, and define specific users' access
  • Commenters can comment on all boards of the project
  • Viewers can only view

  1. Read more about roles here. ↩