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)

21,328 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

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


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • Tim ONeill commented  ·   ·  Flag as inappropriate

    Any update? What is your best guess at an ETA for this feature? It's pretty mandatory. As it is we have to use SP permissions to make sub-folders with restricted access / documents but we can't discuss them or refer to them at all in MS Teams ...

  • Deniz commented  ·   ·  Flag as inappropriate

    Any updates on this? We are waiting for this to be delivered to switch to teams app.

  • Anonymous commented  ·   ·  Flag as inappropriate

    hi Suphatra, it's been a while since we've heard from you. When do you suspect this functionality will be in place. Like many of my fellow Microsoft Teamers, we cannot implement Teams into our environment until permissions at the channel level are in place. Please advise...

  • Creft commented  ·   ·  Flag as inappropriate

    Will this feature also roll out to your educational experience as well. This was one of the key features we were looking forward to. Are there any updates to the timeline for deployment?

  • Anonymous commented  ·   ·  Flag as inappropriate

    Yikes, just found out that we cannot have private channels. DISASTER! This is critical for deployment.

  • Scott Brower commented  ·   ·  Flag as inappropriate

    An absolute must-have that has been available within Slack for a long time. As we evaluate using Teams at our company, this is truly critical feature.

  • John Pickett commented  ·   ·  Flag as inappropriate

    To echo what many have said, this seems like such an obvious capability. We are experiencing extreme team sprawl with many teams only having 1-2 channels. As users gain more experience, channels get consolidated as threaded conversations increase, particularly since there's very limited benefits to creating multiple channels without any kind of access control. Why create a channel for a specific topic when you can just create a few threaded conversations? How it works currently just confuses users and makes the distinction between a team and channel difficult to quantify.

  • Bob commented  ·   ·  Flag as inappropriate

    Please provide an updated timeline... we are waiting on this before rolling out to our firm.

  • Anonymous commented  ·   ·  Flag as inappropriate

    To our Organisation this is the key factor to moving to Teams, we don't want Team sprawl.

  • Giulio Vannini commented  ·   ·  Flag as inappropriate

    Having this feature would dramatically reduce the need of classic SP Team sites in my organization ...

  • Devis commented  ·   ·  Flag as inappropriate

    Really waiting for this feature before rolling out Teams to the business

  • David commented  ·   ·  Flag as inappropriate

    This would be the feature that put our organization over the edge for adoption of Teams. A must have.

  • Anthony Marc commented  ·   ·  Flag as inappropriate

    I'm really looking forward to this. It is a major obstacle for organization adoption of Teams for me. We have a lot of teams that need to collaborate with different departments, but they don't need their whole document library visible to everybody. It causes a security issue on several levels because of the sensitive nature of some of these libraries. Being able to invite someone to participate in just a channel will eliminate having to create a separate Team for each department people have to collaborate with and will clean up the interface a ton! Not to mention how much it will improve the user experience. I was really hoping to hear about this coming soon at Ignite, but I didn't hear anything about it. Did I miss it? How soon can we expect to see something like this?

  • Miguel Sanabia commented  ·   ·  Flag as inappropriate

    This was mentioned in many of the Ignite sessions and even at the solutions booth but no real ETA. The only mention is by end of year. This is a really sought after feature that many are in need of, and like in our case has really hindered our ability to release it to everyone.

  • Nick Duxfield commented  ·   ·  Flag as inappropriate

    Wow this is a Gotcha moment I came to early on. I only started with one team, and that's all i needed. But one sub group in the team wanted to chat privately. Answer, I needed to create another group. For another chat channel it creates a teams site and the full set of resources. Is that necessary.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Will this work with OneNote ClassNotebook's? I am envisioning a new Collaboration Space section being created with each new private team...

    Can you please loop in the Edu team when you're creating the workflow?

  • [Deleted User] commented  ·   ·  Flag as inappropriate

    I had this idea with a colleague last week. We worked together on several topics. But only two persons and it‘s not a need to create a special team for these topics.

    It would be great to create channels in the private chat per person I communicate. Or conversations would be in order and we would found the information faster.

  • Daniel V commented  ·   ·  Flag as inappropriate

    I‘m not quite sure, if this was already discussed, but I would suggest to divide the file storage of different channels within a team not by folders within one document library but by single document libraries per channel. To be honest, we have an issue with OneNote then because OneNote must reside in different document libraries as well, which is not a good idea in terms of user experience...
    So maybe it is best, to create dedicated document libraries (to restrict access easily) when creating a private channel. Same is true when creating a OneNote-Tab within this private channel. The OneNote Notebook could be created in the dedicated private document library as well.

    This would enhance guest access SOOOO much! :-)

Feedback and Knowledge Base