How can we make Microsoft Teams better?

Support for Private Channels

Looking for the ability to create a channel that only channel members can see. Private channels are available in slack. There is an admin for private channels who is the creator, and they are the ones who add/remove users.

Five types of public/privacy that is being asked for by users:

- Public-Open (visible anywhere including outside the org and anyone can join)
- Public-Invitation (visible anywhere including outside the org, must be invited)
- Company-Open (only visible inside the org and anyone in the org can join; outside the org must be invited)
- Company-Invitation (only visible inside the org, must be invited)
- Secret (invisible to everyone except existing members, must be invited)

10,195 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Angela Sze shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    828 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Henrik Nordtorp commented  ·   ·  Flag as inappropriate

        Surprisingly few people voting in here! This is crucial to making Teams an enterprise solution and ensure only selected set of people has access to content

      • Howard commented  ·   ·  Flag as inappropriate

        Awesome, thanks Suphatra! I'm looking forward to this feature. Also, thank you for providing consistent updates on this product.

      • Beau P commented  ·   ·  Flag as inappropriate

        I noticed now you can make "Teams" public or private, but you can't make "Channels" public or private. Is this supposed to be this way or is public/private channels still on its way?

      • Haley Engle commented  ·   ·  Flag as inappropriate

        Within a team be able to edit permissions to each channel for the team members that channel apply to.

      • Giulio Vannini commented  ·   ·  Flag as inappropriate

        Actually enabling chats with end-to-end encryption using RMS digital rights would give TEAMS a very strong competitive advantage for positioning on confidential executive chats.
        Chats that nobody can read other than the addressses would be a powerful compliance feature

      • jeffwllms commented  ·   ·  Flag as inappropriate

        Really hope this come. Having a bunch of teams with just a general channel is annoying. Setting this up now the way we want it knowing this is in the works. So far we actually have found it isn't so important for teams to not be able to see the project groups they are not specifically on. We actually just received benefit from the fact someone who wasn't assigned to a project checked the channel out and was able to help.

        We still need it for the board groups. Because some board committee are private from the entire board. (Governing committee for example). But actually finding this feature is less important than we originally thought.

      • Anonymous commented  ·   ·  Flag as inappropriate

        We like our development team to have access to the Architecture Group but we will like to have a private channel for sharing draft documents between architects.

      • Nick Milner commented  ·   ·  Flag as inappropriate

        I have a services team who works on multiple projects so I'd like a channel per project plus a couple of general channels. I don't want every team member in every channel because there could be sensitive material shared, and I'd also like the ability to add customers to their project channels. Right now I have many teams with one channel in each which makes the concept of channels redundant. Thanks.

      • Jaap commented  ·   ·  Flag as inappropriate

        This is especially needed when externals work on our projects. We created a team for every customer, and a channel per project with that customer. I don't want another external digging in another project, even though it is within the same customer.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Add ability to create a new channel within a team but make it confidential between specific team members.

      • Matt Coyle commented  ·   ·  Flag as inappropriate

        This is very much a needed feature. Otherwise we are going to have to create a different Team for each group. We will be creating several Teams when all we need is one.

      • jeffwllms commented  ·   ·  Flag as inappropriate

        I think I have a somewhat different idea. Just do away with the team/channel thing all together. Have groups map directly to channel. You then have a 1 to 1 relationship with group data (another big issue) and you are able to add channels with specific groups. You reduce ui clutter since you don't have the concept of teams and channels.

        This also maps more closely to what you see in slack and other system. I think you were trying to create additional functionality by offering the additional level, but it jest seem like it is the root to all the extra confusion and complexity.

      • Stephane Moulec commented  ·   ·  Flag as inappropriate

        Totally agree that this is needed. It is nice to centralize a team activity in one group but not everyone needs access to all channels (project, topic, whatever concept a channel represents in an organization). Creating multiple teams as a workaround dilutes info IMHO

      Feedback and Knowledge Base