Nested Teams and sub channels (Re-opened)
1541 have already voted for this, but Microsoft have disabled the option for addition votes. (https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16954120-nested-teams-and-subchannels)
Sub channels or grouping of channels, createdand managed by the team owner.
Could it be possible to create teams within teams. For example, we have a Development Team at our company which consists of two sub-teams, tech support team and project team.
I’d love to be able to have a “home” top-level channel for my project team, and then have sub-channels for each project that we are working on.
The fact that this is not a basic feature is astonishing. The value of Microsoft Teams would skyrocket if there was a way to nest groups.
Indeed, most important reason why we are all starting to detest everyone 'creating a teams' for something. I really don't understand how people can do without the possibility to organise in a flexible way. Everything in 1 main folder is like people who save all documents on their desktop...horror!
This is an actual feature that if added I'd use!
the need for nesting or sub-channel creation is critical to success with Teams on a larger scale. I have multiple department projects that if this capability was available I could have one parent site for X Team projects and they could have their own sub-channel(s) to collaborate and communicate through.
Sub-channels should be a basic functionality to minimize the need for so many channels at the parent level. We are a product development company who needs the sub-channels for one level deeper categorization of conversations and to limit the clutter
I would love for this feature. Or just some way to organise my channels.
Phil Hawkshaw commented
This would solve a load of problems with Teams sprawl!
Wayne Head commented
Nearly every competitor has this functionality day 1 and it's a must for any medium/large corporation. There needs to be *some* way to nest, or group teams (or sub-groups). Yes, pinning helps, but in large organizations even your "pinned" list leads to unwieldy lists of teams, missed notifications etc..
Added to this the inability to add more than 30 private teams, or the ability to delete or archive private teams to add room for more. This means that even making a lot of very specific teams (that should be together) still hits the wall pretty fast.
Our current Teams structure is a mess. Subteams or nested teams would help this tremendously. We could reflect our actual org structure and secure teams accordingly. Private channels and multiple teams only get us so far. Thanks for your consideration. I love the frequent Teams updates.
I agree with others, this would be so useful.
We are an extremely large corporation (multiple thousands of employees) with hundreds of offices all around the world. Creating a new channel for each of our offices projects, teams, etc. instead of having access to subchannels is simply unmanageable and pure craziness. Unless this feature becomes available in the future we might have to switch to Slack.
Jayesh Patil commented
Our training team need this feature wanted to know when this feature will be available.
Desperate for this feature. I am from a global school, multiple campuses and we moved onto Teams. We have a huge curriculum, classes, units and we need Team sub channels for each channel.
OneNote does this very well, why can't teams? Please implement this, will make things so much better!!
JEFF BERG commented
how is this not a feature. It really should be
B Washburne commented
At the very least, please enable sub-channels.
Gotta have. Makes no sense not to have
Yves Basquet commented
Teams is about enabling people to work collaboratively together, within set organisations. I guess many of us follow some sort of work breakdown, from the top of the organisation down to adhoc teams created for specific work items to be done.
Without subchannels, we can't replicate that work breakdown, set specific subchannels that represent that structure AND LIMIT THE COMMUNICATION TO THE ONES ACTUALLY IN AN ADHOC WORK ITEM SPECIFIC TEAM.
Result, no way to manage an efficient teams communication. As a consequence, WE CAN'T REALLY USE CHANNELS, a real shame !
We are down to using Teams by creating specific chats per work items, away from the channels. Basically, doing what we previously did with Skype.
A lot of effort and value in Teams wasted away because we don't have subchannels that allow to taylor communications to the actual work breakdown performed by the organisation.
Brian McFadden commented
We need a grouping to organize large numbers of channels within a Team (Team -> Grouping -> Channels). Separate teams are a work around but clunky and don't organize well in the application.
This is a must - I work in a multi-national and can't control how people create Teams. I'm already part of 50 teams and its just a mess.
Tim Sanson commented
Nested Teams makes no sense to me, but sub-channels are becoming a must...
Let me highlight that one of the key benefits for us with Teams is not only doing the work today, but being able to retrieve and update that work at some future time.
Creating a team creates a new SharePoint page for the Team, and each Channel creates a new Folder within the page file area. (We deploy the largest practical Team otherwise file collaboration is not possible across smaller teams.)
Within a large team, channels either end up being broad, and then specific discussion topics get lost in a large volume of discussion, or channels become very specific, and there are a large number of channels that may contain related content...
Sub Channels allow content within Channels (and the underlying file structure within the site) to be more logically organized and managed, and all the resultant conversations are more focused on the specific topic area.