Ability to turn Teams into Channels and Channels into Teams
In some cases, Teams are created that can be absorbed into existing Teams, and inversely Channels may be created that outgrow their parent Team and need to be separated to allow for channels of it's own. Would be nice to have the ability to convert Channels into Teams (promotion), or convert a Team into a Channel underneath another Team (demotion)
This functionality is long overdue! It is obvious that some projects begin as a subset (channel) of Department A (team) but then grow and begin to involve other departments and need input from other stakeholders. Those other depts and stakeholders don't need to be involved in the other work of Dept A, so the original channel should be able to be promoted to Team status, preserving all files, chat, etc. from its inception but now with people from multiple departments being able to access the history and create the future of the project together.
I need to be able to migrate not just files but posts and bots from a channel in 1 team into another to allow departmental hand off of projects as they work through the pipeline of a project
Ken Kwon commented
We need the ability to take a Team and convert it to a Channel of another Team. With working from home, use of Teams in my org has increased like everywhere else and formation of Teams has been somewhat organic. So now we are running into a few teams that are very related and could be under one "parent' if you will. Thanks!
The obvious first structure is to build a team, and then have sub channels for projects belonging to that team - but at a certain point, certain projects become more complex and it would make more sense to be able to make that channel its own Team so that it can have sub channels, be more selective in team members, etc - This really is a must have feature and a big oversight in the journey of a team/channel
Yes! It is especially hard to get started with teams when you are stuck thinking should this be a channel?, a team? a chat? something else?. having more flexibility and allowing users to make mistakes and correct them later or provide for companies in spaces that are constantly changing, growing, adapting is critical especially with managing employees enthusiasm for getting on board with using the software.
Juan Pablo Gil Galindo commented
The Reason we make this practice is mainly Privacy