Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

4.2.3. SharePoint Sites and Permissions

💡 First Principle: A SharePoint site is a container whose permissions flow down to everything inside it unless someone breaks inheritance. So the safest permission is set once at the site through its groups — owners, members, visitors — rather than item by item.

Creating sites. SharePoint admin center > Sites > Active sites > Create (also reachable from Microsoft 365 admin center > Resources > Sites), as at least a SharePoint Administrator:

  • A team site is connected to a Microsoft 365 group, and membership of the group drives access. Every team in Teams has one.
  • A communication site is for broadcasting to a broad audience — a few authors, many readers — and isn't group-connected.
Default permission groups on a team site:
SharePoint groupPermission level
OwnersFull Control
MembersEdit
VisitorsRead

Other permission levels include Contribute, Design, Approve, Restricted Read and View Only (view without download). Site admins (formerly site collection admins) have full control and can see all content; every site needs a primary admin. For group-connected sites, you manage access mainly through the group's owners and members.

Two defaults with Copilot consequences:
  • On a public Microsoft 365 group-connected team site, Everyone except external users gets Edit access by default — so a public team's files are reachable by everyone in the organization, and by Copilot on their behalf.
  • Permissions for private and shared channel sites are synced from Teams and can't be managed independently in SharePoint.

Sharing settings are set at the organization level and can be made more restrictive per site — from Anyone links, through new and existing guests and existing guests only, down to Only people in your organization.

⚠️ Exam Trap: Making a team public is effectively granting its site to the whole organization. If a scenario says "only the project team should see these files," a public team (or a site shared with Everyone except external users) is the problem, not the solution.

Reflection Question: A department created a public team for confidential budget planning. Explain what everyone in the organization can do with its files, and give two ways to fix it — one quick, one thorough.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned