SharePoint
What is the difference between a SharePoint team site and a communication site?
Quick answer
A team site is a collaboration workspace: members co-author files, track lists, and usually get a connected Microsoft 365 group and Teams team. A communication site is a publishing surface: a small author group shares news, policies, and showcases with a large readership, without group membership overhead. Choose by authorship — many co-authors means team site, few authors with many readers means communication site — and connect related sites of either kind with a hub.
Key takeaways
- Team sites collaborate; communication sites broadcast.
- Authorship pattern decides — count the authors, not the readers.
- Hubs connect families of either type.
Detailed Explanation
A team site is a collaboration workspace: members co-author files, track lists, and usually get a connected Microsoft 365 group and Teams team. A communication site is a publishing surface: a small author group shares news, policies, and showcases with a large readership, without group membership overhead. Choose by authorship — many co-authors means team site, few authors with many readers means communication site — and connect related sites of either kind with a hub.
How it works
Creating a team site provisions a Microsoft 365 group (and optionally a Teams team), so membership drives access to files, lists, and chat at once. A communication site creates a standalone site collection with SharePoint-only permissions and designated owners. Hub association later layers shared navigation and search scope over both kinds without merging their permissions.
Limitations and considerations
Picking wrong costs rework: broadcasting on a team site spams members with access they should not need, while collaborating on a communication site fights its permission model.
For broader context, see the SharePoint Hub — it collects the guides around this topic.
When to use it
Default to team sites for work groups and projects; commission communication sites for departments, leadership, and intranet publishing.
Practical example
The migration project runs in a team site (plans, RAID log, Teams chat), while the program announces cutover windows from a communication site all staff can read.