Miro uses role-based access control to manage what a user can see or do in the product. Roles are defined on the level of Boards, Projects, Teams, and Companies. Some of the user roles may be inter-dependent, require a specific plan or a paid license.
Roles on boards
-
Owner of a board can define who can have access to the board, can delete or duplicate the board, move it between projects or teams and save the board backup. Ownership can be transferred to another user.
-
Editors are users who can edit the content of the board, duplicate and share it with other users.
- Guest editors are users who can edit the content of the board but cannot duplicate it and share it with other users.
-
Commenters can view the board content and leave comments visible to other users on the board.
-
Viewers can only view the board.
Role on a board can be received directly by invitation or indirectly by default sharing settings on the team level.
Roles in projects
Available for: Team, Consultant, Business and Enterprise plans
-
Owner of a project 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. Ownership can be transferred to another user.
-
Editors can add/remove and edit boards in the project, and define specific users' access.
-
Commenters can comment on all boards in the project.
-
Viewers can view all boards in the project.
Note that project access and board access complement each other and work at the same time:
- If a user already has a role on a specific board, the role with maximum access takes effect.
- When their membership in a project is revoked, the user loses project-incurred access rights and retains only the roles on boards received directly.
Role in a project can be received directly by invitation or indirectly by default sharing settings on the team level.
Roles in teams
- Team admins are members with extended rights to manage users, access rights settings and other team properties. They don’t receive any special level of access to other users' content. If there are a few teams in an account, each of them has its admin. There can be multiple admins per team.
-
Members are users who were invited to a team and can access all its boards and projects with respect to their sharing settings as well as create their own boards.
-
Non-team users are users who were invited directly to boards, but not to the team itself. They can access the boards but can't create their own ones.
Non-team users are available on paid plans. On the account level, Billing Admin is also recognized. This status is given to a person who starts the subscription having attached their card to the account.
Company level
Available on: Enterprise, Consultant and Business plans
A Company can have several teams under its umbrella, Occasional Members and Non-Team Editors.
- Company admins are members with extended rights to manage users, team admins, security, access rights settings, and other properties of the Company and teams within it. They don’t receive any special level of access to other users' content. There can be multiple Company admins.
-
Occasional members are users who were invited to a team of the Company as members and consume Day Passes. They can access all the team boards and projects with respect to their sharing settings as well as create their own boards.
-
Non-team users are users who were only invited directly to boards in any of the Company’s teams. Those Non-team users that can edit boards in the teams consume Day Passes.
On the Business plan, Company and Team admin roles are merged.