2.1.3. SharePoint Admin Center: Sites, Libraries, and Permissions
💡 First Principle: SharePoint is Microsoft's document management and collaboration platform. Its admin center manages the structure — sites, libraries, and permissions — while the content itself lives inside those structures. Getting permissions wrong at any level cascades downward to all content beneath it.
SharePoint organizes content in a hierarchy:
Tenant
└── Site Collection (e.g., https://contoso.sharepoint.com/sites/HR)
└── Site (can have subsites, though modern SharePoint avoids these)
└── Document Library (e.g., "Shared Documents")
└── Folders and Files
Permissions in SharePoint follow an inheritance model: by default, a library inherits permissions from its site, and a file inherits from its library. Breaking inheritance at any level creates a custom permission scope — powerful, but a common source of oversharing mistakes.
The SharePoint admin center lets you:
- Create and manage site collections
- Configure tenant-wide sharing settings (who can share with whom, external sharing policies)
- Manage storage quotas per site
- Run data access governance reports (more on this in Phase 3)
- Enable or restrict features like hub sites and site templates
SharePoint roles and permissions:
| Role | Permissions |
|---|---|
| Site Owner | Full control — can manage permissions, delete the site |
| Site Member | Edit — can add, edit, delete content |
| Site Visitor | Read — can view content only |
| Site Collection Administrator | Super-owner — bypasses all permission checks |
External sharing levels. In Policies > Sharing, the organization-level setting is a ceiling: each site can use the same level or a more restrictive one, never a more permissive one. From most to least permissive: Anyone (links that work without signing in), New and existing guests (recipients must sign in or verify with a code; new guests can be invited), Existing guests (only guests already in the directory) and Only people in your organization (no external sharing). Lowering the ceiling below Anyone stops anonymous links from being created anywhere in the tenant while keeping authenticated guest sharing. The default link type (Specific people, People in your organization, or Anyone) is a separate setting that decides which link the Share dialog offers first; Specific people is the most restrictive.
Site creation and site types. Turning off self-service site creation (Settings > Site creation) removes users' option to create sites from SharePoint and OneDrive, so new sites go through IT. It does not stop anyone who can create a Microsoft 365 Group or a team, because every group gets its own site; that is controlled by restricting group creation. A team site is for collaboration — members create and edit content together, and it is usually connected to a Microsoft 365 Group. A communication site publishes to a broad audience: a few authors, many readers.
Site access. A licence and a tenant account grant no access to any particular site. Each site's access comes from its own permissions — its Owners, Members and Visitors groups, or the connected Microsoft 365 Group — so a new person must be added there.
⚠️ Exam Trap: SharePoint permissions and Teams channel permissions are managed separately and can diverge. When you create a Team, a corresponding SharePoint site is created automatically. But if someone is added directly to the SharePoint site without being added to the Team, they can access the files without being a Team member — a common oversharing pathway.
Reflection Question: A file in a SharePoint document library is visible to users who shouldn't have access to it. You check the library permissions and they look correct. What's another permission scope you should check, and why?