Site Collection in SharePoint: Modern Definition and Guide
A site collection is a SharePoint administrative and content boundary built around a top-level site and, in older or specific designs, any subsites beneath it. In modern SharePoint Online, each team site and communication site is normally its own site collection, and hub sites connect related collections without turning them into one permission hierarchy.
What Site Collection Means in SharePoint
The term site collection comes from SharePoint's underlying architecture and remains common in administration, migration, APIs, and technical discussions. Users may simply see a site, but administrators use the collection boundary to understand where settings, administrators, content types, features, and permissions are scoped.
Modern information architecture favors a flatter model: create separate sites for separate units of work, then use hub associations and navigation to express relationships. This is more flexible than placing every department and project under one permanent subsite tree, because a site can change hub association as the organization changes.
Why It Matters to the Business
Business leaders do not need to manage the technical object, but they should understand its effect on ownership and change. A collection boundary makes it easier to give a project or department clear accountability, apply appropriate policies, and move or reorganize relationships without redesigning an entire hierarchy.
During migration, the source system's hierarchy should not automatically dictate the destination. Legacy subsites may represent real business boundaries that deserve separate modern sites, while other sites may be duplicates or abandoned. Mapping these decisions before moving content reduces inherited complexity.
What SharePoint Administrators Need to Know
Administrators should document site collection administrators, hub association, sharing posture, sensitivity, lifecycle, and any exceptions. A hub association does not merge permissions: users need access to each associated site, and content rollups remain security trimmed according to their existing rights.
Technical teams should also distinguish a site collection from tenant-wide configuration. Search schema, term sets, content types, and other features can have tenant and site scopes. Knowing the boundary prevents a local change from being mistaken for an organization-wide standard—or the reverse.
What to Consider
Prefer flexible relationships
Use hubs to connect autonomous sites when the business relationship may change; avoid making URL hierarchy the only representation of the organization.
Reassess legacy subsites
Before modernization, determine whether each subsite should become a separate site, merge with another destination, remain temporarily, or be retired.
Keep administration explicit
Record responsible administrators and owners for every modern site collection, especially after migrations, reorganizations, or staff departures.
Practical Takeaway
Treat a site collection as a governable unit of work, not as a branch that must remain forever in a rigid corporate tree.
How This Shows Up in the Field
Organizational change
A compliance site can move from a Legal hub to an Enterprise Risk hub without moving its content into a new subsite path or inheriting the hub site's permissions.
Modernization assessment
A legacy portal with dozens of subsites can be decomposed into owned communication and team sites, associated to hubs by function, while obsolete areas are archived instead of migrated.
Site collection, subsite, and hub
| Site collection | A top-level SharePoint site boundary with its own administration and settings; most modern sites in SharePoint Online are separate site collections. |
|---|---|
| Subsite | A site created beneath another site within the same collection, historically used to build fixed hierarchies and inherit settings or permissions. |
| Hub site | A registered site that connects separate sites through navigation, branding, search scope, and rollups without creating a parent-child permission structure. |
Related 6SC Services and Proof
Related SharePoint Glossary Terms
Frequently Asked Questions
Is every modern SharePoint site a site collection?
Modern team sites and communication sites are normally created as separate site collections. The interface often calls them sites, but the collection concept remains important for administration, migration, permissions, APIs, and feature scope.
Does associating a site with a hub change its permissions?
No. Hub association connects navigation, branding, search scope, and content rollups, but it does not automatically grant access to associated sites. Each site keeps its own permission model and security-trimmed content.
Are subsites obsolete in SharePoint Online?
Subsites still exist in supported scenarios, but modern architecture generally favors separate sites connected through hubs. Separate sites are easier to reorganize, govern, archive, and assign to distinct owners than a deep inherited hierarchy.
Why does site collection planning matter during migration?
A migration can either remove or preserve structural debt. Reviewing purpose, ownership, access, and lifecycle helps determine which legacy subsites become modern sites, which content consolidates, and what should be archived or deleted.
Official Microsoft References
- Planning your SharePoint hub sites
- Introduction to SharePoint information architecture
- Default SharePoint groups and site administrators
Editorial review date: July 13, 2026. Product status and licensing can change; confirm current Microsoft documentation before implementation.
Modernize your SharePoint site structure
6SC can inventory legacy collections and subsites, design a flat hub architecture, clarify ownership, and map content into a cleaner Microsoft 365 environment.
Talk with 6SC