Jim Scott
My feedback
-
862 votes
As mentioned in the prior status, the channel limit was raised from 100 to 200.
In the near future a retention limit will be set so you can still go back and reinstate a channel you had deleted. Once the retention period has expired then the channel will get a hard delete which will free up the space and no longer count toward the 200 channel limit.
This will help with some of the issues you have voiced in the comments below.
But I understand many of you wish the limit to be further increased. I will continue to provide your votes and comments to the feature team.-Warren
An error occurred while saving the comment An error occurred while saving the comment Jim Scott
commented
We moved all our communication from Slack to Teams and at first made the mistake of creating Teams for each part of our organization. That required everyone to be part of every team that we wanted to have cross-organizational communication with.
We just recently switched to creating an organizational team and moved many of our teams used for cross-org communication to the one team and I am a bit worried that we will quickly push that upper limit OR people will start moving some of their channels into other teams which puts us back at the same point. Is there a technical reason that the limit is only set to 200 channels?
Jim Scott
supported this idea
·
-
3,187 votes
The team has not made a decision on whether to move forward with this feature. We will update when we have new status to share.
An error occurred while saving the comment Jim Scott
commented
I think the problem with decisions that MS is making with features is applying the behavior to everyone. Some may not like chat and teams to be on the same tab. But many do so why not make this a preference setting and satisfy everyone?
Jim Scott
supported this idea
·
-
5,216 votes
As part of our commitment to being customer driven, we’d love your input on top features that will improve your satisfaction with teams and channels navigation, and help you be more productive in Teams. Please access the survey here: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7hW7rKdVrVInUSM809cvrtUNFhLRVNJVVhaUFI0WEJHVTA4MlpGWVZUSS4u
Thanks for your feedback!
An error occurred while saving the comment Jim Scott
commented
Any decisions on this? Last update was March 12, 2019 that needs feedback. Now we need feedback ;-)
Jim Scott
supported this idea
·
-
Reply to specific message in chat on desktop app
-
reply.png 26 KB -
reply.png 26 KB -
Respond_to_specific_Chat.PNG 53 KB -
Teams_message_idea.docx 174 KB -
Teams_2020-05-30_01-13-29.jpg 182 KB -
Whatsapp Screenshot.jpg 255 KB -
Teams_Reply_To_Message.png 3 KB -
whatsApp.jpg 31 KB -
CHAT.jpg 192 KB -
Team Chat.JPG 80 KB -
Capture.PNG 35 KB -
pandraus06-11-004.jpg 118 KB -
reply.PNG 82 KB
41,729 votesThank you for your continued feedback. As many people have pointed out, this is available on mobile today. Support for replying to a specific message is on the backlog for desktop. I’ll let you know when we have progress to share. Thanks.
An error occurred while saving the comment Jim Scott
commented
This would be a nice feature to have for sure in the desktop client.
Jim Scott
supported this idea
·
-
-
58 votes4 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Jim Scott
commented
On the following page it claims they are working on this.
https://docs.microsoft.com/en-us/microsoftteams/private-channels
What you need to know about private channels
Currently, private channels support connectors and tabs (except Stream, Planner, and Forms). We're working on full apps support for private channels, including messaging extensions and bots.An error occurred while saving the comment Jim Scott
commented
Definitely need this feature. We just built a chat bot to interact with one of our services only to find that the only place we can add our chat bot is public, group chat and personal? So every place except private channels? The most important channels we have that require the bot of course are those private channels.
Jim Scott
supported this idea
·
-
44 votesJim Scott
supported this idea
·
-
757 votesJim Scott
supported this idea
·
An error occurred while saving the comment Jim Scott
commented
Uh, Oh! I hit the maximum number of private channels limit (30) and thought that I would go and delete the channel to free up a few slots only to find that when you delete a channel it is not permanently deleted and must still be considered in the number of channels. That means that once you have created either 200 standard channels or 30 private channels you will not be able to create any more even though you have deleted them?
-
396 votes
Updating the status to “Try this instead” and have added the clarification that after 30 days the name is once again available.
The reason for this decision was that Channels can be restored 30 days after being deleted. During this time, we intentionally don’t support creating a channel with the same name. After the 30 days, the name is available.
You can workaround this by restoring a deleted channel, renaming it, and then deleting the channel again. The previous name is then available for use.
This workaround has already been mentioned in the comments and if an immediate reuse of a Channel Name is required, this is the recommended solution.
-WarrenJim Scott
supported this idea
·
An error occurred while saving the comment Jim Scott
commented
How about allowing an administrator the ability to permanently delete the conflicting channel that is sitting in deleted queue instead of having to wait for 30 days? This would fix all sorts of additional issues like cannot have more than 30 private channels which includes those that have been deleted in the last 30 days. Or cannot exceed 200 standard channels which again includes those that have been deleted in the last 30 days.
I get the benefit of not really deleting a channel and sending it to a deleted queue that can be undone, however give someone the ability to permanently delete the channel from the deleted queue without having to wait 30 days and you solve this issue.
An error occurred while saving the comment Jim Scott
commented
Great to see there is a work around, how about adding something to the channel name when someone deletes a channel to help make it unique and unlikely to clash with the previously deleted channel name?
Use Case: I have a channel named get-help and I decide to delete it. Teams deletes and renames it get-help-DELETED.
-
454 votes
An error occurred while saving the comment Jim Scott
commented
How about allowing an administrator the ability to permanently delete the conflicting channel that is sitting in deleted queue instead of having to wait for 30 days? This would fix all sorts of additional issues like cannot have more than 30 private channels which includes those that have been deleted in the last 30 days. Or cannot exceed 200 standard channels which again includes those that have been deleted in the last 30 days.
I get the benefit of not really deleting a channel and sending it to a deleted queue that can be undone, however give someone the ability to permanently delete the channel from the deleted queue without having to wait 30 days and you solve this issue.
Jim Scott
supported this idea
·
An error occurred while saving the comment Jim Scott
commented
Same issue with private channels. You cannot have more than 30 private channels and even if you delete the private channel it does not free up a private channel. You have to re-purpose an existing channel that has been deleted!
-
47 votesJim Scott
supported this idea
·
-
8 votesJim Scott
supported this idea
·
-
1,151 votes
An error occurred while saving the comment Jim Scott
commented
Yikes, this gets even worse. I decided to delete a few private channels to free up the number of private channels in use and found that the channels are actually put into a deleted queue that can be restored and counted still towards your private channel count and no way to permanently delete the private channel?
Only solution I have now is to restore one of those private channels I deleted, rename it to something relevant, clear out any old material and invite people ?
Here is another request we need to support
An error occurred while saving the comment Jim Scott
commented
Further confirmed by searching for the error.
https://docs.microsoft.com/en-us/MicrosoftTeams/private-channels
"Each team can have a maximum of 30 private channels and each private channel can have a maximum of 250 members. The 30 private channel limit is in addition to the 200 standard channel limit per team."
An error occurred while saving the comment Jim Scott
commented
I just hit this limit today and I am freaking out. I made everyone in our organization move to Teams and turned down Slack. When everyone finds out that no more private channels can be created they are going to slaughter me!
Please help save my life ;-) Increase the number of allowed private channels, please!
Jim Scott
shared this idea
·
-
22 votesJim Scott
supported this idea
·
-
631 votes
Admin controlled contact groups for Teams are available via the O365 Global Address List (GAL). Please see documentation here: https://docs.microsoft.com/exchange/address-books/address-lists/create-global-address-list.
An error occurred while saving the comment Jim Scott
commented
Would love to see functionality added to contact groups for sure. I created a contact group in teams but I cannot for the life of me figure out any place I can actually refer to the group?
Jim Scott
supported this idea
·
-
269 votesJim Scott
supported this idea
·
An error occurred while saving the comment Jim Scott
commented
I did not see this request when I opened my new one : https://microsoftteams.uservoice.com/forums/555103-public/suggestions/39400009-add-ability-to-invite-team-or-contact-group-to-new
-
13 votes
An error occurred while saving the comment Jim Scott
commented
This would be great and would offer the most flexibility needed and would satisfy most everyones request for additional permission functionality.
As a team or channel owner, I would like to assign permissions at the individual level, so that I can provide more granular control for individuals without having to give them everything assigned to the owner role or having to enable permissions that I do not really want everyone else to have at the member level.
Use Case: I want to create a private channel and do not want to give everyone the ability to invite new members to the channel. Today I have to make them all owners to get that additional behavior which then gives them additional rights that I would not prefer them to have. You could of course add a permission for that right at the member level and allow me to give everyone permissions to add new members but I would also like to decide that maybe just a handful of people should be allowed to perform that right.
Jim Scott
supported this idea
·
-
381 votes
We have added a lot of new settings changes since the last update. You can see the updated list here https://support.microsoft.com/office/team-owner-member-and-guest-capabilities-in-teams-d03fdf5b-1a6e-48e4-8e07-b13e1350ec7b.
We would like your feedback on any gaps or additional settings that you feel are missing. Please let us know, the team would love to hear from you!
An error occurred while saving the comment Jim Scott
commented
Agreed, need more flexibility in assigning permissions other than just roles.
Jim Scott
supported this idea
·
-
1 voteJim Scott
shared this idea
·
-
9 votes
An error occurred while saving the comment Jim Scott
commented
This appears to be a supported feature?
-
18,156 votes
This item remains on the backlog.
An error occurred while saving the comment Jim Scott
commented
We are going to need this with the adoption of a single team for most cross team communication so we can archive channels when no longer needed and yet remain searchable for content stored in the archived channel. If you allow the channel to be archived then please do not count it towards the limit of the number of channels supported.
Jim Scott
supported this idea
·
Any update to this, last update was Aug 2018