Private channel access by non Team member
The new private channel functionality doesn’t solve the basic private channels need. We have tons of needs for private channels where we want to invite someone to a channel but not give them access to the rest of the team. One example: BD proposal where you need a non-BD team member to be involved. They can’t have access to other BD files, just this one channel for this one proposal. Since they can’t have access to other BD files they aren’t part of the team, but if they aren’t part of the team they can’t get access to the channel. The relationship between members of a team and members of a channel needs to be reworked. Need to be able to invite anyone to a channel regardless of them being a member of the team or not. Current implementation is the exact opposite of what I was hoping for. Current setup is a mechanism to exclude some team members on a per channel basis; whereas, what is needed is the ability to include non team members on a per channel basis.
Tracy Duhamel commented
I have come across, let alone outside users, I can't add anyone from my own network if they aren't part of the given team to a private channel. Has there been any update on this? It is definitely an very necessary feature.
I agree completely. Only solution we've found is to keep creating additional teams with limited members. Often we have need to engage with other colleagues on projects but we don't want to add them to an entire team, just a particular channel.
Daniel Rüffer commented
The permission structure of teams is currently not convenient:
- Public channels can be seen by everyone, including guests.
- So you need to use private channels for the team's content if guest should not see everything
- On top, membership control of private channels is cumbersome and has to be managed on a per-channel basis
Chris Hutchinson commented
I echo the request and all the comments. The only alternative currently is to create a number of similar teams with different member lists becoming a bit messy and confusing. We wanted to move to MS Teams to be better organized, leading to not only more collaboration but better collaboration. Lack of this feature will make it difficult for me to get my company on board with MS Teams.
We also need this. The suggested feature would be great but instead of non-members not having access to files and folders, I would like a setting to control whether non-members have access to files and folders.
This feature is actually the one I'd rather have instead of the initial Private Channel functionality.
It would greatly increase usability and productivity within most of the Teams I see both in my org and those who I am consulting with.
Hosam Alzahal commented
it is extremely needed feature. especially if the non-team member is actually a domain member
- Channel only members: to enable collaboration with people outside the team in a specific channel, without granting them access to the team itself. https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31374577
Totally agree!!! Please add this functionality, otherwise it’s useless for the scenario of my company, since we want to add guest user (external user) to only one private channel, not to first add them to the whole team and then add them to the private channel. The external user shouldn’t access to the rest of the team content rather than only content in the private channel.
So very true.
It's not only about excluding within a team, but also on including (guest-account or member from another team in the organization) in a private channel when not member of the whole team.
same here. We need to ability to add a company user to a private channel, even if he's not a member of that Team
Alex Carlock commented
As we're looking at Private Channels, we're realizing the same thing. We want to have one Team per client/prospect with a channel for each Pursuit or project. We don't want the client to see the pursuits, but we want to grant them access to specific project channels. We know we can create a private team and a public team, but that leads to Team sprawl with at least two per client. If we could invite a person (internal or external) to a Channel directly, that would solve the issue for us. Since Private Channels use their own SharePoint Site, this seems like something that could be done.