What Is a SharePoint Site Collection? Sites, Subsites and Hubs Explained

What Is a SharePoint Site Collection? Sites, Subsites and Hubs Explained

What a SharePoint site collection is in SharePoint Online and Server, how it compares with sites, subsites and hub sites, limits and how to create one.

In this article

Let's Discuss your tech Solution

book a consultation now
November 02, 2026
Author Image
Sharjeel Hashmi
SharePoint & .NET Team Lead
Sharjeel Hashmi is a SharePoint & .NET Team Lead at Centric, with extensive experience in designing, developing, and leading enterprise-level solutions. He specializes in building scalable SharePoint platforms and robust .NET applications that align technology with business objectives. With a strong focus on collaboration, performance, and security, Sharjeel leads teams to deliver high-quality solutions while driving continuous improvement and best development practices. His expertise spans solution architecture, team leadership, and modern Microsoft technologies, enabling organizations to streamline processes and achieve long-term digital success.

A SharePoint site collection is a top-level site plus any subsites under it, managed as one unit for permissions, features, storage and administration. In SharePoint in Microsoft 365, each modern team or communication site is its own site collection, so Microsoft now simply calls them "sites" and connects them with hub sites instead of subsites.

Key Takeaways

  • A site collection is the unit SharePoint uses for administration, security, features and storage.

  • In SharePoint in Microsoft 365, every team or communication site is its own site collection, and Microsoft now calls them "sites".

  • Microsoft reports more than 2 million SharePoint sites created every day (Microsoft, 2026), so structure decisions scale quickly.

  • Microsoft recommends a flat structure: one site per topic or team, grouped with hub sites, not subsites.

  • Each site can hold up to 25 TB, and an organization can have up to 2 million sites (Microsoft Learn, 2026).

  • Clean site-level permissions matter more than ever, because SharePoint is the number one grounding source for Microsoft 365 Copilot (Microsoft, 2026).

In this guide

  • What is a SharePoint site collection?

  • SharePoint site collections by the numbers (2026)

  • How does a site collection work in SharePoint Server and Microsoft 365?

  • What is the difference between a site collection, site, subsite and hub site?

  • Who manages a site collection?

  • Why do separate site collections matter?

  • When should you create a new site collection?

  • How do you create a site collection in SharePoint Online?

  • Examples of site collection structures

  • How do you measure a healthy site structure?

  • Common mistakes to avoid

  • SharePoint site collection checklist

  • Frequently asked questions

SharePoint operates at a scale few platforms match: Microsoft says it serves "more than 1 billion users each year" and sees "over 2 billion files uploaded and 2 million SharePoint sites created every day" (Microsoft, 2026). With that much content being created, the way sites are structured decides whether people can find information and whether access stays under control.

The term "site collection" still causes confusion because it means slightly different things in SharePoint Server and SharePoint in Microsoft 365. This guide explains both, compares site collections with sites, subsites and hub sites, lists the current limits, shows how to create and govern sites, and gives a checklist you can use for your own tenant.

What Is a SharePoint Site Collection?

A SharePoint site collection is a container that groups a top-level site and any sites below it so they can share administration, security settings, features and storage. In SharePoint in Microsoft 365, each modern site is created as its own site collection, so the container and the site are usually the same thing.

Microsoft's SharePoint Server documentation defines it this way: "A site collection is made up of one top-level site and all sites below it." It is "the top level of organization in a SharePoint Server web application," and "all content in a site collection must be stored in a single content database" (Microsoft Learn).

In SharePoint in Microsoft 365, the admin center now describes creating "sites (formerly known as 'site collections')" (Microsoft Learn). The structure still exists underneath, but the word rarely appears in the interface.

Three common misunderstandings:

  • Site collections are gone in SharePoint Online: Site collections still exist. Every modern site is a site collection with its own URL, admins, storage and settings.

  • A site collection is a folder of many sites: In modern SharePoint, most site collections contain one site. Grouping happens with hub sites, not nesting.

  • Subsites are the way to organize an intranet: Microsoft states that "in the modern SharePoint experience, subsites aren't recommended" (Microsoft Learn).

SharePoint Site Collections by the Numbers (2026)

The figures below show the scale SharePoint runs at and the limits that shape how you plan site collections. Usage figures come from Microsoft's own announcements, limits come from the SharePoint service description on Microsoft Learn, and the security figure comes from Microsoft's 2026 Data Security Index survey.

Statistic

What it means

Source

More than 1 billion users each year

SharePoint is a core platform for most Microsoft 365 organizations

Microsoft, 2026

2 million SharePoint sites created every day

Site sprawl is a real governance risk without creation rules

Microsoft, 2026

Over 2 billion files uploaded every day

Structure and metadata decide whether content can be found

Microsoft, 2026

Up to 2 million sites (site collections) per organization

The number of sites is rarely the constraint; governance is

Microsoft Learn, 2026

25 TB of storage per site

One site can hold a very large library, but large sites are harder to govern

Microsoft Learn, 2026

Up to 2,000 hub sites per organization

Hubs can model every department, region or program

Microsoft Learn, 2026

Deleted sites retained for 93 days

Admins have a fixed window to restore a site deleted by mistake

Microsoft Learn

32% of surveyed organizations' data security incidents involve generative AI tools

Site-level permissions matter as AI tools read SharePoint content (survey of more than 1,700 security leaders)

Microsoft Data Security Index, 2026

How Does a Site Collection Work in SharePoint Server and Microsoft 365?

In both versions, a site collection is the scope where administration, security, features and storage are applied. SharePoint Server nests subsites inside a site collection within a web application, while SharePoint in Microsoft 365 treats each site as its own site collection and connects related sites through hubs and navigation.

Layer

SharePoint Server

SharePoint in Microsoft 365

Top container

Farm and web application

Microsoft 365 tenant

Site collection

Top-level site plus subsites, stored in one content database

Called a "site": usually one team or communication site

Grouping

Subsites inside the collection

Hub sites that link independent sites

Administration

Site collection administrators and farm administrators

Site admins (formerly site collection admins) and SharePoint Administrators

Storage

Content database capacity managed by the farm

Pooled tenant storage, up to 25 TB per site

Navigation

Site collection navigation

Global navigation from the home site, hub navigation and local navigation

Microsoft notes that, for site collection administrators, "security, policies, and features can be managed for a whole site collection," along with shared site columns, content types and navigation. Good site structure also underpins SharePoint document management, because libraries, metadata and retention all live inside a site.

Site collection features are switched on or off per site. Microsoft's support guidance places them under Site settings, then Site Collection Administration, then Site collection features, and notes that most of them are off by default (Microsoft Support).

What Is the Difference Between a Site Collection, Site, Subsite and Hub Site?

A site collection is the administrative container; a site is the workspace people use; a subsite is a site nested inside another site's collection; and a hub site connects independent sites with shared navigation, theme and search. In SharePoint in Microsoft 365, the site and site collection are usually the same object.

Term

What it is

When to use it

Site collection (site)

An independent container with its own URL, admins, permissions and storage

Each team, department, project or communication portal

Subsite

A site nested inside a site collection, reflected in the URL

Rarely in new designs; mainly legacy or SharePoint Server environments

Hub site

A site that connects other sites with shared navigation, theme and search

Grouping related sites, such as all HR or all regional sites

Home site

The intranet landing site that enables global navigation

The single front door to your intranet

Microsoft explains the move away from subsites in its hub site guidance: "subsites don't give any room for flexibility and change," because they are "a physical construct reflected in the URL," and "many features (including policy features like retention and classification) in SharePoint apply to all sites within the site collection, whether you want them to or not." Microsoft recommends "using hub sites going forward to organize the sites in your intranet" (Microsoft Learn).

Two hub rules shape every design. Each site can belong to only one hub at a time, and hub association does not change site permissions; content shown on a hub is security trimmed, so people only see items they already have access to.

Who Manages a SharePoint Site Collection?

Site admins manage a site collection. Microsoft describes them as having "the highest level of SharePoint permissions," with the same Full Control as site owners plus control of search, the recycle bin and site collection features. SharePoint Administrators manage all sites across the tenant from the SharePoint admin center.

Role

Scope

What they can do

SharePoint Administrator

Whole Microsoft 365 tenant

Create sites, change storage, register hubs, add or remove site admins

Site admin (formerly site collection administrator)

One site collection

Full Control plus search settings, recycle bin and site collection features; access to all items, even where inheritance is broken

Site owner

One site

Full control of the site; group owners are added automatically on group-connected team sites

Site member

One site

Edit permissions: add and remove files, lists and libraries

Site visitor

One site

View-only permissions

Role descriptions from Microsoft Learn, site permissions. For a deeper walkthrough, see our SharePoint site permissions tutorial.

Why Do Separate Site Collections Matter?

Separate site collections give each team, project or department its own security boundary, settings and owners. That separation keeps sensitive content contained, lets you reorganize navigation without moving content, and lets governance policies match the risk of each site instead of applying one rule to everything.

1. Clear security boundaries

Each site has its own admins and permissions, so access to HR, Finance or Legal content can be managed without affecting other sites.

2. Flexible structure

Independent sites can move from one hub to another when the business reorganizes, without changing their URLs or breaking links.

3. Targeted governance

Retention, sensitivity labels, sharing settings and storage limits can be set per site instead of being forced on everything under one collection.

4. Safer AI adoption

Microsoft states that Copilot "only surfaces organizational data to which individual users have at least view permissions" (Microsoft Learn), and Microsoft calls SharePoint "the number one grounding source for Microsoft 365 Copilot" (Microsoft, 2026). Tight site-level permissions reduce the chance of AI surfacing content to the wrong people.

5. Easier recovery and ownership

Deleted items stay in the recycle bins for 93 days, deleted sites can be restored within 93 days, and every site has named owners for reviews and lifecycle decisions.

When Should You Create a New Site Collection?

Create a new site collection when content has a distinct owner, audience, permission need or lifecycle. Microsoft's guidance is to "create one site for each discrete topic, task, or unit of work," then connect related sites with a hub. Use a library or folder instead when the content shares the same people and rules.

Situation

Recommended option

Why

A new department or team with its own members

New team site, associated with a department hub

Separate owners and permissions

Company-wide news or policies

New communication site, or the home site

Broad read access, small group of authors

A project with external partners

New site with external sharing enabled only on that site

Keeps external access away from internal content

Confidential HR, legal or board content

New restricted site

Separate security boundary and sensitivity label

A new document type for an existing team

New library in the existing site

Same people and rules; no new site needed

Grouping several related sites

Hub site

Shared navigation and search without nesting

For external collaboration, see how to share a SharePoint site with external users.

How Do You Create a Site Collection in SharePoint Online?

Create a site collection in SharePoint Online from the SharePoint admin center: open Active sites, select Create, choose a team or communication site and template, then enter the name, owner and language. A user needs at least SharePoint Administrator permissions to create sites from the admin center.

  1. Sign in to the SharePoint admin center with at least SharePoint Administrator permissions.

  2. Go to Active sites and select Create.

  3. Choose Team site (connected to a Microsoft 365 group), Communication site, or Browse more sites.

  4. Pick a template and select Use template.

  5. Enter the site name, owner, language and other settings, then select Create site.

  6. Open the site's Membership panel in Active sites to add site admins.

  7. Associate the site with the right hub so it picks up the hub's navigation and theme.

Steps from Microsoft Learn: create a site and manage site admins. If the chosen address already exists, SharePoint changes it automatically, for example from /sites/marketing to /sites/marketing2.

Explore Our SharePoint Consulting Services!

Tool

Use it for

SharePoint admin center (Active sites)

Creating sites, adding site admins, changing storage, registering hubs

Site templates

Starting team and communication sites with a standard layout

SharePoint Online Management Shell or PnP PowerShell

Creating and configuring many sites consistently

Site, hub and global navigation

Connecting related sites without nesting

Admin center policies

Site creation settings, sharing limits and inactive site reviews

Moving from SharePoint Server or a subsite-heavy tenant? See our SharePoint migration and integration services.

Examples of Site Collection Structures

Most organizations combine a home site, a small number of hubs and many independent team or communication sites. The four models below cover the most common patterns for US mid-market and enterprise intranets, and many organizations use two or three of them together.

  • Department model: one site per department (HR, Finance, IT), all associated with a "Departments" hub.

  • Project model: one team site per project, connected to a "Projects" hub and archived when the project ends.

  • Regional model: one communication site per region, associated with a regional hub, linked from the home site's global navigation.

  • Secure content model: separate sites for board, legal or HR case files, with restricted permissions and no external sharing.

Microsoft assigns clear owners to each level: intranet owners set overall direction, hub owners manage hub content and navigation, and site owners manage site-level content and permissions (Microsoft Learn). For a full intranet plan, see Centric SharePoint 365 intranet services.

How Do You Measure a Healthy Site Structure?

Measure site structure health with a short set of governance KPIs: ownership, sprawl, hub coverage, sharing exposure and storage. Review them every quarter so problems such as ownerless sites or old external shares are fixed before they turn into security or compliance issues.

Area

KPI

What it shows

Ownership

Sites with at least two active owners

Whether every site has accountable people

Sprawl

Inactive sites older than your review threshold

Whether lifecycle reviews are working

Structure

Sites associated with a hub

Whether navigation and search are connected

Security

Sites with external sharing enabled; open access review items

Exposure of sensitive content

Storage

Sites near their storage limit

Where clean-up or archiving is needed

For automated governance across many sites, Centric offers Centric Governance Central, and AI content features are covered in our guide to implementing SharePoint Premium AI content management.

Common Mistakes to Avoid

Most SharePoint structure problems come from habits carried over from older versions: deep subsite trees, permissions given to individuals, and sites created without owners or naming rules. The table lists the most common mistakes, why each one hurts and what to do instead, so you can check your own tenant against it.

Mistake

Why it hurts

What to do instead

Building new intranets with deep subsites

Reorganizations break URLs and policies apply to everything below

Create independent sites and connect them with hubs

Giving permissions to individuals

Access becomes impossible to review

Use Microsoft 365 groups or SharePoint groups

No creation rules

Duplicate and ownerless sites pile up

Set who can create sites, naming rules and templates

One owner per site

Sites become orphaned when people leave

Require at least two owners

External sharing on by default everywhere

Confidential content can leave the organization

Allow external sharing only on sites that need it

Ignoring inactive sites

Old content clutters search and AI answers

Run inactive site reviews and archive or delete

SharePoint Site Collection Checklist

Use this checklist before creating new sites or restructuring an existing tenant. Each item maps to a Microsoft recommendation or a common failure point, and together they cover naming, ownership, permissions, external sharing, sensitivity labels, legacy subsites and regular quarterly reviews.

  • Agree internal names for site, hub and home site, and document them.

  • Define which roles can create sites and which templates they use.

  • Set a naming convention for site names and URLs.

  • Plan hubs for departments, regions or programs before creating sites.

  • Assign at least two owners and one site admin to every site.

  • Use groups, not individuals, for permissions.

  • Restrict external sharing to the sites that need it.

  • Apply sensitivity labels and retention to confidential sites.

  • Plan to move legacy subsites into their own sites.

  • Review ownership, inactivity and sharing every quarter.

Book A Free Call Now!

Frequently Asked Questions

What is a site collection on SharePoint?

A site collection is a top-level SharePoint site and any subsites under it, managed as one unit for permissions, features and storage. In SharePoint in Microsoft 365, each modern team or communication site is its own site collection, which is why Microsoft now calls them sites.

What is the difference between a SharePoint administrator and a site collection administrator?

A SharePoint Administrator manages SharePoint across the whole Microsoft 365 tenant from the admin center. A site admin, previously called a site collection administrator, has full control of one site plus search, recycle bin and site collection feature settings, and can be added by a SharePoint Administrator.

Do site collections still exist in SharePoint Online?

Yes. Site collections still exist in SharePoint Online, but Microsoft now calls them sites. Each team or communication site created in the SharePoint admin center is a separate site collection with its own URL, site admins, permissions, storage and settings.

How do I copy a SharePoint site to another site collection?

SharePoint has no single button that copies a whole site with all its content. Teams usually recreate the structure with a site template or PowerShell, then move or copy the files and lists, or use a migration tool when the full content and permissions must be moved.

What is the best way to organize a SharePoint site?

The best way to organize SharePoint is a flat structure: one site per team, department or project, grouped with hub sites and a home site for global navigation. Microsoft recommends hub sites instead of subsites because hubs can be reorganized without breaking URLs.

How many site collections can I have in SharePoint Online?

An organization can have up to 2 million sites (site collections) in SharePoint in Microsoft 365, and each site can store up to 25 TB, according to Microsoft's SharePoint limits. Total storage for the tenant depends on licenses, starting at 1 TB plus 10 GB per license.

Can a site belong to more than one hub?

No. A SharePoint site can be associated with only one hub at a time. Content from a site can still appear on several hubs through links and web parts, and hubs can be connected to each other through hub-to-hub associations and navigation.

Final Thoughts

A site collection is still the core building block of SharePoint, even though Microsoft 365 calls it a site. Keep sites independent, group them with hubs, give every site clear owners and group-based permissions, and review ownership and sharing regularly. That structure scales with your organization and keeps content safe as Copilot and other AI tools read more of it. Centric provides SharePoint consulting covering strategy and planning, intranet design, migration and integration, and document management, which are the areas where site structure decisions get made. Its teams also built Centric Governance Central, a product for managing ownership, permissions and lifecycle across many SharePoint sites.

Contact_Us_Op_02
Contact us
-

Spanning 8 cities worldwide and with partners in 100 more, we're your local yet global agency.

Fancy a coffee, virtual or physical? It's on us – let's connect!

Contact us
-
smoke effect
smoke effect
smoke effect
smoke effect
smoke effect

Spanning 8 cities worldwide and with partners in 100 more, we're your local yet global agency.

Fancy a coffee, virtual or physical? It's on us – let's connect!