Skip to main content
Open

Ability to add non-team users to project sharing settings

  • August 24, 2020
  • 1 reply
  • 155 views
  • Lars Kempe
  • Peter Simmons
  • BrendanD
  • DKA
  • MelS
  • SilviaS
  • Anderl
  • Lakshmi Narayana Ayinala
  • Michael Brawn
  • Daniel Lind
  • Jean-Charles Perron
  • mikemcmaster
  • Gregory Primosch

Background: Our organisation currently uses a team with business plan licenses.

Our business plan license holders regularly need to collaborate with external Miro users who are not necessarily members of our team in Miro.

We have found it is very convenient to organise boards into projects to simplify board permission management.

One limitation we’ve found that somewhat diminishes the usefulness of projects is that we cannot add non-team users to the project’s ACL. I realise on the business plan, you are only able to have named editors who are in the same team that the board resides - this makes sense from a licensing perspective.

However, it would be very useful if you could add non-team viewers/commenters to projects. This way, if a new person needs to be given visibility of a project-grouped set of boards, they only need to be added and managed in one place. Currently, to achieve this, the sharing settings for each individual board needs to be changed which is time consuming, prone to human error (e.g. accidentally missing a board) and needs constant maintenance (e.g. a new board is added).

Could this functionality be considered for a future update?

Thanks,

Was it helpful?

1 reply

MarkT
  • Active Contributor
  • 32 replies
  • August 18, 2021

This is something from which we would also benefit.  For the past 18 months we have been adding users individually to each board, where adding them at project-level would be significantly easier.

We did experiment with the idea of adding some users as full members and using this to allow us to set permissions at project level.  However, this was a non-starter for another reason; when you add users to a team they are able to see the names and email addresses of everyone else in that team.  That would be a GDPR breach for us as we are running external workshops in some cases.


Reply