Shared channels in Microsoft Teams
Shared channels in Microsoft Teams create collaboration spaces where you can invite people who are not in the team. Only the users who are owners or members of the shared channel can access the channel. While guests (people with Azure Active Directory guest accounts in your organization.) can't be added to a shared channel, you can invite people outside your organization to participate in a shared channel by using Azure AD B2B direct connect.
You might want to use a shared channel if you want to collaborate with a group of people who are all members of different teams. For example, people from engineering, sales, and support who all work on different aspects of the same project or product could use a shared channel to collaborate.
Only members of shared channels can see and participate in shared channels that they are added to. Other members of the team to which the shared channel is connected won't see the channel.
When a shared channel is created, it's linked to the parent team and can't be moved to a different team. Additionally, shared channels can't be converted to standard channels and vice versa.
Getting started with shared channels
Shared channels is enabled by default in Teams. You can choose if people can create shared channels, if they can share them with people outside your organization, and if they can participate in external shared channels by creating a channel policy.
If you plan to share channels with people outside your organization, read Plan external collaboration for important planning considerations.
Sharing channels with people outside your organization also requires that you configure cross-tenant access settings in Azure AD. Each organization that you want to share channels with must also complete this configuration. See Collaborate with external participants in a channel for details.
Shared channel creation
Only team owners can create a shared channel. Team members and guests can't create them. The ability to create shared channels can be managed at the organization level. Use policies to control which users in your organization are allowed to create shared channels.
The person who creates a shared channel becomes the shared channel owner and only the shared channel owner can directly add or remove people from it. (You can add more than one owner if you want.) A shared channel owner can add anyone from the organization to a shared channel they created. Members of a shared channel have a secure conversation space, and when new members are added, they can see all conversations (even old conversations) in that shared channel.
Team owners can see the names of all shared channels in their team and can also delete any shared channel in the team. Team owners can't see the files in a shared channel or the conversations and member list of a shared channel unless they are members of that shared channel.
Team members can only see shared channels that they've been added to.
Cloning a team will not clone the associated shared channels.
Shared channel deletion
Deleted shared channel can be restored within 30 days after deletion. When a deleted shared channel is restored, all previous memberships (individual and team sharing) will be restored.
Deleted teams can be restored within 30 days after deletion. When a team is deleted, all shared channels will also be deleted. When a deleted team is restored, all shared channels will be restored as well with all sharing relationships.
When a team is archived, individual sharing will remain intact, but sharing with teams other than the parent team will be removed. When archived team is unarchived, all shared channels will be restored with individual sharing only.
Adding and removing owners and members
A shared channel owner can't be removed through the Teams client if they are the last owner of one or more shared channels.
If the last shared channel owner leaves your organization or if they are removed from the Microsoft 365 group associated with the team, a member of the shared channel from your organization is automatically promoted to be the shared channel owner. If there are no members from your organization to promote, the shared channel will remain ownerless. A Teams admin will have to manually assign a channel owner. Consider adding more than one owner to avoid this situation.
Guests - including those converted to members (in their user type property) - can't be added to a shared channel.
External participants must be added using their UPN, rather than their email address, if the two don't match in Azure Active Directory.
Channel owner settings
Each shared channel has its own settings that the channel owner can manage, including the ability to add and remove members, add tabs, and @mentioning for the entire channel. These settings are independent of the parent team settings. When a shared channel is created, it inherits settings from the parent team, after which its settings can be changed independently of the parent team settings.
The shared channel owner can click Manage channel, and then use the Members and Settings tabs to add or remove members and edit settings.
Shared channel owner and member actions
The following table outlines what actions owners, members, and guests can do in shared channels.
|Action||Team owner||Team member||Team guest||Shared channel owner||Shared channel member||Shared channel external participant|
|Create shared channel||Admin controlled||Admin and team owner controlled||No||N/A||No||No|
|Delete shared channel||Yes||No||No||Yes||No||No|
|Leave shared channel||N/A||N/A||N/A||Yes unless they are the last owner||Yes||Yes|
|Edit shared channel||No||N/A||N/A||Yes||No||No|
|Restore deleted shared channel||Yes||No||No||Yes||No||No|
|Manage tabs and apps||No||N/A||N/A||Yes, apps must be installed for the team||Channel owner controlled||No|
Shared channel SharePoint sites
Each shared channel has its own SharePoint site. The separate site is to ensure access to shared channel files is restricted to only members of the shared channel. These sites are created with a document library by default, and can be easily enhanced to a full-featured site through the site management interface. Each site is created in the same geographic region as the site for the parent team. These lightweight sites have a custom template ID, "TEAMCHANNEL#1", for easier management through PowerShell and Graph API.
A shared channel site inherits the sensitivity label of the parent team. This remains true even if the channel is shared directly with another team.
Only people with owner or member permissions in the channel will have access to content in the shared channel site. People in the parent team and admins won't have access unless they are also channel members.
Membership to the site owner and member groups are kept in sync with the membership of the shared channel. Site permissions for a shared channel site can't be managed independently through SharePoint.
Teams manages the lifecycle of the shared channel site. If the site is deleted outside of Teams, it is restored automatically within four hours as long as the shared channel is still active. If the site is permanently deleted, a new site is provisioned for the shared channel.
If a shared channel or a team containing a shared channel is restored, the sites are restored with it. If a shared channel site is restored and it's beyond the 30-day soft delete window for the shared channel, the site operates as a standalone site.
Shared channel messages
Shared channel messages are stored in a dedicated system mailbox associated with the Shared channel rather than the group mailbox.
For more information about performing an eDiscovery search for shared channel messages, see Conduct an eDiscovery investigation of content in Microsoft Teams.
Considerations around file access in shared channels
Files, folders, and OneNote notebooks in a shared channel can be shared with people outside the channel (but not outside the organization) by using standard SharePoint file sharing.
If a user is granted access to a file, folder, or notebook in a shared channel through SharePoint, removing the user from the team or shared channel won't remove the user's access to the file, folder, or notebook.
If an existing notebook is added as a tab to a shared channel, access to the shared channel isn't changed and the notebook retains its existing permissions.
Resources for your users
The following articles may be helpful for the users in your organization when they use shared channels.
Limits for shared channels
The following table describes the maximum number of channels and members.
|Members in a team||25,000||Includes all users in the team and direct members in shared channels.|
|Shared channels per team||200||Hosted and shared with the team. (Includes deleted channels during their 30-day recovery window.)|
|Teams a channel can be shared with||50||Excluding parent team|
|Members in a shared channel||5,000 direct members, including up to 50 teams. (Each team the channel is shared with counts as one member for purposes of this limit.)||Real time updates are only available to 25,000 users at a time and only 25,000 users will appear in the channel list.|
The following limitations also apply:
Only Azure AD work or school accounts are supported for external participants.
Shared channels support tabs except for Stream, Planner, and Forms.
Bots, connectors, and message extensions are not supported.
Org-wide teams are not supported to be added as members of a shared channel.
When you create a team from an existing team, any shared channels in the existing team won't be copied over.
Notifications from shared channels are not included in missed activity emails.
Shared channels are not supported in class teams.
Supported apps in shared channels
For information about how to prepare your app for shared channels, see How to open your app to cross-organizational collaboration with Microsoft Teams Connect.
The following apps are supported for use in shared channels.
- Adobe Acrobat Sign
- Calendar Pro
- Code by Vivani
- Freehand by InVision
- Jira Cloud
- Pear Deck
- Priority Matrix
- SharePoint Pages
- Tasks in a Box
- Teams Manager
- Zoho Projects