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.
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
Jagjeet Singh commented
A pretty important feature for a company who provide supports to other companies.
Another idea is for each Team to have an external-to-the-team Channel as a type of 'message board' that all other members/teams of the organisation can post to, with the addition of subchannels that can be created to allow better targetting of such posts to members of the target team or even subgroups of members of the target team. Members of ths target team can then subscribe to/make themselves members of any of their Teams' sub channels and so handle the commuications arriving in that sub channel. The concept is that a Team has an organisation-facing 'service area', that others can leave messages or posts or queries to e.g. specially created sub channels such as Suggestion box, Likes/Praise, technical issues, priority issues, complaints and so on. This channel would have its own Wiki to include e.g. instructions on how to work with the service area best, how to construct and where to leave your messages, SLAs etc. It also makes sense for sub channels to have their own wikis as well
Frank Wang commented
Even within the same organization, shared channels between teams is also a critical yet missing feature. Without this, your only option is to build huge teams that include everyone from multiple teams, but then everyone will have visibility of all team content...
this is all really important and we need this asap! please fix this microsoft. i say 'fix' because teams is 'broken' without these collaboration features...