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.
@mike - how did you get private channels? less than 2 weeks ago MS said "later this year." Seems odd it would start rolling out in April, but I'll be thrilled if it is.
Done! I sincerely hope private channels bear no resemblance to what was proposed in that survey. Unless I misread it about 10 times, the only thing private is the chat. Everything else is accessable via Sharepoint or other sites (planner, etc)
So, is one of these five suitable for this scenario? We want a team for our purchasing department (all internal) and each channel is a vendor. We would invite the vendors to a particular channel. Insiders should see it all, external are totally sandboxed, cannot even see other channels (vendors).
Thanks for the update. I was hoping this was forthcoming with allowing access to outsiders. That is what we are really looking for here. So we could have a "Purchasing" team with a different channel for each vendor, and those outside vendors could be invited to the Team (with the outsider access feature being worked on) but restricted to just their channel. It just isn't feasible for us to create dozens of teams to make this work.
Allow us to put security at the channel level within Teams, so some info could be kept confidential by team members without having to create additional teams.
We are working on a better experience in Teams when a user is not connected to the internet. No timeline to share at this point, but we will keep you posted.
This feature request is still working its way through the backlog queue.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
Voted! Still needs a checkbox next to that "New Conversation" button saying "I agree I understand that I am creating a new conversation"
ANd then they should have to wait for a 6 digit code to be sent to their phone and entered into Teams before they can start a new conversation.
And a CAPTCHA for good measure. The annoying one with street signs.
So 2 more months of disconnected replies? :-(
Glad it is getting fixed, but so so so long.....
Thanks. This one still bites us several times a week. Maybe just get rid of the "start new conversation" box and make it a button that has to be pressed to start a new conversation. Just leave the boxes for replies.
The sooner the better. Too much stuff is being missed because someone replies as an orphaned conversation.
Please please please do this. Hide the "new conversation" box! Make it so you have to click something to show it or something. It is horrible the way it is now. Especially if when scrolling the message you want to reply to has its reply box obscured by the New Conversation box.
The feature team is still digging into the details of this item. I don’t have an update yet, but all your feedback and votes are shared with the feature team every month.
I’ll keep pushing this item and hope to have more details soon.
Sorry for the delay on an update on this one! I’m hunting down the status for you and will update once I have it.
Also, if you are interested in participating in testing or surveys for this, just tweet me at @skprufo.
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.
Full multi-tenant, multi-user support will be added after fast tenant switching.
Agreed. And to add to this. we have some files with conversations hundreds of messages long. It takes FOREVER to scroll up to get to the file. There needs to be a fast way to get to the file in these long conversations, so maybe this pagination idea is the way.
Adding any emoji as a reaction remains under review.
I am marking this as partially done to let you know a new reactions bar with Like, Heart, Laugh, Surprised, Sad, and Angry has begun rolling out to all users.
This item is still on the backlog.
Same. Getting this on my desktop (windows 10) app. Not in the browser though.
I’m switching the status to Partially Done.
The request for a Preview Team is still in the works. No new information is available at this time.
Team Discoverability is still being worked upon, no details are available at this time. If you support this idea please navigate over to the main topic and vote for it! https://microsoftteams.uservoice.com/forums/555103/
Change Prompt: this has been completed
This request is still working its way through the backlog. Nothing additional to report yet.
To clarify how it breaks, if you unsave an item from the bottom of the list it works fine. if you unsave from the middle or top, everything below it gets off one row. It is like it remembers the count of items. So if you unsave item #6 by clicking on the bookmark in the conversation side, it removed the bookmark, but it does not remove it from the left side list.
When i click on item #7 in that list, it shows me the body of item number 8, and 8 shows 9.
Unsaving from the list vs the conversation view doesn't help. Same problem.
I also noticed that the avatar from the item below moves up, so the avatar knows the item above was removed, but teams doesn't remove the snippet of the conversation.
I can repro this on the web version in Chrome too.
Unfortunately we hit some snags and this has moved back to “working on it”. The team is working to make some corrections and I hope to have a release date in the near future. I’ll keep you posted with what I hear.
Is this done, or was it killed? According to https://blogs.technet.microsoft.com/skywriter/2018/04/19/office-365-planned-service-changes-april-2018-updates/ this was moved to an archive, but if it is available, I am unaware.