Jake Hedstrom
My feedback
-
1,042 votesJake Hedstrom
supported this idea
·
-
91 votesJake Hedstrom
supported this idea
·
-
24,698 votes
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.
~Alex
Jake Hedstrom
commented
Hmmmmmm... is that Slack I hear laughing?
If MSTeams is to win hearts of all those Slack fanboys out there, standard features like this are a must have. Microsoft will need to implement this feature (along with others) ASAP. I currently have 4 private Teams just for my IT department - it's cumbersome, irritating to work with, complicates workflow, and just plain doesn't make sense. Private channels is a must! I have a number of 'key stakeholders' who won't even consider a move to MSTeams until this feature is released.
Thanks for listening.
Jake Hedstrom
supported this idea
·
-
1,507 votes
This feature request is still in the works. I hope to have more updates soon. I’ll keep you posted.
-WarrenJake Hedstrom
supported this idea
·
-
1,203 votes
This feature is under review by the feature team. No new feedback at this time.
-WarrenJake Hedstrom
supported this idea
·
-
2,266 votes
This feature request is now actively being worked upon. As we move through the development process, I will post an new updates to this topic.
Please keep the votes and feedback coming in. Your feedback is shared with the feature team every month.
-Warren
Jake Hedstrom
supported this idea
·
-
960 votes
Hi — My apologies for the delay in updating this item. We rolled out a fix a year ago for a specific issue of status changing to away in Teams when you were still active on the device. We thought this had fixed the “incorrect status” issue. From comments below, it sounds like people are still seeing issues.
If you are still having issues, it would be super helpful if you can capture logs by typing Ctrl + Shift + Alt + 1, and send the file from your downloads folder along with device info and detailed repro steps to teamsml@microsoft.com.
Thanks all!
Jake Hedstrom
supported this idea
·
-
1,447 votes
The ability to remove a user from group chats (including meeting chats) is now available on desktop, and coming soon to mobile.
How it works: A user can go to any group chat of 3 or more people and navigate to the roster and by hovering over any user you will see the “X”. Clicking on this will show a confirmation dialog. Then the user must select remove to remove the user.
What does everyone see: Everyone in the chat will see the control message that says “User A removed User B from the chat”.
What does the removed user see: The removed user will still have access to the chat history but will no longer see new messages after the point of removal and will not be able to compose messages or make any changes to the chat.
Note: This setting is controlled by your tenant admin, so may or may not…
Jake Hedstrom
supported this idea
·
-
3,476 votes
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
Jake Hedstrom
supported this idea
·
-
4,667 votes
Thanks for following our suggestion to vote this up on SharePoint. It worked! SharePoint has confirmed that they have already started working on this and I’ll be getting an ETA from them after the holidays. -Suphatra
Jake Hedstrom
supported this idea
·
-
66 votesJake Hedstrom
supported this idea
·
-
47 votesJake Hedstrom
supported this idea
·
-
17 votesJake Hedstrom
supported this idea
·
-
5,041 votes
This feature request is still on in the backlog. No new updates available at this time.
-Warren
Jake Hedstrom
supported this idea
·
-
3,343 votes
This feature request is working its way through the backlog queue. No new details are available yet.
-Warren
Jake Hedstrom
supported this idea
·
-
10,326 votes
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.
~Alex
Jake Hedstrom
supported this idea
·
-
5,361 votes
The feature team is still reviewing, there is lots of discussion about this item and I hope to have a decision soon.
-Warren
Jake Hedstrom
supported this idea
·
-
7,080 votes
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
~Alex
Jake Hedstrom
supported this idea
·
-
12,300 votes
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.
~Alex
Jake Hedstrom
supported this idea
·
-
9,126 votes
We are still considering this feature for future releases, and will continue to update the status when it changes.
~Alex
Jake Hedstrom
supported this idea
·
Hey Suphatra - thanks for the update!
A specific question re this feature - will we be able to create a channel where we can define permissions to only a specific subset of Team members? Those permissions would then flow onto the channel folder in the SharePoint team site i.e. auto break inheritance and set the explicit permissions etc. etc.
Thanks.