SharePoint Groups vs Microsoft 365 Groups vs Teams: How Access Really Flows
| Site type | What controls access | Where to add people | Read-only role |
|---|---|---|---|
| Team site (group-connected) | The Microsoft 365 group | The group, or the Teams team if there is one | Add to the site's Visitors group directly |
| Team parent site (standard channels) | The team's Microsoft 365 group | Teams (team owners and members) | Add to the site's Visitors group directly |
| Private channel site | The channel's owners and members | The channel in Teams | Not managed in SharePoint (read-only there) |
| Shared channel site | The channel's owners and members | The channel in Teams | Not managed in SharePoint (read-only there) |
| Communication site | SharePoint Owners, Members and Visitors groups | Those SharePoint groups | The Visitors group |
"Who has access to this site?" sounds like one question, but SharePoint answers it with three different kinds of group, and which one is in charge depends on how the site was created. Mix them up and you get the classic tickets: a person is in the team but can't see a file, someone left the project but can still open it, or an auditor sees a group name instead of people. This guide explains how the pieces fit, in plain terms, with a one-page rule for where to add people.
The three kinds of group, in one minute
| Group | Where it lives | What it does |
|---|---|---|
| SharePoint groups (Owners, Members, Visitors) | Inside one SharePoint site | Bundle permission levels. By default Owners get Full Control, Members get Edit and Visitors get Read. |
| Microsoft 365 group | Microsoft Entra ID (the whole tenant) | One membership list that unlocks several services at once: a SharePoint site, a mailbox, a calendar, Planner and others. |
| Teams team | Teams, backed by a Microsoft 365 group | Team membership is stored in the team's Microsoft 365 group, and that group also gives people access to the team's SharePoint site. |
The simple summary: a team is a Microsoft 365 group with chat added, and a team site is the SharePoint site that belongs to that group. SharePoint groups are the older, per-site mechanism, and they still do the work on sites that have no Microsoft 365 group.
Which group controls access, by site type
Per Microsoft's sharing and permissions overview, it depends on the site type:
| Site type | What controls access | Where to add people | Read-only role |
|---|---|---|---|
| Team site (group-connected) | The Microsoft 365 group | The group, or the Teams team if there is one | Add to the site's Visitors group directly |
| Team parent site (standard channels) | The team's Microsoft 365 group | Teams (team owners and members) | Add to the site's Visitors group directly |
| Private channel site | The channel's owners and members | The channel in Teams | Not managed in SharePoint (read-only there) |
| Shared channel site | The channel's owners and members | The channel in Teams | Not managed in SharePoint (read-only there) |
| Communication site | SharePoint Owners, Members and Visitors groups | Those SharePoint groups | The Visitors group |
Team sites and Microsoft 365 groups
By default every SharePoint team site belongs to a Microsoft 365 group. Microsoft says that when you add owners or members to the group, they get access to the site along with the other group services, and that group owners become site owners while group members become site members.
One detail surprises people: Microsoft 365 groups don't have a view-only role. If someone should be able to read a team site but not edit it, add them directly to the site's Visitors group, which is a SharePoint group on the site.
You can add people straight to the site's SharePoint groups instead of the Microsoft 365 group. Microsoft recommends against it for the simplest management. The reason is that people added directly to the site won't get the group's other services, and you now have two places to check when someone asks why they can or can't open something.
Teams: one team, several sites
Per Microsoft's Teams and SharePoint integration page, a team's membership lives in its Microsoft 365 group, and the files on each channel's Files tab live in SharePoint. How that works depends on the channel type:
- Standard channels all share the team's parent site. Each channel shows up as a folder in that site's default document library, and every team owner and member can reach all of it.
- Private channels each get their own SharePoint site. Only members of the private channel can reach it, so a team member who isn't in the channel can't open its files.
- Shared channels also get their own site, and only members of the shared channel can reach it. A shared channel can include people from outside the team, and even outside your organization.
For private and shared channel sites, Microsoft says permissions are managed in Teams: channel owners become site owners, channel members become site members, and SharePoint shows the permissions read-only. The practical rule for Teams-connected sites is the same as for group-connected ones: do the permission work in Teams.
Communication sites and hub sites
Communication sites aren't connected to Microsoft 365 groups. They use the three SharePoint groups. You can put individual users, security groups or Microsoft 365 groups into any of them. A few habits from Microsoft's guidance are worth copying:
- Keep Owners to a few named people, and Members to the small group that creates content.
- Use a security group in Visitors to give a large audience read access without listing every person.
- Avoid nesting security groups inside each other, which Microsoft says can cause performance issues.
- If a team should create content on a communication site, add the team's Microsoft 365 group to the site's Members group.
A hub site isn't a separate type for permissions. It follows the site underneath it: manage it through the Microsoft 365 group if it's a team site, or the SharePoint groups if it's a communication site.
Five mistakes that cause access tickets
- Adding people in two places. Someone is in the SharePoint Members group and in the team, then removed from only one. Pick one place per site and stick to it.
- Expecting the team to cover a private channel. Team members aren't automatically members of a private channel, so they can't open its files.
- Looking for "read-only" in the Microsoft 365 group. It isn't there. Use the Visitors group on the site.
- Assuming membership is the only way in. Someone can still have access through a sharing link or a folder with its own unique permissions, no matter what the group says. See sharing links explained.
- Trusting the group name in the permissions panel. The Site permissions panel shows Contoso Marketing Members — Edit, not the people behind it. Nested and Microsoft 365 groups hide more. You need an expanded view to see real users.
A one-line rule for each case
- Team site or a Teams-connected site: manage people in Teams or the Microsoft 365 group. Add read-only people to Visitors.
- Private or shared channel: manage people in the channel.
- Communication site: manage people in the SharePoint Owners, Members and Visitors groups, using security groups for large audiences.
- Any site: remember that links and unique permissions add access that group membership doesn't show.
How to see who is really in the groups
The built-in panel stops at group names. To see every SharePoint group, Microsoft 365 group and security group expanded to individual people, with the permission level and how each person got it, run a permissions report. The free Smart Permissions web part does this inside SharePoint and exports to Excel. Start with how to see who has access to a SharePoint site and how to see who's actually in your Microsoft 365 group, or run a report for one specific person when the question is "why can this user open that?"
Need help untangling a tenant?
If your sites mix all three models and nobody is sure who has access to what, our permissions audit maps it and proposes a clean structure, or you can get in touch.
Related
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.
Frequently asked questions
Are SharePoint groups and Microsoft 365 groups the same thing?
No. SharePoint groups (Owners, Members, Visitors) live inside one site and bundle permission levels. A Microsoft 365 group is a directory-wide membership group that gives people access to a SharePoint site, a mailbox, Planner and more at the same time.
If I add someone to a Teams team, do they get access to the SharePoint site?
Yes. Per Microsoft, team owners become site owners and team members become site members on the team's connected site, and all standard channels use that site.
How do I give someone read-only access to a team's SharePoint site?
Add them directly to the site's Visitors group. Microsoft says Microsoft 365 groups don't have view-only access, so anyone who should only view the site has to be added to the Visitors group on the site itself.
Who can open the files in a private channel?
Only the members of that private channel. The channel has its own SharePoint site, and its permissions are inherited from the channel and can't be managed separately in SharePoint.
What happens if I add someone straight to a team site's Members group in SharePoint?
They get access to the site but not to the other group services such as the team or the group mailbox. Microsoft recommends against managing a group-connected site this way, because it splits access across two places.
Where should I manage permissions for a team site?
In Microsoft Teams or the Microsoft 365 group. Use SharePoint groups directly only for communication sites, or for the Visitors group on a team site.
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
OneDrive vs SharePoint vs Teams: Where Should Files Live?
Teams files are SharePoint files, chat files are OneDrive files, and the right home depends on who owns the work. A simple rule and the facts behind it.
SharePoint Permission Levels Explained: Owners, Members, Visitors and Limited Access
Owners, Members and Visitors are groups. Full Control, Edit and Read are the permission levels behind them. Here is how they fit together, and why Limited Access keeps appearing.
Why Can't I Access This SharePoint Site? "Access Denied" and "You Need Permission" Explained
Seven real causes behind "access denied" and "you need permission", how to tell which one you have from the message, and the fix for each, for users and admins.
Want our team to do it for you? If you would rather not run this yourself, our team can run your permissions audit using the free tools on this site. You get hands-on help and no software license to buy. Talk to us
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.
