How to Limit access to Channels in a Single Team

New Contributor

Hello everyone and thanks in advance for the help!


Is there a way to share only one channel under a particular team and not all at once with the link?

We have a "Projects Awarded" and "Projects Bid" teams with many jobs/projects under each team.


I want to share just one of those individual channels or jobs to a particular person without them seeing all of the other projects. Is there a way to do that? I do I need to make a separate Team for every project?


Thank you,


30 Replies
best response confirmed by Juan Carlos González Martín (MVP)
No, you can’t currently! MS is working on a solution for this but we don’t know when!
Either use a different team or use a group chat with the files shared in that files folder ( onedrive )
Good Deal.
Thanks Chris!
Thanks Adam

We create Teams per client with channels per project, that way if we join a project we can see what's happened before at that client. It works really well.


I wouldn't wait for a new feature that's not been announced or has any timescale set, while it's a common ask it's not always really the best solution. 

Sure - but it’ll be the No.1 solution for Teams sprawl and resolve a major governance issue! :white_heavy_check_mark:
It’s a feature that for sure would help out and be useful in many cases, but I still think it’s overrated!
If you do take some time and do proper planning, you will do fine most times without having “private channels”
Teams is meant to be “if you’re in -> your in” experience and having a lot of channels with different permissions will create an administrative overhead even within the teams! There is a risk that it will be like the days of folder structures with many different permissions on a file server
I always tell people to look at it like Slack, except call Teams Channels. Then you basically have Private channels with sub channels. I mean, in reality when you look at it, it's the same thing. However, there are plenty of use cases for private channels for sure.

But I agree, group chat's work just fine, the biggest miss there is persistent file storage, and full group chat roster control. Once you can remove people from group chats, it'll be solid.... then maybe let you pin a group chat to a team as a channel, then only people in the group chat have it render.... next best thing to private channels right there :p

@adam deltinger I don't think it's actually overated Adam. Take for a example, I have so many clients in my company and scartered around the globe.


Company A has many offices/sites in different parts of the country and similarly in different countries. I have many of these sites who do not want share projects they're working on until it's completed. Others are happy to share which is fine. Without the option to restrict users to channels, one is left with creating multiple teams for all the various sites within a single company.


So in my thoughts, 1 Teams is better, have multiple channels for the different sites then make them public or private to limit audience.


In my case I can potentially have 1 Team (1 Organisation) with 8 channels (8 sites) but currently at it stands, I have to create 8 separate teams for a single organization. No amount of proper planning will help in this case - the problem is it soon becomes a clutter.

Hi! Thank you for the feedback! My take on overrated don’t mean that it can’t be used in a good way :) Wether you use teams or channels it might be cluttered both regarding to structure and permission wise!
But overall I’m not against private channels and do believe that with proper use of it, it definitely has its pros!!


I concur on that basis @adam deltinger, something gotta give somewhere. I've seen some really poorly implemented active directory, and other tree-node structure so - so I share the concerns where proper planning doesn't happen.

Your better off with multiple teams anyway. People want to cram everything in one channel. The point of channels is spreading conversations into different topics etc. by putting things into a channel you got an “inbox” folder that’s unmanaged basically.

By having teams for each then each one can utilize having multiple channels to split up those conversations, work streams and notifications.

I dunno some cases private channels make sense but in instances where you are trying to load projects by channel or customers by channels using teams makes more sense IMO.
Dear Chris,
So MS Teams's teams are not Project based, it is team based, isn't it?

For example,
I have a project called Workplace transformation including Building Team, Network Team, Users Team.
I would create 3 teams for this project at least because I do not want to let them see the details across the teams.
and then I have to create another team for announce the project progress and overall plan.

And meanwhile there are another project upcoming with multiple teams again, the teams list will be so long.

But the Private channel solves my problem.

@adam deltinger  I wrote an article last year about how you can make private folders within a Team.


I recently figured out how to do the opposite: invite Guests to individual folders/channels without giving them access to anything else in the Team. They won't have access to the conversations either.


@adam deltinger Holy crap this is limiting.  We have a team that has multiple projects, and those projects will naturally have a different set of people working on it.  We also may want to have management discussions that the rest of the members are either not privvy to or needed on.  Having channels be a free-for-all (especially with the "private" designation when literally anyone can just waltz on in there) is a ridiculous stretch of reasonable user assumptions when trying to migrate to this tool from something like Slack.  Why can't we just create a channel and add 2-3 people to it?  Why was this not assumed to be the default use case/behavior/need for a product like teams? 

Good it’s coming real soon then
Cool--any idea when, roughly?

Hopefully November.  It was due in September and then October 2019 but now that window has nearly passed too.

@Mike_CotterI can currently do that, tagging the Channel security level as "private".

Channel access (and left pane display) is then limited to members that are added to the "Private Channel".


=> Problem is that you cannot create more than 30 "private" channels within the 200 allowed per TEAM.