Nested Teams and subchannels
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.

This request has been reviewed and declined by the feature team.
You can continue to up vote this topic as well as leave comments. Depending on the ongoing feedback, there is always a chance a topic will be revisited based on user demand.
-Warren
233 comments
Comments are closed-
Anonymous commented
Instead of declining the idea why not show us how to do it with the current technology. If it can be done - great. If not - then perhaps it’s needed?
-
Anonymous commented
Really need sub channels and tree structure
-
Anonymous commented
This feature is sorely needed by many, would add a lot more functionality and reduce the amount of 'teams' that those in large organisations inevitably end up with.
-
EA commented
At least it must be possible to select members to participate for a channel.
So, for changes only these channel members are informed, same for channel meetings where I do not want everybody by default. -
Anonymous commented
No solution to this? Teams need a tree structure for channels. Adios Teams. Looking for another software solution.
-
Anonymous commented
We generate about 1,000 teams a year. My users complain that it's hard for them to follow the teams. A tree-shaped organization would be perfect.
-
Totti commented
Use of teams has been changing from 30-50 people to over 200 people.
Super fits for project style of work.To do so, Sub-channel is essntial.
like below imageTeams: XXXX project
Channel 1: Civil engineering team
Sub channel 1: General info to civil team
Sub channel 2: Foundation design team
Sub channel 3: Structure design team
Sub channel 4: Request from other teamChannel 2: Piping design team
Sub channel 1: General info to piping team
Sub channel 2; 3D modeling teamIt is possible to achieve above structure with builting huge number of teams, but it would be mess and also we will be in trouble to send info to other subchannels.
I met many potential teams company members and most of those guys are requested above function.
Actually, our comapny (10000 users) will introduce teams fully to our normal work, if ths sub-channel function is ready.
Alternative idea is
1,Grouping several teams
2, Allow forward and link between teamsThank you!
-
Anonymous commented
Having the ability to add sub channels would eliminate having to create a new Team for every release of the same product.
For Example:
Production Release Team
Subchannel - Production Release 33
QA - subchannel
Business Dept - subchannel
Subchannel - Production Release 34 -
Stephen Powers commented
Please reconsider this. I am trying to build user acceptance and one of our biggest issues is clutter for our volume of users. To help understand we support Point of Sale Equipment. If I want to have a End-Of-Life Channel with a Sub-channel of a specific device name that is End of Life then it would help keep the channel organized and easy to reference dialogue amongst my team and me.
-
Tim Nagels commented
Nested Teams doesn't make sense, but context-integrated chat-channels would be usefull. E.g. Our team manages a very large number of products, but creating a full channel per product is over the top as navigation becomes cluttered quite easily. So I would think just setting up nested navigation could benefit a lot of our teams.
-
Kalpesh Khetani commented
Very interested in using a tool like Teams to completely transform Business Communications. Currently everything is done via email. Things like weekly Company Updates, Notices, etc would be ideal candidates.To do this, it is imperative to have nested Teams! Otherwise you have to manually manage scores of individual Teams. Am I missing the obvious or wouldn't you simply link it to Active Directory structure?
-
Anonymous commented
Organizationally, It makes sense to be able to create sub-teams. I'm finding it more cumbersome to use without being able to create subteams.
-
nowayjose commented
Teams is garbage. Garbage software, garbage team, won't listen to consumers.
-
Anonymous commented
Periodically, I use virtual meetings including sub-group meetings. Currently, I use MS Teams for sharing the visuals and phone conferencing for audio, supporting this feature but with poor sound quality. It would be much more convenient if we could have sub-group meetings in MS Teams
-
Vibhor Agarwal commented
Agree, MS feature team should seriously reconsider their decision.
-
David Wood commented
The MS feature team should seriously reconsider their decision regarding sub channels.
-
Kevin commented
Like most of the other comments here, I am seeing more and more Teams and Channels that truly belong organizationally below others. For example, I have a dev team that has several areas of responsibility and each of those areas has several projects. Instead of flat list of 15 channels, grouping the channels under the areas of responsibility would make logical sense and reduce clutter. It also will let those team members only interesting in some of the areas focus on them and not have to pick through items they are not interested in.
-
Lucie Harris commented
Would be great to have sub-channels that could be expanded/collapsed on the side menu so that theyre visible if you need them
-
Anonymous commented
Like every organization ever, ours has a hierarchy of groups within other groups. The fact that this isn't an option is just plain crazy and doesn't reflect the natural organization of the work environment.
-
Vibhor Agarwal commented
Having a tree structure is a very common use case. I agree to the fact that the current single level hierarchy keeps it simple, but a mid way can be achieved by limiting the level of hierarchy up-to a maximum of 2 or 3. A team can always have sub-teams. Sub-Sub-teams can be prevented, but a sub-team is a must.