How come -- as a Company Admin in Miro -- I am not able to see every board that has been created by users in my org? I was looking for a post that would describe “rights and limitations” of a company admin on the forum. I can’t seem to find anything.
Three times I’ve had users ask me for help on their boards -- edits, moves and changes -- but I can’t see their boards until they add me to the permission list. What if an employee leaves the org?
Would you think a company admin would be a super-user that can “see all”? Am I missing a default setting somewhere?
Page 1 / 1
@Doug Harrison - Have you reviewed the following article yet?
We are on the Consultant plan, so the Enterprise rules may (or may not?) apply to me.
I see that “In case you do not see a board on the dashboard, it means that the board hasn't been shared with you, but you can still find it: search by the board name…”. It’s still odd to me that a company admin has to guess at what is going on and has to do a blind search to find content in order to support it. I trust there is a greater good.
I’m very grateful for your help, Robert.
D
@Doug Harrison
We are on the Consultant plan, so the Enterprise rules may (or may not?) apply to me.
Correct - it would not apply.
I, too, have the Consultant Plan and just tested this scenario by adding one of my test accounts as a member of the plan. Because the default sharing settings for boards and projects are such that only the creator can see them, they are considered “private” and no other users can see them (as you are experiencing).
There are a few ways that your users could give you access to their boards:
Then you would set the permissions so that Anyone in your team can view this project is toggled ON.
Then you ask the user to move the board they need help with to that project. In this scenario, even though the board’s Team permissions may be set to “No access”, your project permissions will override them and you will have full access to the board. Once they (or even you) remove it, you will no longer see it. NOTE: If you go this route, all users will see this project and can open any boards they do not own in view-only mode, but only you (as the project owner) and the board owner will have edit access - it’s really kind of convenient that it words this way. Here’s a screenshot of what it could look like if you set up the project:
Another scenario is that the user creates a project with “Anyone in your team can view this project” is toggled OFF, but they add you as a member of that project and give you edit access, e.g., they call the folder “Bob shared with Doug”. This would be handy if they needed you to see many boards and didn’t want to have to share each with you individually.
I hope this provides some clarity and options for you. Please "smash that Like button" if it does
@Robert Johnson Great explanation Robert, as always!
I understand your use case @Doug Harrison, but I don't agree that a company admin should be allowed to see everything in a Miro team. Figma and other design tools have the same functionality, i.e, creating content that only you have access to. Even Slack has this, in the form of direct messages and private channels (although it's possible for workspace owners to get access to everything, even private messages, it's quite tedious and it's set up in a way so that affected users would be notified).
Henrik. I understand your point about privacy, but I guess a lot depends on company culture and the purpose and role Miro plays as a communication tool and learning environment within the organization. As a non-profit, we have secret stuff, but it is usually on the back of an an envelope on someone’s desk.
Robert. You’re going above and beyond in giving me ideas to come up with possible remedies. Thank you again for your thoughts and encouragement. They make sense.
