Microsoft Teams and SharePoint Sites: Standard, Private, and Shared Channels
| Channel type | File location | Access boundary |
|---|---|---|
| Standard | Folder in the parent SharePoint site's library | Team membership |
| Private | Separate channel SharePoint site | Private channel membership |
| Shared | Separate channel SharePoint site | Shared channel membership; external users via B2B direct connect |
A team with several private or shared channels can have multiple SharePoint sites. An audit that visits only the parent site misses those separate storage and access boundaries. Microsoft's Teams and SharePoint integration reference (Microsoft Learn: Teams connected sites) documents this architecture and the differences between parent and channel sites.
Map the team before measuring storage
For each team, record the parent site URL and all private and shared channel site URLs. Add the channel type, business owner, active project, retention obligations, and latest review date. Include channel sites in your storage inventory rather than assuming every file appears under the General channel's site. Channel sites contribute to SharePoint storage even though users primarily encounter them through Teams.
Channel sites are not invisible to administrators. They are separate sites whose relationship to the parent team needs to be recorded. Use the SharePoint admin center and authorized Teams administration views to reconcile the inventory. Do not label a site orphaned solely because its name looks unfamiliar or nobody recognizes its URL.
Who controls permissions?
Team owners and members have access to the parent site. A private channel restricts its site to the channel's members; belonging to the parent team does not automatically grant access. Shared channels also have their own membership. Microsoft documents that channel-site owner and member groups are managed by Teams, so make membership changes there rather than trying to maintain an independent SharePoint membership list.
There is an important external-access distinction: private channels can include guests who are members of the parent team. shared channels cannot add Entra guest accounts as channel members; external collaboration uses B2B direct connect and the participating organizations' cross-tenant settings. A guest-account-only inventory does not cover all shared-channel collaboration.
Storage sprawl is an ownership problem, not just a folder problem
Multiple sites are an intended access boundary, not inherently a mistake. Review whether each channel still has a purpose, an owner, and a known retention requirement. Measure each site separately and check for preserved content before treating deleted files as reclaimed quota. See the Preservation Hold Library guide when storage remains high after cleanup.
Use a repeatable register: team, channel, site URL, owner, storage, external participants, retention status, and approved action. This is more useful than a tenant-wide delete list because each owner can confirm the proposed action. Schedule reviews around project closure as well as periodically, and record the decision to retain an inactive site when compliance requires it.
Do not delete channel sites independently
Teams manages channel-site lifecycle. Microsoft documents that deleting an active private channel's site outside Teams can trigger its restoration by a background job. Deleted and restored channels also have lifecycle rules. Review the parent team, channel status, restore window, and retention requirements before making changes; a SharePoint delete operation is not a reliable channel cleanup workflow.
Copying files is not migrating a team
Smart Copy copies Teams files stored in SharePoint, including full version history, in the same tenant or between tenants with identity mapping. It does not migrate Teams chats or channel conversations. A copy of a channel library does not recreate the channel, its membership, tabs, apps, or external collaboration configuration.
Provision the intended target structure first, confirm owner-approved access, and run a small test copy before moving the rest. Verify file counts, metadata, versions, and target permissions. Do not blindly reproduce source permissions if the destination has a different audience. The tenant-to-tenant migration playbook covers planning and cutover.
Smart Permissions can provide a read-only SharePoint permissions report for sites you are authorized to inspect. Treat it as file and site access evidence, not a Teams channel inventory or a cross-tenant B2B configuration audit. For the access model behind parent sites, see SharePoint groups vs Microsoft 365 groups vs Teams.
Get your first result in about 10 minutes
Visual permissions audit + Excel export. No PowerShell. Free, MIT licensed, no sign-up.
- Download the .sppkg package from the latest release.
- Upload it to your tenant App Catalog.
- Add the web part to a SharePoint page.
Email me when a new release ships
No marketing spam. One short email when a new release ships. You can unsubscribe anytime.
Was this page helpful?
One click. No form, no email address.
Missing something in SharePoint Smart Permissions? Feature requests and bug reports go straight to the developer on GitHub — no account needed to read, free account to post.
Request a featureRelated tool
SharePoint Smart Permissions
Visual permissions audit + Excel export. No PowerShell. Free, MIT licensed, no sign-up.
Keep reading
Compare two SharePoint folders and get a duplicate report in Excel
Point Smart Copy at any two folders in your tenant and it tells you what matches, what is duplicated, and what is missing — exported as an Excel workbook you can filter and share.
How to Migrate a Large SharePoint Document Library Without Timeouts or Throttling
One giant copy job is the most common reason large library migrations stall. Here is how to break the move into batches, pre-seed it and verify the result.
How to copy a Power Automate flow to a different SharePoint site or list (without rebuilding it)
A copied flow still points at the old site, list and columns. Microsoft's built-in options and the free Smart Copy Flows tool, compared for moving a flow to a brand-new SharePoint site.
Need expert hands on deck?
Let our team plan and run your SharePoint migration
Full-service file and metadata migrations across sites, tenants, or from on-premises to SharePoint Online, from planning and test runs to verification and cutover.
About the author
Sean Regan
SharePoint & Microsoft 365 consultant with 20+ years of hands-on experience building SPFx web parts, migration tooling and tenant-grade automation. Maintainer of the open-source SharePoint Smart Solutions suite.
