Skip to main content
Open

Default to Least Privileged Access When Moving Boards to a Space

  • May 14, 2025
  • 2 replies
  • 57 views

When a board is moved to a space, it should not retain the permissions it had in its previous location (including if it was “not in a space”), it automatically adopt the default permissions of the new space. If not, the board security should default to the least privileged access—ideally private to the board owner or with explicitly defined access.

This would prevent unintended access, especially in enterprise environments where boards can contain sensitive or in-progress content. Retaining broader permissions from a space (or from being outside a space) increases the risk of accidental oversharing.

Applying a "zero trust" default helps teams control visibility intentionally, rather than having to retroactively restrict it.

Thanks for considering this improvement to safeguard content and support more secure collaboration.

2 replies

Eca
Mironeer
Forum|alt.badge.img+5
  • Mironeer
  • May 17, 2025

Thanks so much for taking the time to submit this idea, ​@Debbie Baker. Our team will review this and it’s open for votes and comments. 

 

For those coming across this idea, if you feel this would be helpful for you or your business, please be sure to vote for it and leave a comment about your use case to help our team scope this request!

Thank you again for helping make Miro better!


I came here because I didn’t understand the permissions.  We have a pretty unorganized Miro account. And spaces sound nice, but I also don’t want to destroy the access for other users just because I want to be able to organize.  Feels like it should be an radio box option when you move a board to a space: 
A) Keep permissions as is. 
B) Restrict permission to only people in space
C) Retain legacy permissions, but add space users. 

I actually was afraid to move things because I didn’t understand what would happen to the permissions.