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).
Thank you for the interest in meeting with research. All slots have been filled (in under 6 minutes).
This item remains on the backlog for now. Thanks!
yes, please! This will make my projects so much more effective.
Would be so great if we could give non-team members access to a specific channel. Right now we're opening in SharePoint and adding access to the folder, but you can't tell from within Teams that there is special permission. Please add this.
Cannot believe that this is put on the backlog when this should've been done in conjunction with the private channels feature. Defeats the purpose. This is a basic feature of Slack...
Great work adding the Private Channel Functionality. Now we need to be able to include our employees who do not need / want / should not have access to a Team; but we want their collaboration on a Channel. My example is our Leadership Group wants a team that we can use to collaborate on running and leading the company. Some confidential information is shared there. Now we want to include non-leadership members on specific channels to keep the number of Teams down and really leverage the power in this tool.
Excited that this is in the works! Let's move it up the list !!!!
Thanks for Private Channels 1.0! Now, this is the other half of the coin, the yin to the yang, the PB to the J... and hopefully is very high on the development list for what's next to deliver.
ED. Handeland commented
We definitely need this. Too many teams are made for projects where you have to include someone from another department. It is getting out of hand.
People stay away from Teams because all the different single-channel teams make it confusing.
Should be an option for both normal and private channels.
Ian Caldwell commented
+1 for this feature - flexibility is important. But, also good to know who has permission where - so this needs to be done carefully to avoid confusion i.e. a guest to one channel won't be able to see a file in another channel.
It is great that Private Channels is now done however we still can't use it as we have many external users that need to join in on some of these channels and currently that can't be done unless I add them to the team... something I obviously don't want to do as these external users will get a lot more access they shouldn't have.
Anyway great steps with regards to the private channel setup but I hope that this task is also done as it is 100% needed for external users
Just tested the Private Channels and for our environment they are not usable in the way we use Teams. If we could just grant access to external users (our clients) on a specific channel it would help us tremedously.
This would enable project teams to include their client, or other stakeholders, in a specific channel, without them having access to the other channels intended for the wider team. If we don't have this, then we'll end up with all other channels being private channels, which is not particularly helpful.
That would be very helpful. Please implement
This really would take Teams to the next level in terms of collaboration
This was my idea of a Private channel. Please develop this rapidly.
Would not shared channels cover this -> https://microsoftteams.uservoice.com/forums/555103-public/suggestions/32987917
Perhaps it might not.
This was our idea of Private Channels too. We have a department Team, but often engage consultants who only need access to the channel for their project.
Our workaround is making all channels private (staff-only), then adding staff + consultants to the project channels. Lots of manual permissioning though, and we can't privatise existing channels (esp General) - along with the limit of 30 private channels.
Back to creating a Team for each project I guess...
Stephen Bacchus commented
This was, to me, the actual request of "Private Channels." A channel that had it's own membership outside of the top level Team.
We need to be able to create a channel for a project, working with a client, and that client should only have access to what we deem is necessary. We should also be able to create a second channel, with a second client, and have that client only see what we want them to see.
Then, you would actually have "Private Channels." The feature request was obviously updated to reflect Microsoft's inability to implement.
On June 15, 2017, Suphatra, former Microsoft Employee, modified the feature request based on 5 channel types. This week we only got 1 of the 5 apparently...
Admins, can you give us an update for this feature?
Any ETA on when this feature will be available? There hasn't been an update for over a year.
Eelco Heuvelmans commented
This feature would really free up all the clutter that is now there because we have to create different teams to control which freelancer sees what.
Roberto Cabassi Bombardieri commented
We are still waining for the feature!