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.
Rhys
shared this idea
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-
Cass
commented
Sub channels would be of great help, especially since you can restrict access to channels. We have 50+ audits that we would like to share with different set of individuals. Creating a channel for each of these makes navigating through the site onerous, as with creating permissions on the SharePoint side. Please consider sub channels (with permission restrictions).
-
John
commented
This is a much needed part of any project. Imagine if you could only create one layer of folders and have no sub folders. We have multiple projects going on with many sub categories. Makes for a pretty ****** application when people either have to search through a who channel to find a sub topic. Might be better off finding a 3rd party application instead.
-
Dale Gardner
commented
Sub-teams would be extremely useful. Channels do not cover the same use cases.
-
R Miller
commented
I think it was a bad decision to dclin sub-teams and sub-channel
-
David
commented
+1 for this feature the ability to @ a certain group of people inside a team would be a benefit instead of sending it to the whole team.
In my use it would be a group of experts to a certain topic you need to get the request to. currently we are making an e-mail distribution to get around this but the @ ability would be a much cleaner solution
-
Nicole Bailey
commented
we have multiple groups of people working on a given project, we have the project group, marketing group, technical group, it would be ideal to assign people a given group where you can '@' a specific group for an action item or question. Please please please make this a functionality.
-
Eldu
commented
Working for a large corporation, we have very leveraged teams, but also want a team specific to an organizational unit. The leveraged/external resources to the organizational unit may need to see collateral for a given project on our team site (implemented as a "channel" for a specific project), but not for other channels (projects which a given leveraged/external resource really may not need to see) on our team site. This seems like a very valid use case to me.
-
RoDu
commented
While we are in the process of beginning with Teams, using subchannels really was one of the first questions we had.
-
Bill Lloyd
commented
+1 vote for this feature request.
Why would the Microsoft Teams team reject this kind of request, especially when there are so many who would like to have it added?
-
Jon
commented
this should be part of design of private channels. use case for us would be : Patients (root private channel) and subchannels would be Site #1, Site#2, On Call... adding staff to Patients channel, staff would see all conversations across subchannels/sites. Staff added to Site #1 would see only those conversations. Use case is nested *channels* but not "teams". There's hierarchy in every large organizations.
-
Jason Simone
commented
Just to chime in, I am happy NOT having this feature. We need the ability to pull other people in to certain team projects also, but I don't think "nesting" is the right way to think of this. The planned feature regarding access controls to change membership and visibility for different channels within a single team seems like the appropriate way to handle it.
-
Anonymous
commented
Many teams at our org need this. Also there will be departments we cannot even consider onboarding to teams until we have this. Thanks!
-
Tanveer Huq
commented
This is a must have feature.
-
David Ulloa
commented
This feature is a must, please re-evaluate
-
Jay Hadley
commented
Also, I noticed that this feature was declined in June of 2018. Teams has grown in use and function since then. This really needs to be reviewed again.
PLEASE REVIEW THIS AGAIN
-
Jay Hadley
commented
We have Teams setup for Projects and the Customers under that. However, it would be great to have subchannels so we can place multiple projects under the customer. As it is right now we have to have one channel with many project intermingled in conversations, files, notes, wiki and other things we use. Why not give the users of Teams more flexibility in how they want to use it for their on needs. Don't place baby in a BOX!!
-
Andreas Hagendorf
commented
Have to agree, this would be a very useful feature!
-
Marie
commented
I don't understand why this option is being rejected while it is THE thing we need to facilitate the life of a cross-functional teams.
For instance, when you work for a program splitted in 20+ project; you create a Teams and structure it as every project is a channel. Issue is that project managers lose the ability to organize themselves with their teams thanks to subchannel (and I really mean channel with the ability to have a conversation and to personnalize the tabs). Of course you can create a new team, but then you loose the transparency the tool brings because you are not going to add 250+ people to every single project Teams.
It makes no sense to me regarding collaboration but maybe am I missing something key that will help to solve my problem?
-
Rob W
commented
In light of other tools capabilities to do this functionality - with customers desires to stay within one platform such as Microsoft, rather than integrating in other products, it seems MS should reconsider and enhance/develop Teams. Organizational hierarchy in Teams would add so much - and is what we need - and sounds like it is what others need as well.
-
Tobias
commented
Subchannels would be the last step towards moving our organisation entierly to Teams.