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!
Thomas Hebes commented
Adding my myself to the people who need these feature. In a normal project life there are some external partners which needs some access to colaborate. Right now we are creating everytime a new Team just for external colaboration. So the information is now stored in two different teams. Not very helpfull.
Adding my urgent vote to please add this feature. At my company, people LOVE the chat feature where you can freely invite anyone and quickly arrange a quick text or phone call meetup. The problem is that there are very limited organization methods in MS Teams for managing these chats that can number in the dozens to hundreds over time. Some chats are quick and shortlived. Others can carry on extended conversations that yield very useful discussions that we'd like to 'memorialize' by being part of a subject teams channel. So far this can't be done per another suggestion I saw here.
What would then be really useful is to be able to spontaneously start that chat WITHIN the topical Teams channel and select who should be able to see and participate in this channel chat. It could be all the team members of this channel, a select subset, AND allow guests that could be anyone in the company or external users. Allow the chat owner to set scope of view for the chat members to just the chat, chat plus to encompassing channel, chat plus selected channels in the team, etc.
This will preserve the spontaneity and freedom of the chat service, from within the organizing framework of the Teams channels. PLEASE!?
Adding to the list of people who need this. The issue is that you have to create a new team for every company you want to communicate with. This is extremely inefficient as you end up with hundreds of teams for each external company rather than just one team and then multiple sub-channels for each company. Please fix this ASAP. Been on the backlog since 2017.
Ian P. commented
Echoing the feedback of others - needing to grant Team access to a user so they can collaborate on a topic quickly & easily is just silly...and potential security risk if they just need chat access
Natalia Fuentes commented
This is needed yesterday!!! In higher ed we need to be able to add student workers to a channel in our staff team. They should no see all other channels and we should not need a duplicative second team just to talk to our workers.
@Heinrich Ulbricht That user feedback thread was the first feedback thread for creation of Private Channels, this is sort of a contingency of that thread with feature improvements.
Osman Sharif commented
Not having this feature greatly limits the use of private channels
Definitely need this sooner rather than later. I was forced to give a user access to a whole Team and all its channels. This is a security concern with the user having access to resources they shouldn't have. Such permission issue should not be allowed on Teams and leaves organizations without options to protect data. With the number of votes it is surprising this critical feature is on the backlog. It is hard to understand how other features in development such as Teams dynamic view, video filters, chat bubbles, are more important than this.
Not having this feature severely limits the use of Teams. We switched from slack and because of this one feature, we are considering going back.
I feel like this functionality is ESSENTIAL when collaborating with people external to the organisation (which we do on a regular basis). Yes, you can add external guests to a private channel but they can still see the public channels. Being able to add guests to one channel only would solve a lot of internal issues!
There is definitely a need to invite guests to a specific channel. The only other alternative is to create a new team for that channel. This is the kind of duplication and inefficiency we are trying to avoid by including Teams in our organisation.
This would be very useful in my organisation, I hope MS can add this feature soon.
I also need the possibility to invite a different Person, into one Channel, who is not member of the Team. The Team has got more than 7 Channels (permanent). In my opinion this is a very important - missing - feature. It would be a pleasure to use it soon. :-) Thank you Andreas
John Taylor commented
Can you advise when the feature to add a person ONLY to a channel (and not a team) will be realised? I have a need whereby I need to grant access for a user to a channel but I do not want them to have cross-visibility to the rest of the Team. Please advise when this feature will be available or if it is even being worked upon? Thank you, John
Mikael Holmqvist commented
What is the status of this feature? It's now been 6 months sins the last Admin post @Alex. We really need this functionality.
I coordinate with over a dozen different external partners, and I want a single team where I can create a dedicated channel for each partner, without those partners (guests) having cross-channel visibility. We currently use Slack and they've nailed this feature. I'm being asked to evaluate Teams as a substitute to Slack, but until we get this feature in Teams, it's difficult to recommend making the switch.
I need to add an external consult and that's impossible unless he becomes member of our company wide Team.
Aslam GC commented
This is a very important feature. Especially as we use channels to gather conversation around particular projects. In a large or matrix structured organization, a project will almost certainly include contributors from outside your "team". Without the ability to create a channel that has specified members who are outside of the "team", we find ourselves without a good solution for how to enable conversation for that project. In some cases, we have created an ad-hoc user chat with those members. This is not ideal because one cannot organize/delete files posted to an ad-hoc chat. In other cases, we have ended up using the chat for the weekly project check-in call as our discussion forum. This is also not ideal and really is using the check-in call chat for much more than it was intended for. Thus we really need the ability to add members/guests to a specific channel that gives them access to all aspects of that channel but not to anything else within the team where that channel sits.
I note that this is a problem that only exists with Teams because of the "team" construct that this program uses which competitors like Slack do not. With Slack you can easily create a project channel with a mix of members to gather discussion around a particular project, and there are no issues with doing this. While I see lots of value in the "team" construct that Teams uses, this use case is an example where having that construct necessitates other features to allow for us to break the construct when the business requirements demand it.
Shared Channels have been announced... coming soon
Adding input from a Legal team within a company. We NEED this function. We often collaborate on projects outside of our legal function but within the larger org. We discuss confidential information on our Legal Team site and cannot add members outside of our core team. Even within our core team there are projects that are sensitive in nature and only a few members of the team should have access to. Due to this need for confidentiality, our collaborative projects are parsed out between Team sites and back end SharePoint sites opposed to being centrally located in our Legal team site. Our core team members must navigate to several locations on an average workday causing confusion and reducing efficiency. Essentially an entirely new SP site is being created to house 1 project for a short time, then it is abandoned. If all the members of this Team site were to leave, the historical knowledge of this project would be lost. Having the ability to add a "guest" to a channel (even if the person is within the larger org), would mean that channel would live on in one location for posterity, projects would be more easily accessed by core team members, and overall organization would be improved.