Nesting sub spaces into spaces

Hi @Cedric Lavoie 

Thank you for submitting this idea about sub spaces! We appreciate your feedback, and our team will review this. This suggestion is now open for votes and comments.

For those just joining the conversation, if you believe this feature would be helpful for your workflow or business, please take a moment to vote and share your use case. This will help our team better understand the demand and prioritize accordingly.


Thanks again for helping improve Miro!

Use Case:

I have three teams.  They are all generating boards.

I need to generate boards that relate to all three of them, not to one of them in particular.  I would like to save those ‘all three team boards’ in a space where the three teams spaces are saved.

Thanks!

I run multiple teams all related to bettering the FE of our platform. We use Miro for meetings about governance, brainstorming solutions, presentations, etc. I would love to have just one link for all FE developers to be able to access all of this information, but as it stands i need to make multiple spaces (which i only just now realized i can use the top search bar to search through) and link them to all of the spaces individually.

Nesting would be a major help

Here is my use case:

• I have a collection of Products/Services
• Each Product/Service has a collection of Features
• For each Feature we use Miro for Architecture Diagrams, Designs, Meetings and Agile workflows (retros etc) etc etc
• It would be great to if Miro could support subfolders (“sub spaces”) such that we can have:
  • Service A / Feature B / Meetings / Meeting Boards
  • Service A / Feature C / Arch Diagrams / Diagram Boards
  • Service A / Feature C / Designs / Design Feedback Boards

Another thing to note, though while not a use case it might help prioritise this feature, is that your competitors such as Lucidchart and Whimsical offers this feature

Yes, please x 1000.

This will be very helpful for categorizing boards into teams and projects. Right now we have to add that into the product by putting team and project names on the name of the board eg:

• TM - PRO - Boardname 1
• TM - PRO - Boardname 2

This gets a bit unwieldily, and it would be great to just organize boards in a standard directory tree.

Definitely a MUST HAVE feature! 

For me, the possibility to make nested Spaces / Sections / Canvases is a game changer. I am starting to work on my personal game and now I am deciding how to organize all the processes and considering Miro as a tool for Game Design Documentation. With the brand new Spaces, Formats, and Docs capabilities, it could be a perfect tool. BUT without nesting, it will be a nightmare to navigate such a GDD. So, for now, the only option is to use Notion / Confluence with embedded Miro frames for whiteboard elements. In case of nesting implementation, the whole GDD / Project documentation can be solely kept in Miro without any additional tools.

What does this have to do with the Miro feature request? There are plenty of solutions which support nesting, but with different capabilities and purposes. The point is that here we can request a feature specifically for Miro.

Totally agree with you on this, it should 100% have an infinite level of nesting, ideally for boards as well. But at least for spaces should be a minimum, which could already allow people to organize Miro as a documentation hub for their teams.

Great day to you as well! 😉

Use case:

in company we have many teams working in miro, so we have as many or more spaces.

My team uses miro for retrospectives, so every two weeks we add new board.

It would make way easier to navigate if we could organize them by quarter and year as in standard directories in Windows/Mac/Linux. There is just too much stuff within single level in a space.

I follow that 100% as we have many departments with sections, and each section has their own workflow. I need to categorise all this in levels (tree structure)

Upvoting.
Spaces, Sections, Frames - why is the general UX pattern here to NOT allow nesting? We need to be able to structure our content because currently, things are not scalable. Thanks.