Shared Channels across organizations
Shared channels across organizations will allow people in an organization other than yours to collaborate on a shared project or v-team.
Coming in june according to Teams Roadmap. Functionality shown here: https://www.youtube.com/watch?v=a5mvbm2gSSo&t=78
Dominic Kent commented
A quick guide I put together on how you can create your own shared channels in Teams using Mio: https://dispatch.m.io/microsoft-teams-shared-channels/
If you want to try more than one tenant for free, you can email me email@example.com
This is a critical weakness of teams that it is designed for 'in tenant' cooperation with second class external guests. That's not how real teams work, who are usually operating across multiple companies who would never join under one tenant.
Dominic Kent commented
While it's not the original use case, you can install a Mio Universal Channel between differerent organizations as a workaround.
I.e. Company A works in Teams.
Company A creates universal channel
Company A invites Company B to join universal channel.
Company B joins universal channel (from their organization's Teams tenant)
Company A remains in its Teams tenant and chats to company B.
You can find out more at https://www.m.io
Your first three channels are free so you can test them out.
This flexibility will increase the adoption for Teams in our organization.
Capability to move a channel a new team and also share channels with outside organisations would improve our efficiency like you wouldn’t believe! Please do it!
Extremly important to us, any news on when this could be on the Roadmap..
Very important to our business.....any ETA on where it is on the roadmap?
Slack has this
With so many partner relationships to manage, my organization desperately needs this capability. It is essential for us to include staff and outside members for Teams collaboration on separate (private) channels.
Jeremy Lyon commented
Shared channels across organizations would have been the perfect solution for our State COVID Emergency Command Center. Unfortunately, the limitation of guests forced us to look elsewhere for Incident Management collaboration across disparate groups/organizations. Please add this GCC capability ASAP. Thank you!
Donna Andrews commented
As we begin implementing MS Teams as a one-stop application to replace Outlook+Skype+SharePoint to the extent possible, the Channel seems to be a great option to move the broken email threads into a single (internal) collaboration board, with a best practice of keeping each thread on a single subject within the Channel. This allows ALL of the stakeholders in the Channel to stay in the know. HOWEVER, the appropriate internal collaborators are often across other departments within the organization. To get around this we'll recommend that a Cross-Departmental "Team" be created for Channels that require Users that straddle several departments. This seems kludgy in that the SharePoint records created from this approach will force these artifacts to live outside of our department's records, so hoping that Microsoft can introduce a better workaround. Having a "guest" from another department is not uncommon .. not sure why that would be restricted within a channel.
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:
Angelo Mark Gopaul commented
This feature It very important for the and Built Environment. Different Organisations tend work on the same project, and would need access to documentation produced by others. The lack of this feature makes Teams (and SharePoint) pointless. many people already assume that the feature already exist and even think that the "private channel" feature was where that ability would come in. I honestly don't understand how Microsoft think you can only work on a project within an org alone.
Right now, Because of a lack of cross organisation/tenant abilities, We the Architectural Team are forcing the engineers, contractors to ignore their SharePoint project sites and use ours which is very limiting. Microsoft needs to sit down with architects, engineers and other stakeholders in the field to understand the user case. It being on the backlog, does not not bode well for the future of the must needed feature and we are forced to look for alternatives outside of Office 365 for future projects.
I would also say that this is a "must" feature for teams.
L. Günther commented
I understand the need, but please, Teams must stay simple!
If this is done wrong from the visualization, UI, clearness, and simplicity, it will confuse people being confronted with too many different channel types.
yes please - will prevent the proliferation of Teams
Ian Caldwell commented
+1 for anything which adds flexibility - but who owns this shared channel? and when can other people see the channel or not? I would not like to see 100's of shared channels in my Teams view..
When is it for?
That would be very helpful. Please implement