Forum Discussion
Security loophole in Private Channels?
This is not the isolation model Microsoft documents for a private channel. A private channel has a SharePoint site; membership is synchronized from Teams, and site permissions cannot be managed independently. Only channel owners and members should have site access.
The subsite appears to have broken inheritance and received a direct grant. SharePoint evaluates that subsite’s unique permissions, explaining why you can reach it while the channel site remains denied. Treat this as a configuration exposure, not proof that private-channel isolation is designed this way.
Have a SharePoint administrator audit the subsite’s unique permissions, sharing links, site-collection administrators, and sharing events. Remove the direct grant and restore inheritance if the content belongs to the channel. If permissions cannot be corrected, open a Microsoft support case before moving data. For content requiring another audience, use a separate SharePoint site with deliberately managed permissions rather than a subsite beneath a private-channel site.
It gets even more interesting.
I can create a Teams team, a private channel, a subsite of a private channel, and remove permissions inheritance on the default document library and I am allowed to invite a colleague to access the doc library via the sharepoint permissions page. And I can do this without the colleague being a member of the private channel.
However the permissions to the private channels site is still only controlled via the teams team (or of course the admin center).
So that is another way that someone who is not a member of a private channel can gain access to content associated with it.