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.
233 commentsComments are closed
[Deleted User] commented
yes we really need to be able to make subteam
Jack Michel commented
+1 on this idea.
We have larger national teams and then smaller office-wide teams. It would be great if they could be more directly integrated.
Yes, subchannels are essential to running projects and large enterprise wide programs.
In order to work with Teams, this feature is crucial. In any organization larger teams are usually built from subteams, e.g. a site might consist of various departments, each with a separate manager. Now, when the site manager creates his site team, he jsut can add the various department teams and maybe some single users who don't belong to specific subteams. Then it's all done. No hassle to maintain all individual membersof all teams over and over again. This makes on- and offboarding of employees a snap.
I would like to be able to @mention a specific group within our all staff Team. This would be helpful instead of having to @mention twenty individuals. This is core to the purpose of the product. Make information available for the entire group while calling out the specific subgroup that needs to take an action. This is the only reason my users are hesitant to move from email.
Tania Jordan commented
Yes I totally agree as well that having sub-teams would be great! Also the fact that each channel is created with a separate folder in the document library messed up my original library structure now, as I want some of the topics to be a sub-folder, but when I move the folders around in SharePoint , they are no longer accessible from the channel.
Jared Pickerell - Troy Public Schools commented
Would be great in our school. Some examples:
- A top-level group of students > building/school level group > Class Of 20xx groups
- A top-level group for employees > building/school level > teacher/other groupings groups > etc
I can do this with security groups and distribution lists and it hinders being able to migrate some of these over to Groups.
Stevie E commented
Multi-level channel hierarchy in Teams is a much-needed feature!
Since O365 group subsites do not create new groups (and therefore cannot become new teams or channels in Teams), I need a way to organise hierarchical projects while retaining the Teams integration.
This would be very useful, as input to the channel might come from differents teams (channels).
Multi level sub channels will be a great addition. Right now we have multiple teams, its pain to manage permissions on every channel and too much of scrolling, especially on smart phones..
Dan Wilson commented
This would be very helpful
This would be an exemplary addition. Sometimes, you have specific teams within teams that you want to notify. As I stated in one of my articles:
"When a team is made, there is one role that controls all of those sub-channels. This also means that it is limited to tagging that one team, essentially as an @all feature. What I want to see is a way to have a single team, and within those channels be able to tag @Admins, @Editors, @Writers. Currently, this potential feature hasn’t been addressed as of yet. Instead, it seems users are encouraged to make private teams. But this is a different monster entirely. These private teams cannot be mentioned in another team’s conversation threads, rendering them useless. Sub-teams and roles would also fix another requested feature on UserVoice: more efficient permission handling."
Brandon Schwarz commented
+ 1 more for "sub-channels"!!!!!
100% agree - this is the feature that brought me here.
Jake Moore commented
100% agree. I have far too many top-level teams here. If I could nest teams that would be helpful. My main requirement is to keep 'channel' permissions separate to 'team' permissions but currently the only way to do this is to create a new top-level team which becomes overwhelmingly large when a new channel is created for each incident. If I could somehow either assign separate permissions (user access control lists?) to each channel then this could be an option too however, greater nesting would indeed be super helpful.
I have the same issue. I have set channels up within a team, but not all members of the team will need to be part of every channel as everyone has different roles and responsibilities. It would be useful if you could only invite certain members of a team to specific channels within the team as some team members will not need to receive the amount of messages as others will so I worry that some will find this distracting and annoying.
Joseph Garlinghouse commented
Apologies for some errors in the above. I was dictating with Dragon.