Controlling settings, permissions, and membership within Teams and channels
Dear @Sanjay Dattani,
Welcome to Microsoft Q&A.
Thank you for explaining the folder structure and the access requirement so clearly. I’ve taken some time to review how this works in Microsoft Teams and SharePoint, as this is a scenario many organizations run into.
In Teams, file access is actually controlled by the underlying SharePoint site. Teams itself doesn’t offer granular control at the folder level, it simply follows whatever permissions are set in SharePoint. That’s why, when users are given access at the main folder or Team level, they can normally move into all subfolders by default.
You can refer to this article, this explains why permissions in Teams are tied to the underlying SharePoint site: Team site permissions and Microsoft 365 Groups
If your goal is to keep the current folder structure and restrict access to just one folder inside the Status folders, the supported approach is to manage that folder as an exception in SharePoint. This means removing inheritance on the restricted folder only and adjusting permissions there, while leaving access to the rest of the folders unchanged. Purchase Ledger (PL) users can continue to have full access across all folders.
From a Teams user’s point of view, that restricted folder will still be visible, but Depot users won’t be able to open it. Unfortunately, hiding folders in Teams based on permissions isn’t supported at the moment, so this behavior is expected.
You can find more details here: Customize permissions for a SharePoint list or library
If you’re open to alternative designs, there are a couple of other supported options worth considering:
- One is to use a Private channel for the restricted content. A private channel has its own SharePoint site, so only PL members would see and access those files, and Depot users would remain in the main Team. This avoids complex folder permissions and is often easier to manage long‑term.
You can learn more about this here: IT Admins - Private channels in Microsoft Teams
- Another option is to store the restricted documents in a separate SharePoint location that only PL users can access and then reference it where needed in Teams. This works well when the content needs clearer separation, although it does change the layout from a single folder structure.
I hope this explanation helps clarify why the issue occurs and points you in the right direction. If anything is unclear while applying this, or if something doesn’t behave as expect, please don’t hesitate to reach out again. I’ll do my best to support you however I can.
Looking forward to hearing back from you with any updates or additional details.
Warm regards,
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.