We create our Teams as private by default since they are about the clients we work with. We are okay with everyone at the company knowing that these Teams exist, but we don't want them to be able to join them without permission.

The problem we're having is that people keeping asking 'does a Team exist for client X?' and there is no easy way to answer that question.

We'd like a way to search for private teams so that folks can request to join them.

Currently there are public teams that can have channels below them, but for contacts, you can only specify someone as a Favorite. It only makes sense to be able to categorize contacts into groups (like all other chat tools). Even Skype for Business has this functionality.

Is it possible to make an assignment per channel. Instead of make an assignment on the General channel.
We want to use a team as class. The channels are the subjects and in each "subject channel" we want to make an seperate subject assignment

I am not able to remove previously added chat-members. a workarround would be starting a new chat with the other members but then i will loose the chat-history. any other Ideas ?

Request #1: Currently, as shown in that attachment, permissions can only be changed for the general channel. Allow these settings to be changed for each channel.

Request #2: Add an addition option where "Only owners can start a new conversation, but anyone can reply". Example use: Only a manager could post an announcement, but everyone could reply to that comment.

Make a virtual user grouping that can be managed by conversation group admin.

For example, all the release teams in the company are on a single Teams conversation group. If a person wants to address all the scrum masters in their message, there is no way to do it currently except to @tag each one of them.

My suggestion is to have a virtual grouping like @ScrumMasters. The group name and the members of that group should be manageable by the admin for the whole group.

I experienced this error several times now. I created a new team and tried to upload a team picture. No matter which size or file type (png, jpg), I always get the message "Problem uploading your picture. Please try again later."
Then I created another team and the picture upload worked without any problem. After waiting approx. 5 minutes, uploading worked on the first team.

Why is that? Do we just have to wait some time before we add a team picture? Then some notification would ne nice when creating a new team.

Great work by the way! :-)

Enable team members to configure T-bot's responses for their specific team based on keywords. For example if I ask T-bot about "PTO", it could respond back with the company PTO policy and a link to the PTO request form. This is a feature available today in Slack that is heavily used by my organization.

Our HR unit is using Channels with threads that is to be printed for handout purposes (procedures) They are suggesting the ability to print a thread would be very helpful as oppose to having to screenshot the whole page.

Add an option to "Mark all as read" at the team level to mark all channel of the team as read.

This would allow to clear new message that we don't want to read.

Add the ability to hide the General channel (not rename/delete, as has already been declined)

Right now the Activity tab only shows conversation activity. This tab should show ALL activity across ALL Teams activity: Files, Planner, Wiki, etc.

I can delete inside of every channel conversation tab except the General channel. This General channel conversation is precisely, and unfortunately, where inappropriate content will find it's way under Murphy's Law...

Would be nice to have an Action in Microsoft Flow to Create a Team. Currently only the 'create channel' is available.

Ability to have sub-teams within a larger team chat structure. These sub-teams should receive notifications on issues that pertain to them while the rest of the team can see the messages but should not be notified.

As an example, we have two teams(data management and tech support) that coordinate work together in a channel (support services team). When messages need to alert TS or DM but not both, there is no way to use @data management to notify only the relevant part of the team. We have to use @support services to get the attention of both.