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
Joseph Garlinghouse commented
There seems to be no way to establish sub-teams within the team. As an example, working at a local health department, one team may be "environmental health". Within that team, it would be fantastic if there could be sub-teams. To further illustrate the example, these could include: Lake water testing, septic, well testing, etc. Within the lake water testing team, there could be channels such as leg superior, St. Mary's River, Dukes Lake soldiers Lake, etc. There could also be channels within septic including residential and commercial. Basically what I am saying is having only one level of team makes the organization to simplistic. Organizations may have multiple levels, with some employees present in some sub-teams whereas not present in other sub-teams.
Definitely smaller teams on a project/team. This would be very helpful when trying to assign tasks through outlook/tasking. Then, like a security group controls folder access, the assigning a task can be given to a team, and as a member of the team you can move the task in progress or complete. Presently we are creating a team; graphics team; builder team; manager team for every project and then creating a roll-up account. Additionally sub-channels are also helpful- we have many phases and many sub-teams may be called upon to contribute at different phases.
+1 We have a delivery team and this consists of managers and programmers, and sometimes you want them all together but in other cases it's more appropriate to have separate channels for just those specific sub groups.
+1 for sub-channels. We have a huge demand for this
Justin Leung commented
I agree with Rhys, our company have many projects and need this sub team function.
I agree with Tobias.
and to expand on reasoning, here's an example of naming convention a team may use to keep things organized.
-BP - Word
-BP - Excel
We also need sub-channels, we have many different components in projects and the channel list becomes long and unclear.
Tobias Zackrisson commented
It would be a nice feature to have a sub-category on channels.
- Sub Channel
Leah Schlosser commented
That would be great! We have like named practices in each of our 5 office cities. It would be great if we had the ability to create sub-teams from one single parent that could be city specific. That way we aren't clogging the parent team with information that isn't relevant for the other 4 cities. We could use the parent team only for information that is relevant to all "development' practices (as appropriate)!!
Nick Ellis commented
Indeed. We work in IT support, I was hoping to have a parent channel called "Major Incident" and then be able to spin up a new child channel for each major incident that occurs
Nested Channel > Sub-Channel(s) would be a great addition. For example Marketing > Event 1 etc.
The general channel can be home for the entire team, but presumably each channel (which is a folder in the "files" doc library and has its own conversation) would be nice to be able to nest sub-channel for further organization of sub folders of files, and for separating out sub-topics of conversations/projects
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. Alternatively, some form of threaded convos may work too...