This is under review! If you have more ideas/feedback specifically on this item, please sign up for user testing here: https://1drv.ms/xs/s!AryUNzh1ogZzif8pDcOcx2pW45I87w
You can also tweet me at @skprufo if you have any questions.
I'm concerned that this will be confusing regardless of the implementation. Notification sync'ing between the two has potential, but conversation history? S4B has no concept of a channel, so what channel in Teams is the S4B history going to sync with? A private Teams chat with all members of the S4B chat? And visa-versa?
Too many apps with overlap now...maybe S4B should be retired. :-)
Hey guys, I’m rallying to get you more info. In the meantime, here’s the official response from our PR team:
“We are actively working on guest access. Thanks for your patience and stay tuned for more."
I share in your frustration and promise we are dedicated to delivering this feature, and I promise to continue to advocate for you. I appreciate your investment in us and Teams’ success.
If you have any questions, as always — just email or tweet.
skprufo Email: sparavimicrosoft.com
This is a must have. Today's teams span across company borders. It needs to be easy and seamless, no requirement for a MS account. +10K
Slack has pretty much set the bar, so Teams needs to _at least_ meet it. The area where Teams has a chance to beat-up on Slack is for all Office 365 users/companies due to the seamless integration...BUT Teams _must have_ feature parity. :-)
Hiya again folks.
I just wanted to write and let you know that I updated the idea to better reflect the vibrant discussion in the community about exactly what a private channel means. It looks like there are five definitions — shout out to user John Black who wrote it out so elegantly. I’ve included that description in the original idea.
We still have this item under review, and I’m personally interested in seeing if this request is further changed when we release guest access (coming super soon!) this summer. Stay tuned, stay cool, and as always, thanks for your support of Teams.
Yes, private channels are important. One use case is specific team members may be assigned to a client's project. There would be a channel built for this project but only those assigned to the project should be in the channel.