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)

15,942 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 →
    needs your feedback  ·  Suphatra responded  · 

    Hey Microsoft Teams users — I want you to weigh in on new features around channels and group chats. The engineering team and I have put together this survey to find out how you want to see channels improve. You can fill it out here: https://microsoft.qualtrics.com/jfe/form/SV_esTxHdABLQxKLvn

    And I’m still waiting on approval to get you a good update about Private Channels. I can say that we ARE working on it, fervently.

    Thanks and ping me any time, for anything at all: www.twitter.com/skprufo or sparavi@microsoft.com. I’m a little behind on email but catching up, so apologies for delays there!

    Suphatra

    1396 comments

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

        When initiating a meeting and choosing the channel, user still needs to specify who should be invited (from the team list). By default, all members of the channel should be invited and not all members of the team (since the channel seems to be a subset of the team) and there is no need to bug everyone in the team with channel-specific meetings.

      • Cécile MAYER commented  ·   ·  Flag as inappropriate

        Hope the release will come soon, this is needed when you have a team with different areas of expertise: communications, administration, technical projects. You don't want to bother everyone with emails they are not concerned with

      • CHANDAN ESANAKULA commented  ·   ·  Flag as inappropriate

        individual channels should be able to be made public or private closed, in case of private only access on invite from members is allowed.

      • ed hansberry commented  ·   ·  Flag as inappropriate

        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.

      • Kamel L commented  ·   ·  Flag as inappropriate

        we're setting up teams, each team creates a specific channel for each project.
        We need to invite guests, to allow them to get updates as the project goes on, and to get info from them.
        The guests don't need to be part of the team, or to access to other channels whitin the team which invited them.

      • Tim commented  ·   ·  Flag as inappropriate

        Yes, private channels are important. One use case is specific team members may be assigned to a client's project. There would be a channel built for this project but only those assigned to the project should be in the channel.

      • Arden Shackelford commented  ·   ·  Flag as inappropriate

        I can't wait for this to be released! We're not even using this fully in my department, but this is a feature that is heavily requested!

      • Anonymous commented  ·   ·  Flag as inappropriate

        Make Channels private and only accessible by invite. A Project Team doesn't need to view what each channel 'team' is doing. For example, the developers don't need to see the conversation by the QA team. They are both part of the General Project Team, but channels could be used as 'sub-teams'.

      • 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.

      Feedback and Knowledge Base