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,944 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...
      • Ladislav Šesták Jr. commented  ·   ·  Flag as inappropriate

        For me it's the same as for Emin Yalcindag.

        "TRY THIS INSTEAD" is not acceptable. I want to make a group with many people and then I want to make private channels in this group!

      • Emin Yalcindag commented  ·   ·  Flag as inappropriate

        "TRY THIS INSTEAD" is not acceptable. I want to make a group with many people and then I want to make private channels in this group!

      • Roger Wessel commented  ·   ·  Flag as inappropriate

        "Try this instead" does not solve the problem here, because: 1) We really need the possibility to invite external users to a single channel within the Team, and 2) We also need the possibility to restrict access to a single channel within the Team (so that just some of the Team members can access the channel).

      • Anonymous commented  ·   ·  Flag as inappropriate

        Your "Try this instead" doesn't work for what we need. We want the ability to add users outside the team to a channel that is still within the team. For example. We have a Technology Team and an Integration Team. They sometimes work together on projects. Right now the Tech team can't see anything in the Integration Team's group, and vice versa. However they're working on a new Tech Project together, and members from both groups need to collaborate in a single channel. I don't want the teams to have unfettered access to every discussion they've both had, but I do want them to work on one channel together without having to create a separate "Tech AND Integration" team.

      • Terry commented  ·   ·  Flag as inappropriate

        Why should we have to have multiple sharepoint sites, groups, etc. created for that? seems excessive to do given enacting limited visibility to a channel shouldn't really be that hard of a task to complete.

      • Terry commented  ·   ·  Flag as inappropriate

        So you are forcing us to create two+ groups for the same team so that we can silo some folks to each one? seems a bit reducndant and kind of takes away from what the channels could actually do.

      • Jennie commented  ·   ·  Flag as inappropriate

        This is a functionality that relates to tasking, not just for visibility of a task. This is a critical piece and this work around is not the same as what is being asked

      • Anonymous commented  ·   ·  Flag as inappropriate

        I like that you added the ability to private a whole team, but I can see it getting confusing having my developers jumping back and forth from one team to another. Information will definitely be put into the wrong team. The way we typically organize in Slack is one team for everyone and anyone from the company can join who would like to see what is happening with our products. Each product has public and private channels. The public channel is used to broadcast information to our product owners and anyone interested in updates of the release. The private channel is for internal team work only (the back and forth conversations that happen while the team is working). Sometimes there are multiple public and private channels for a product if we need break them up into smaller components for the group to work in smaller circles.

      • matshe@microsoft.com commented  ·   ·  Flag as inappropriate

        I would need to use this more to give very good feedback.

        Private channels may still be important. It is way too heavy to create this many private teams on the fly. :( Channels are supposed to be more light way, ways to have a conversation on the fly. Perhaps the encouragement should be towards group chat instead? Though there some might lose needed functionality that a channel has?

      • Al Linke commented  ·   ·  Flag as inappropriate

        My users asking for this too. Creating additional teams for this need would just clutter things up, not a good way to go.

      • Marc Wenning commented  ·   ·  Flag as inappropriate

        really need to the ability to create private channels within a team, having to create a new private team seems unnecessary and would add teams that really arent needed when they could just be a private channel.

      • Max commented  ·   ·  Flag as inappropriate

        The "try this instead" does not meet our needs. It is not useful for us to have to create a new group/Team for every sub-conversation when a private channel in an existing team would be much easier.

      • Mstyslav commented  ·   ·  Flag as inappropriate

        We at the beginning of preparing a structure of the MS Teams in our organization, and private channels is crucial if we want to avoid needless multiplying of teams.
        Provide us with ETA, please

      • Cory Calderon commented  ·   ·  Flag as inappropriate

        You should be able to have both open and private channels. Project teams usually consist of people at all levels of the organization (manager, supervisor, specialist, etc.). Some channels should remain private where private conversations, documents and files can be exchanged. For example, a Finance Channel might have people from the finance department sharing budget or compensation information.

        You want that conversation happening on a MS Team, but not visible to all people and all stakeholders. If this feature was enabled, it would improve our MS Team adoption rate because employees are fearful that anything and everything is visible to all team members.

        We are a company of 500 employees and 14 regional offices. MS Teams is critical, but with a few tweaks it can be our go-to standard for team management.

      • Damien commented  ·   ·  Flag as inappropriate

        this is a key feature to manage the Teams structure, and prevent a lot of duplicates and inefficiency

      Feedback and Knowledge Base