Support for Private Channels
Looking for the ability to create a channel that only channel members can see. Private channels are available in slack. There is an admin for private channels who is the creator, and they are the ones who add/remove users.
Five types of public/privacy that is being asked for by users:
- Public-Open (visible anywhere including outside the org and anyone can join)
- Public-Invitation (visible anywhere including outside the org, must be invited)
- Company-Open (only visible inside the org and anyone in the org can join; outside the org must be invited)
- Company-Invitation (only visible inside the org, must be invited)
- Secret (invisible to everyone except existing members, must be invited)
Hi Everyone – thank you for your patience. As was commented by someone below, Suphatra is no longer at Microsoft, but rest assured we are working on this feature.
Mike R commented
The only feature stopping us from switching
We have users who would like to have a select set of users within the larger team. This feature has to be implemented.
I was just asked today about this, very much needed in our company unless we want to create multiple teams for the one project, which is not ideal.
Charlie Benbow commented
Private teams is not sufficient. We also need to be able to control access down to channels as well. Please provide an ETA for this feature.
Any ETA on this? I got 1100 slack users which we want to adopt teams because of our recently O365 engagement, however without controlling access to channels they will not adopt.
Really need this feature added for collaboration on sensitive items.
Please let us know if this feature will likely be implemented in 2018 or not!
Louis Esmeijer commented
Indeed, please, fix this! Or give us an update of the ETA! It's so important....
Lindsay Brenner commented
Is there any timeline that can be shared instead of the vague status updates? Many of us have to make business decisions based on this so a best guess would be helpful - even if it is something like "likely not within 2018"
John Kostenbader commented
I'll add my voice as well. Adding the guest feature was a giant leap forward but guest access without some restriction to channels is a problem for us. I'd really like an update on this release as well
Jamey Steinmann commented
Any update on this feature? It's a critical feature to drive adoption of Teams within our org
Check the previous updates (this is from November... 2017):
WORKING ON IT · ADMIN
Suphatra (Microsoft Teams, Microsoft Teams) responded · November 30, 2017
Its been a while since my last update, so wanted to check in and let you know that this is well under way. We’re aiming for early next calendar year (2018) if development and testing go well. I’ll ping you again with a more exact ETA after the new year.
Meanwhile, feel free to ping me on Twitter at @skprufo if you have any questions!
Ron Bouma commented
This is a feature that has been promised for a long time now. It’s about time that it’s being released, SharePoint already has this feature, so why does it take such a long time for this feature to become available in Teams?
years are going by and you have not done it...
What is going inside Microsoft company
Why is this so hard? It's been a showstopper for so long.
Any date release for it
we can not implement team until we can select who can join a channel
Almost a year and counting. At some point you need to provide some information about what the actual ETA is or what the hold up is.
Hello from a dutch company.
We are very excited when this feature will be released.
Is there already some more information on when this is coming?
Zoltán Lehóczky commented
Just an FYI for those thinking this means you can't configure access control: you can, but unlike with Slack where you do this per channel, here you do this per team (so, for a collection of channels).
Russell Myers commented
This was a Slack feature almost from day1. If you want wide-spread adoption of Teams, you need to put more resources in to making this feature available soon.... It's very disappointing to see that it's been on the roadmap for some time and we're still waiting whilst other 'features' that have little support or basis for development in terms of requests from users are being prioritised.
Do you have an ETA?
It's an essential, not nice to have!