# Teams standard vs private vs shared channels: permissions and storage

> Compare standard, private and shared channels in Microsoft Teams: who can join, where files live, which features each lacks, and how to control creation.

Source: https://www.epifive.com/blog/teams-private-vs-shared-channels · Published 2026-10-22 · EpiFive

Teams has three channel types, and the right one depends on who must be inside the conversation. Use a standard channel when everyone in the team should see it, a private channel when only a subset of the team should, and a shared channel when people outside the team, or outside your organization, need to collaborate without joining the team.

This choice is permanent. Microsoft documents that private and shared channels cannot be converted to another type or moved to a different team, so it is worth getting right before content accumulates.

## Who this is for and what you will have at the end

This guide is for Microsoft 365 and Teams administrators, and for team owners who have to decide which kind of channel to create. It covers what each type does with membership, files, meetings and apps, what it costs you in features, and how to control who can create each type.

By the end you will have a decision table, a clear picture of where each type stores files, a policy configuration for the Teams admin center, and a short list of error and behaviour surprises to check when a channel does not behave as expected.

## Prerequisites

- A Teams administrator role to edit Teams policies, or team owner rights to create channels.
- Access to the Microsoft Teams admin center.
- For PowerShell examples, the MicrosoftTeams module, connected with `Connect-MicrosoftTeams`.
- For shared channels with external participants: cross-tenant access settings configured in Microsoft Entra ID, on both sides. Guest access in Teams must also be enabled in order to invite external participants, even though external participants do not use guest accounts.

## The three channel types at a glance

A team is the container: it has members, owners, one Microsoft 365 group and one SharePoint team site. Channels are the topic areas inside it.

| Question | Standard | Private | Shared |
| --- | --- | --- | --- |
| Who can see it | All team members | Only channel owners and members | Only channel owners and members |
| Can membership be a subset of the team | No | Yes | Yes |
| Can people outside the team be added without joining the team | No | No | Yes |
| Can guests participate | Yes | Yes (must already be team members) | No |
| Can external participants (B2B direct connect) participate | No | No | Yes |
| Can it be shared directly with other teams | No | No | Yes |
| Files stored in | A folder in the team's SharePoint site | Its own SharePoint site | Its own SharePoint site |

The comparison is taken from the Microsoft Learn channel feature comparison, which also lists feature gaps. Two rows deserve emphasis because they surprise people.

First, guests and external participants are different things. A guest is a person with a Microsoft Entra guest account in your directory. Guests can be members of a team and can be added to private channels, but they cannot be added to a shared channel, including guests whose user type was converted to member. External participants are people from other organizations who join a shared channel through B2B direct connect and keep their own identity. The EpiFive article on [Teams external access vs guest access](https://www.epifive.com/blog/teams-external-access-vs-guest-access) covers the broader external collaboration settings.

Second, "private" does not mean the same thing in both models. A private channel is private within one team: its members are always a subset of the team. A shared channel is private to its own member list, and other team members cannot see it.

## Standard channels

A standard channel is open to every member of the team. Conversations, files and notes in it are visible to all team members, and its files go into a folder inside the default document library of the team's SharePoint site.

Standard channels have the fullest feature set. According to the Microsoft comparison table, they are the only type that supports moderation, copy link to channel, Planner, and bots, connectors and messaging extensions. They also support scheduled meetings and analytics.

Because channel files are folders in the team site, file tabs in standard channels share the storage limits of the team they belong to. Teams files can use up to 25 TB per site or group, and the per-file upload limit is 250 GB, according to the limits page.

Choose a standard channel by default. Add a restricted channel type only when there is a specific confidentiality or collaboration need.

## Private channels

A private channel creates a focused space for a subset of the team. Only the users who are owners or members of the private channel can access it, and anyone, including guests, can be added as long as they are already members of the team. A lock icon marks a private channel.

### Creation and ownership

By default any team owner or team member can create a private channel. Guests cannot. Admins control this with a Teams policy, and once the policy allows it, team owners can turn the ability on or off for members in the team's **Settings** tab.

The creator becomes the private channel owner, and only a private channel owner can directly add or remove people. New members see all conversations in the channel, including old ones. Team owners who are not members of the private channel can see it under **Manage team** but not in the channels list. A private channel owner or a team owner can delete it, and a deleted private channel can be restored within 30 days.

A few ownership rules matter in practice:

- The last owner of a private channel cannot be removed through the Teams client.
- If a private channel owner leaves the organization or is removed from the team's Microsoft 365 group, a member of the channel is automatically promoted to owner.
- If someone leaves or is removed from the team, they are removed from every private channel in that team. Re-adding them to the team does not restore the channel memberships; an owner must add them again.

### Storage and access

Each private channel has its own SharePoint site, so channel files are restricted to channel members. Per the documentation:

- The site is created in the same geographic region as the parent team site.
- It uses the custom template ID `TEAMCHANNEL#0` or `TEAMCHANNEL#1`, which helps when you script against sites.
- Only people with owner or member permission in the channel can access it. People in the parent team and admins do not have access unless they are also channel members.
- Membership of the site owner and member groups is kept in sync with the channel. Site permissions cannot be managed independently in SharePoint.
- The site inherits data classification and guest access permissions from the parent team site.
- If the site is deleted outside Teams, a background job restores it within four hours as long as the channel is still active.

Sharing files from a private channel site works like any SharePoint site and follows the sharing settings your SharePoint administrator configured. One trap: if someone is granted access to a OneNote notebook through SharePoint, removing them from the channel or team does not remove that access.

### Compliance behaviour

Compliance copies of private channel messages go to the group mailbox, not to each member's mailbox, and the copy's title indicates which private channel it came from. Retention policies can be applied to private channel sites. Microsoft also notes that private channels have moved to a group compliance model, and that the `Get-TenantPrivateChannelMigrationStatus` cmdlet reports whether all private channels in your tenant have moved to it.

### Limits

Microsoft's note on the private channels page states that private channels now support channel meetings and are no longer limited to 30 per team; they count towards the overall limit of 1,000 channels per team. This excludes tenants in special cloud environments, where it arrives later. The limits page lists up to 5,000 members in a private channel. Deleted channels continue to count towards the per-team limit for 30 days.

Private channels do not support connectors and tabs for Stream, Planner, Tasks by Planner and To Do, and Forms. Their notifications are not included in missed activity emails.

## Shared channels

A shared channel is a collaboration space that includes people who are not in the team. Only owners and members of the channel can access it, and other members of the parent team cannot see it unless they are added.

### What makes them different

You can add:

- People from your own organization who are not members of the team.
- Other teams in your organization, through direct sharing. Up to 50 teams other than the parent team can be shared with, and each team counts as one member for the channel's member limit.
- People outside your organization, using Microsoft Entra B2B direct connect.

Guests cannot be added. When you add an external participant in the Teams admin center who also has a guest account in your tenant, search for `ext:user@fabrikam.com` to get the participant's organization account instead of the guest account. External participants must be added by UPN if the UPN and email address do not match in Microsoft Entra ID.

### Creation and ownership

Shared channels are enabled by default. Only team owners can create them; team members cannot. The creator becomes shared channel owner, and you can add more than one owner. That second owner is not optional in practice: if the last owner leaves, a member from your organization is promoted, but if there is no member from your organization to promote, the channel stays ownerless until a Teams admin assigns an owner.

Team owners can see the names of all shared channels in the team and can delete any of them, but they cannot see the files, conversations or member list unless they are members.

### Storage and messages

Each shared channel has its own SharePoint site, created with a document library and with template ID `TEAMCHANNEL#1`. As with private channels, the site is in the parent team's geography, access is limited to channel members, and site permissions cannot be managed independently. The site inherits the sensitivity label of the parent team, even if the channel is shared directly with another team. If someone deletes the site outside Teams, it is restored within four hours while the channel is active; if it is permanently deleted, a new site is provisioned.

Messages in a shared channel are stored in a dedicated system mailbox associated with the shared channel, rather than the group mailbox.

Files can be shared with people outside the channel but not outside the organization, using standard SharePoint sharing. As with private channels, access granted through SharePoint is not removed when someone leaves the channel.

### Deletion and lifecycle

A deleted shared channel can be restored within 30 days, with all previous memberships, both individual and team sharing. Deleting a team deletes its shared channels, and restoring the team restores them with their sharing relationships. Archiving a team keeps individual sharing but removes sharing with teams other than the parent; unarchiving restores individual sharing only. Cloning a team does not clone its shared channels.

### Compliance and security

Shared channels are integrated with Microsoft Purview, with some boundaries worth knowing:

- Conditional Access policies from the host organization apply to B2B direct connect users. Supported policies are scoped to **All guest and external users** and the **Office 365 SharePoint Online** cloud app, using grant controls that require MFA, a compliant device, or a Microsoft Entra hybrid joined device. The external organization's policies are not used.
- DLP policies and retention policies applied to the team are inherited by its shared channels.
- Only sensitivity labels from the host organization can be applied to documents in the shared channel site, and a file encrypted by a label cannot be opened by external participants unless permissions are granted.
- Information barrier policies apply only to users in the host organization. Users who are not allowed to communicate cannot be in the same shared channel.
- Admins can place channel-only members from the host organization on legal hold, but cannot place an external participant on hold.

### Limits and gaps

From the limits page: up to 5,000 direct members in a shared channel, up to 1,000 shared channels per team, and external shared channel members count towards the team's 25,000-member limit. Only Microsoft Entra work or school accounts are supported for external participants. Bots, connectors and message extensions are not supported; tabs work, except for Stream, Planner and Forms. Org-wide teams cannot be added as members, and shared channels are not supported in class teams.

## Feature gaps that decide the choice

Check this before you commit to a type, using the feature comparison table on Microsoft Learn:

| Feature | Standard | Private | Shared |
| --- | --- | --- | --- |
| Moderation | Yes | No | No |
| Copy link to channel | Yes | No | No |
| Planner | Yes | No | No |
| Bots, connectors, messaging extensions | Yes | No | No |
| Analytics | Yes | Yes | No |
| Supported in class teams | Yes | Yes | No |

Note that the comparison table lists scheduled meetings as not supported in private channels, while the private channels page states they now support channel meetings. When the two disagree, test the behaviour in your tenant before you promise it to users, and treat the newer page as the more likely to be current.

## How to choose

Use these questions in order:

1. Does everyone in the team need to see this? Use a standard channel.
2. Does a subset of existing team members need confidentiality, for example budgets or HR topics? Use a private channel.
3. Do people who are not in the team need to participate, whether colleagues from other teams or partners in other tenants? Use a shared channel.
4. Do you need guests to take part? Use a standard or private channel. Shared channels do not accept guests.
5. Do you need moderation, Planner, or bots and connectors? Use a standard channel.

If the real need is a long-lived confidential workspace with its own lifecycle, consider a separate team instead of a private channel. A private channel is linked to its parent team permanently, and a person removed from the team loses all private channel access.

## Control who can create each type

Creation is controlled with a Teams policy in the Teams admin center.

### Teams admin center

1. Go to **Teams** > **Teams policies**. In the newer experience the path is **Settings & policies** > **Custom Policies for users and groups** > **Teams**.
2. Edit the global (Org-wide default) policy, or choose **Add** to create a custom policy.
3. Set the channel policies, then save.

The channel settings are:

| Policy | Effect when On |
| --- | --- |
| **Create private channels** | Team owners and members can create private channels. Team owners can control this per team. |
| **Create shared channels** | Team owners can create shared channels. |
| **Invite external users to shared channels** | Owners and members of shared channels can invite external participants from organizations where cross-organization trust is configured. |
| **Join external shared channels** | Users can participate in shared channels created by other organizations where cross-organization trust is configured. |

Users receive the global policy unless you assign a custom one. After you edit the global policy or assign a policy, it can take 24 hours for changes to apply.

### PowerShell

The `Set-CsTeamsChannelsPolicy` cmdlet exposes the same settings as Boolean parameters.

```powershell
Connect-MicrosoftTeams

# Turn off private channel creation in the global policy
Set-CsTeamsChannelsPolicy -Identity Global -AllowPrivateChannelCreation $false

# Allow shared channels but block inviting external users
Set-CsTeamsChannelsPolicy -Identity Global `
    -AllowSharedChannelCreation $true `
    -AllowChannelSharingToExternalUser $false
```

Two details from the parameter documentation are important. With `-AllowChannelSharingToExternalUser $false`, a channel that has already been shared with an external member or team keeps that access. Likewise, if one of your teams is already part of an external shared channel, new team members get access even if `-AllowUserToParticipateInExternalSharedChannel` is `$false`. The policy stops new sharing; it does not revoke existing sharing.

Several newer parameters on the same cmdlet, such as `-AllowCreateChannel` and `-DefaultChannelTypeOnCreation`, are documented as not yet fully released and having no effect, so do not rely on them.

### Inventory private channels

To list the private channels of a team, use the `-MembershipType` parameter of `Get-TeamChannel`.

```powershell
Get-TeamChannel -GroupId af55e84c-dc67-4e48-9005-86e0b07272f9 -MembershipType Private
```

The `-GroupId` value identifies the team. Note that the cmdlet documentation describes the Private membership type as available in private preview, so check that it returns results in your environment before building reports on it.

## Verification

After setting policies and creating test channels, confirm the behaviour:

1. As a user covered by the policy, check whether the option to create a private or shared channel appears. Allow up to 24 hours after a policy change.
2. Create a private channel, add one team member, and confirm another team member cannot see it in the channel list.
3. Open the channel's **Files** tab, choose to open in SharePoint, and confirm the site URL is separate from the team site, and that membership matches the channel.
4. For a shared channel, add an internal user who is not in the team and confirm they can see only that channel.
5. For external participants, confirm cross-tenant access settings are configured on both tenants and that the participant appears under the `ext:` search result.

## Troubleshooting

| Symptom | Likely cause and fix |
| --- | --- |
| User cannot see **Create private channel** or **Create shared channel** | The Teams policy has the setting off, the policy was changed less than 24 hours ago, or the user is a guest. Guests cannot create private channels, and only team owners can create shared channels. |
| Team member cannot create a private channel, but owners can | The team owner turned off member creation in the team's **Settings** tab. |
| Cannot add a guest to a shared channel | Not supported. Guests cannot be added to shared channels. Use a private or standard channel, or invite the person as an external participant through B2B direct connect. |
| Cannot add an external participant | Cross-tenant access settings for B2B direct connect must be configured by both organizations, and the policies **Invite external users to shared channels** and **Join external shared channels** must allow it. Guest access in Teams must also be enabled. |
| Wrong account returned when adding an external participant | The person also has a guest account in your tenant. Search for `ext:user@fabrikam.com`, or add the participant by UPN if the UPN and email address differ. |
| Shared channel has no owner | The last owner left and no member from your organization could be promoted. A Teams admin must assign an owner. Add more than one owner to avoid this. |
| Person removed from the team still opens files | Access was granted directly in SharePoint, for example by sharing link or notebook permission. Removing them from the channel or team does not remove that access. Review sharing on the channel site. |
| Admin cannot open private channel files | Expected. Admins and parent team members have no access to the channel site unless they are channel members. |
| Channel site deleted | Teams restores it within four hours if the channel is still active. Do not manage the site's permissions separately in SharePoint. |
| Team member re-added to the team has no private channel access | Removal from a team removes the user from all its private channels. A private channel owner must add them back. |

For file-sharing questions beyond Teams, see [SharePoint Online permissions done right](https://www.epifive.com/blog/sharepoint-online-permissions-best-practices).

## Checklist

- Default to standard channels, and add private or shared channels only for a defined need.
- Decide the channel type before content is created; there is no conversion or move.
- Remember that guests belong in standard or private channels, and external participants belong in shared channels.
- Add a second owner to every private and shared channel.
- Set **Create private channels** and **Create shared channels** deliberately in the global or a custom Teams policy.
- Configure cross-tenant access settings on both tenants before inviting external participants to shared channels.
- Do not manage private or shared channel site permissions directly in SharePoint.
- Review files shared through SharePoint links, because they outlive channel membership.
- Check the feature gaps (moderation, Planner, connectors, bots) before choosing a restricted type.

## References

- Overview of teams and channels in Microsoft Teams: https://learn.microsoft.com/en-us/microsoftteams/teams-channels-overview
- Private channels in Microsoft Teams (IT admins): https://learn.microsoft.com/en-us/microsoftteams/private-channels
- Shared channels in Microsoft Teams: https://learn.microsoft.com/en-us/microsoftteams/shared-channels
- Limits and specifications for Microsoft Teams: https://learn.microsoft.com/en-us/microsoftteams/limits-specifications-teams
- Manage channel policies in Microsoft Teams: https://learn.microsoft.com/en-us/microsoftteams/teams-policies
- Set-CsTeamsChannelsPolicy: https://learn.microsoft.com/en-us/powershell/module/teams/set-csteamschannelspolicy
- Get-TeamChannel: https://learn.microsoft.com/en-us/powershell/module/teams/get-teamchannel

## Frequently asked questions

### What is the difference between a private channel and a shared channel in Teams?

A private channel limits access to a subset of the parent team's own members, and guests who are already in the team can be added. A shared channel can include people who are not in the team, from your own organization or from other organizations through Microsoft Entra B2B direct connect, but guests cannot be added to it.

### Where are files stored for private and shared channels?

Files in a standard channel are stored in a folder of the parent team's SharePoint site. Each private channel and each shared channel has its own SharePoint site, created in the same geographic region as the parent team site, and only channel owners and members can access it.

### Can I convert a standard channel to a private or shared channel?

No. Microsoft documents that private channels and shared channels cannot be converted to standard channels or the reverse, and that they cannot be moved to a different team. If you chose the wrong type, create a new channel of the correct type and move the content yourself.

### How do I stop users from creating private or shared channels?

In the Teams admin center, go to Teams, then Teams policies, and turn off Create private channels or Create shared channels in the global policy or a custom policy. Policy changes can take up to 24 hours to take effect.