We acknowledge the customer demand for Private Channels and have been hard at work on it. Private Channels is currently in preview with a select group of customers. We expect to release the feature to the public later this Fall, and will update here when we are starting to roll out to all customers. We appreciate all the feedback you have provided to us on this forum and thank you for your patience.
90% of what i need is the ability to create a channel in a team and restrict who can access&see that channel via its members. the rest can come later..
for now without the ability to create private channels we end up creating hundred of different teams instead of a few consolidate and healthy sized teams.
if we had private channels we could reduce the fragmentation of teams greatly and finally create some healthy sized organizational teams.
Privacy and governance will be quite important for it to actually be used. if the owner or higher level admin would have access to a private channel content, its likely to hinder adoption as users cannot be sure the conversations stay private.
Converting channels from public <> private is likely going to be a common occurrence and a needed feature
Private channels will allow teams to shift from being mostly "activity based" (the project, the event, the customer).. towards org based (the sales team, the devops group,...) and have private channels for their activities that doesnt need everyone eyes. as such membership mamagement and making this easy to understand is important. do all participants in the private chan also become members of the greater team and inherits all permissions from there, or just the private channel... things like this needs careful considerations for how its positioned and used...
its been February 09, 2017 when "this is on it way".
so far this is the biggest reason why teams is not being adopted and slack is.
This feature request is still on in the backlog. No new updates available at this time.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
We are still considering this feature for future releases, and will continue to update the status when it changes.
We know many of you are waiting for a Teams client for Linux, and we’re pleased to confirm we’re actively working on it. Stay tuned for more information.
This feature item is still in the works. We will keep you posted as we have new info from the feature team.
this would be extremely useful. until we either get a tenant based store for the apps, sideloading is the only way we can work with testing bots. this unfortunately turns on every single app in the store so the only option we have to drop all MS team bots development and focus on other products like slack.
The team is working on #2 (and has been for awhile). We will update as soon as we have more news.
without this we cannot really proceed with teams