Channel only members & guests
Channel only members enable collaboration with people outside the team in a specific channel, without granting them access to the team itself. The channel member could be someone in your organization, or external to your organization (guest).
Scott Allen commented
We started using Teams to have online meetings with external clients, which works in calendar invites. But after a meeting, if we have recorded a video and want to share with others in an external organization there is zero option to do so? makes no sense in a collaborative app like Teams. Im not even sure I can share it with the original attendees outside my Org?
This is a necessary feature to manage channels efficiently when needing to give access to specific channels
I was really excited about private channels until I discovered that you can't add external guests without adding them to the whole team first and give them access to everything which defeats the purpose in my use case.
Michelle Gable commented
Agreed. I had to create an entirely separate team simply because of this.
Please bring this off of the backlog and prioritize working on it -- this is a critical component for holding meetings with attendees outside the group, also meetings in a Teams channel, sharing OneNote meeting minutes with a larger group of attendees, it can also help with collaborative Planner plans.
Easy argument is that Slack has it for guests restricted to individual channels that don't see anything else in the team. Slack is the best solution on the market and Teams needs to catch up.
Andreas Huber commented
This is would be a great new feature. Actually we were waiting for private team channels for a long time, but the current solutions is basically useless for us. We want internal and external persons to be part of specific team channels, but not part of the whole team. Surely an option is to make each and every channel private and control channel access in that manner, but that is for sure not a practicable and user friendly solution. I think for many companies, the ability to add persons to a specific channel, without having them in the team itself, leads to a comprehensive and useful private channel feature. The current solutions, unfortunately, is not one.
Stephen Bacchus commented
Please fast track this feature and the remaining features currently listed in your "Private Channels" update if you really want Teams to be a powerhouse collaborative tool.
Why this is on the backlog makes no sense.
Andrew Berry commented
Handy feature that would be very useful.
Chad Smith commented
I really wanted the recently implemented Private Channels to work for us, but as it turns out it is useless.
We need the workflow to be in reverse, as is noted in this request. The ability for all our org staff to freely access all public channels, but then invite a customer (external) user to a particular channel.
This gives us internal freedom, while still restricting external access.
Please move this into a development state.
quiet an vital feature needed.
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:
This is a very important feature if you want to see Teams implemented and replace the use of other collaboration platforms.
Making someone external part of a specific discussion in a project doesn’t automatically mean they’re part of every discussion in that project, or access other resources than the specific discussion itself.
Disappointed that Private channels, are not the kind of private that would have been more useful to our organization. We create one team per project. We have external subcontractors and clients that we would love to add so we can move away once and for all from email tyranny, but alas... not while they can reach sensitive data on the team.
Why it moved to the backlog is beyond me.
Chris Hartnell commented
My heart sank when I saw that it was not possible to have channel only access within a team for external guest users. I am trying to set up a Project Management tool which will have all documentation/comms for around 100 projects, some of them will have specialist external contractors who CANNOT have access to other projects. The idea was to have one channel per project (and I would then use site wide columns/site content created in Sharepoint to set up and see rich metadata across the document library (each project sharing the same root doc library) - another Teams glitch necessitating using SharePoint doc library features to make it work). I can live with that but it looks not being able to restrict external users from nosing around sensitive documents in other projects means Teams is a non starter. This is a fundamental security issue. Setting up a new Team for each project? I don't think so. Incredibly frustrating. Please tell me I've got this wrong.
Thomas Kuegerl commented
We need also any type of communication between Teams and Externals inside an existing team. This is vital for any implementation on our side.
"Can we use Slack or something to be able to contact you faster than email?"
"We use Office 365, and can probably set you up with some sort of guest access for you to be able to chat with us in Teams."
<<< Investigate. Find that adding guests to Team exposes the General channel and its files. >>>
"Nevermind. Yes, let's use Slack."
Ondrej Horky commented
We want to cooperate with our suppliers! We need add them to our internal team without permissions to see other channels = files, conversations, etc.. This function is very important!
Rhea James commented
This is a vital tool for being able to effectively abide to GDPR, private channels are locked within my organisation as is doesn't really help with work continuity with staffing changes so isn't really an option, but you may want someone from another department to be able to access one channel of work and communicate in the channel on that work but other channels are highly confidential and they aren't permitted to view
Once upon a time we had Folders.
Folders could have inherited permissions or unique permissions. Allowing access for users in a variety of different ways.
Now we have Channels - you can access them, but only if you're in the Team
Look back your at roots Microsoft. This needs fixing.