When someone opens a file in Teams, they are often working with SharePoint, even if SharePoint never appears. For permissions and later search, what matters is which channel type holds the file.
The three channel types compared
| Channel | Where files are stored | Who controls membership? |
|---|---|---|
| Standard | A folder in the document library of the parent team site | The team |
| Private | Its own SharePoint channel site | The private channel |
| Shared | Its own SharePoint channel site | The shared channel |
Standard channels therefore share the team site; private and shared channels each have their own site. Microsoft describes this architecture in its documentation on Teams and SharePoint.
A practical example
A project team stores general templates in a standard channel, where all team members can work with the files. For confidential proposal documents, it sets up a private channel with deliberately chosen members. If an external partner needs to edit files together with the team, the team assesses a shared channel and the settings for cross-tenant collaboration. A shared channel is not a substitute for a public file repository.
Before creating channels, owners should answer four questions:
- 1Who needs permanent access, and who only for a project?
- 2Do external people need to collaborate? Assess guest sharing and shared channels separately.
- 3Who reviews membership when the project ends?
- 4Where should completed documents be retained?
For private and shared channels, membership is managed in Teams; SharePoint only displays the channel site permissions. A link to an individual file can have additional sharing rules. So test with an account that is not already a member. Microsoft explains the differences between permissions and sharing links.
How to review an existing environment
Open the channel in Teams and choose “Open in SharePoint” under Files. Note the site address, channel type and members. Compare this with the site's sharing settings. Only then is it worth changing folders, metadata or retention rules. A clean structure starts with a clear access decision, not with as many channels as possible.

