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)

19,284 votes
Sign in
(thinking…)
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 →

1626 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • David Gibson commented  ·   ·  Flag as inappropriate

    I have a private team for a group in leadership aka management. We have a channel for a project. I need to add a staff member to the channel, but not the entire group.

  • shane commented  ·   ·  Flag as inappropriate

    this is the one feature keeping my company from using Teams and sticking with Slack.

  • Becki commented  ·   ·  Flag as inappropriate

    SLACK obviously figured this out ages ago and is a key feature...why is it taking Microsoft so long to figure out private channels?

  • Anonymous commented  ·   ·  Flag as inappropriate

    It would be good if the private nature of the channel can be altered post the creation of the channel. For e.g. one might push out some information on a project to members of a team in a project specific channel but once a proposal has been accepted from a specific group of team members (or perhaps guest member - where the winning proposer is an external company) the channel will become private to a smaller group who are selected to work on the solution. This way one could easily handle requests for proposals - the request is public, any questions asked are answered publicly (to the extent that the team is "public") but once a specific proposal is accepted the channel becomes locked down as those whose proposal was not accepted no longer need to be involved in this specific channel while remaining engaged in the broader team and working through other channels.

  • Scott commented  ·   ·  Flag as inappropriate

    We are past the 1 year anniversary for the suggestion!

    Happy anniversary. See you back here November 2018

  • Anonymous commented  ·   ·  Flag as inappropriate

    This feature will definitely help improve adoption and reduce the number of Teams that are created.

  • Michael commented  ·   ·  Flag as inappropriate

    Do we have a timeline on this. I'm keen to have RBAC in place for the Team site I have created for my function. Seems ludicrous to have all Team members have access to all channels. I believe it should be:

    Team = overarching functions. e.g HR

    Channel = Sub functional elements (RBAC in place & only Channels you have access to visble) e.g Payroll, Training, Discipline, Standards, Performance.

    It also massively puts off new users as they are overwhelmed with the plethora of detail visible to them - whilst also confusing them as to where that are supposed to be working / posting.

  • Office 365 Japan Support Team commented  ·   ·  Flag as inappropriate

    *English follows Japanese
    Teams にて作成したチャンネルごとに固有権限を設定したい
    Teams にて作成したチャンネルごとに固有権限を設定したい
    ---------------------------------------------------
    I want to set specific permissions for each channel that created in Teams.
    I want to set specific permissions for each channel that created in Teams.

  • Anonymous commented  ·   ·  Flag as inappropriate

    We really need is not really permissions channel-wise, but team-wise, as already done with Public and Private teams.

    It is still lacking however:

    - List of all public groups available to users
    (currently they need to know before hand and type the name of the group)

    - Making public teams content open to anyone without needing to join the team

    This is the minimum necessary for content discovery, something Atlassian Confluence is great at.

  • Philip Noble commented  ·   ·  Flag as inappropriate

    This is essential for being able to use teams effectively, we won't be able to start using until in place

  • Anonymous commented  ·   ·  Flag as inappropriate

    As a consultant, this is an important feature for our project teams - we'd like the option of inviting our clients to participate in our Teams, but only if we can restrict them to specific channels. We obviously don't want/need separate Teams for internal and external conversations, that simply muddies the waters.

  • Michael commented  ·   ·  Flag as inappropriate

    We are testing this for the first time. What a disappointment. The lack of Channels pretty is pretty much a non starter for us. Unless this is available now, we will be dumping 365,

  • Skip Leezer commented  ·   ·  Flag as inappropriate

    The addition of this feature would be highly beneficial and significantly reduce the number of "teams" needing to be created just to create unique security.

    The note says this is a very complicated feature - just tag information in each channel and the secure all information to that tag. That would be a fairly simple way of creating and managing many sets of data within the team and channels. This does not help to define what happens on the back end in SharePoint - but tags are commonly used to control access and security policies in many areas of SharePoint.

  • Skip Leezer commented  ·   ·  Flag as inappropriate

    The addition of this feature would be highly beneficial and significantly reduce the number of "teams" needing to be created just to create unique security.

  • David commented  ·   ·  Flag as inappropriate

    I would like the ability to create a team (of my direct reports) and then a separate/private channel for each of them. Today, I have to set up seven different teams (one for each and me). Ideally, it'd be one team with seven private channels.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is already functionally working. If you don't know the name of a Channel, you will never find it in Teams.

  • Dan commented  ·   ·  Flag as inappropriate

    We are looking at Roll out of Teams and from initial chats outside IT, we are already seeing this as pretty essential functionality to achieve optimum buy-in.

Feedback and Knowledge Base