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.
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.
We are working on this!
Unfortunately due to re-prioritization this item has slipped back onto the “backlog” for the time being.
I hope to see it move back into “working on it” soon and will continue to engage the feature team with your feedback.
Hey guys, thanks for the feedback – we hear you loud and clear. After talking this over with the Engineering team, I confirmed this will remain on the backlog and we are actively considering how to accelerate.
Tweet me if you have any questions! @skprufo
This feature item is still in the works. Unfortunately I don’t have any additional details to share. I will keep you posted as I hear 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.
Of the two items in this request, #1 is complete and available.
- is still in the works.
This is part of the convergence roadmap – https://skypeandteams.blob.core.windows.net/artefacts/Skype%20for%20Business%20to%20Teams%20Capabilities%20Roadmap.pdf
As more details become available for item #2 I will share them with you.
without this we cannot really proceed with teams