Shared channels within an organization
Shared channels within an organization will allow people in different teams to collaborate on a shared project or v-team in the context of their own teams. A channel can be shared across teams in the same organization.
this and three other items on the Backlog should all be fat Tracked as they would make Teams the ultimate collaboration space with excessive proliferation.
- Channel only members:
- Shared channels across organizations:
- Shared channels within an organization
- Public channels:
Jordi Borràs commented
I realized about this need just few days ago.
Reading about this, first ideas come from 2017...
A great feature to simplify collaborations between teams.
Now we have to put everyone in every team or create special teams for collaborations (a mess)...
This excellent idea would stop us from having to create so many teams! While it would still be appropriate for certain projects to get their own team, some projects need the communications department and IT involved, or Payroll and Marketing, etc. Shared channels would absolutely nail that use case and would save us some of the overhead of making a million new teams.
+1 . would be an excellent way to simplify the Teams / Channels architecture.
Excellent idea. Will help us tremendously.
L. Günther commented
Is sounds interesting, but we make the whole channel topic more and more complicated. I wonder if this creates more confusion, so it needs to be visualized clearly. Anyway, I agree on the need to have cross team interaction.
Ian Caldwell commented
+1 yes nice feature - but... there needs so be an owner of the shared channel, correct? how does this compare with allowing people to join a specific channel and not a whole team? things could get confusing
Awesome, please implement
That would be very helpful. Please implement
We need this. And shared channel should appear under my "own team".
Martin Waldhauer commented
Would awesome.... please implement ASAP
Any update on this one?
@Warren One year later, this is still on the backlog, I suppose, but could you post a quick update on whether there are any new developments? Even negative news are better than no news...
Matt Baker commented
Would also be great if a tab from one team's channel could be embedded into another team's channel as a tab with only one central source for the data i.e. no duplication.
David Lee commented
After hearing about this from an MS presentation, can we have an update from MS?
Henning Lorentzen commented
This would be a great and necessary feature.
Paul Kardash commented
Can we please get an update about this?
This is very crucial for mature and large organizations.
Some channels/ideas/topics must be communicated across different teams. I know some might offer to setup a common team for that, but that kind of defeats the purpose of working under one umbrella.
Heston Harper commented
Can we bring this back from the back log. THIS IS SUCH A CRITICAL FEATURE!
Cross collaboration is a MUST in any modern day business. Here is my example:
We have a Comms & Marketing Dept - We give them a TEAM. 'COMMS TEAM'
Within that Team we have channels for communications and marketing activities related to Sales, related to HR, related to Development, related to Operations - we give these CHANNELS.
COMMS SALES CHANNEL, COMMS HR CHANNEL, COMMS DEV CHANNEL
But those Channels have their own TEAMS - The Sales Team, The Development Team.
For maximum adoption, alignment, and use - we need to co-host the COMMS SALES CHANNEL in BOTH the SALES TEAM and the COMMS & MARKETING TEAM. So when the SALES TEAM want to look at the latest marketing they stay within their team and comment to the COMMS SALES CHANNEL which auto updates/mirrors to the same channel hosted in the COMMS & MARKETING TEAM.
This is a laboured / detailed example of many uses of these co-hosted channels - modern day business have matrix structures. The absence of this functionality is SERIOUSLY LIMITING our teams Teams abilities...
Echoing what others have said, would be very useful to have a public channel for each team, which would make it much easier to communicate between teams. Making them members causes permission issues; creating new teams for public and private chat is just a headache. Perhaps a toggle to set the ‘general’ channel as public or private?
My organization would greatly benefit from this feature. The current structure of the TEAM - Channel is impeding us from fully adopting the platform for inter-departmental collaboration. The ability to share channels without expanding TEAMs would greatly facilitate collaboration on multidisciplinary projects.