How to Share a SharePoint File with a Group
Group-based sharing is the foundation of scalable permissions. Add someone to the group, they get access to everything the group can see. Remove them, access vanishes everywhere at once.
What it is
Microsoft 365 has multiple kinds of groups: distribution lists, security groups, Microsoft 365 groups (the default behind Teams), and SharePoint groups within sites. They serve overlapping purposes, but for sharing, the principle is the same: grant access to a group, manage membership of that group, and access automatically follows membership.
This is far more scalable than granting individual access. If a team has 30 members and 50 shared files, individual permissions mean 1,500 entries to manage. Group-based permissions mean 50 entries (one per file, granted to the group). Adding a new team member updates all 50 files at once.
For most team sharing, the right approach is to create the file inside a team site (which already has its own group) and let permissions flow from there. For cross-team sharing or specific needs, share with the relevant group rather than naming individuals one by one.
When to use this
- Sharing within a team or department where membership changes regularly.
- Cross-team sharing where you want consistency without manually updating individual access.
- Granting access to roles rather than people (e.g. ‘Project Managers’).
- Anywhere individual sharing would create maintenance burden.
How to do it
- Identify the right group — Microsoft 365 group, security group, or SharePoint group.
- Select the file and click Share.
- Type the group name in the recipients field.
- Set the permission level for the group as a whole.
- Confirm and send.
- When team membership changes, the access updates automatically.
Best practices
- Default to groups for team-wide sharing. Individuals only when there’s a real reason to.
- Use existing groups before creating new ones. Group sprawl is its own problem; reuse where possible.
- Document what each group is for. ‘Marketing team’ is clear. ‘Group_2024_Project_X’ six months later is not.
- Audit group membership. Same principle as auditing file access — but at the group level.
Common mistakes
- Granting individual access when a group would do. Creates maintenance debt that compounds over time.
- Using one big ‘Everyone’ group for everything. Too broad to be useful. Match groups to actual access needs.
- Forgetting to remove people from groups when their roles change. Groups are only as good as their membership.
The Sharing Handbook gives you the Traffic Light System for every SharePoint sharing decision. Real screenshots of the Link Settings dialog, end-user focused, no admin access required.
Get the Sharing Handbook — $27 →FAQ
How do I share a SharePoint file with a Microsoft 365 group?
Click Share, then in the recipient field type the group name (e.g. ‘Marketing Team’). Microsoft 365 groups, security groups, and distribution lists all work. Set permission (View or Edit) and send. Everyone in the group gets access — and as members join or leave the group, their access auto-adjusts. No per-person management.
What’s the difference between sharing with a group vs individuals in SharePoint?
Group sharing follows membership — add someone to the group, they get the file access; remove them, they lose it. Individual sharing is per-person and persists regardless of role changes. Group sharing is the right default for ongoing team access; individual sharing is for one-off targeted access.
Why isn’t my SharePoint group sharing working?
Two common causes: the group is a distribution list (which is just an email alias and has no SharePoint identity — change to a Microsoft 365 group or security group); or the group is mail-enabled but not security-enabled (some older groups can’t be used as SharePoint permission principals). Check group type in Exchange admin.
Should I use Microsoft 365 groups or security groups in SharePoint?
Microsoft 365 groups for team-style sharing where the group has its own Teams, calendar, and SharePoint site. Security groups for permission-only purposes (e.g. ‘IT Admins’) where you don’t need a collaboration space. SharePoint accepts both. The choice usually depends on whether the group needs collaboration features beyond access control.