Site Collections in SharePoint: Architecture Best Practices

Understanding Site Collections

In SharePoint Online, site collections (now often called "sites" in modern terminology) are the fundamental containers for organizing content, managing permissions, and establishing governance boundaries.

Site Collection Fundamentals

What Is a Site Collection?

A site collection is:

• Top-level container in SharePoint
• Security and administrative boundary
• Collection of sites, lists, and libraries
• Separate storage quota
• Independent permission structure

Modern Terminology

Evolution of Terms

• Classic: "Site Collection"
• Modern: "Site"
• Technical: Still site collections underneath
• Admin Center: Shows as "Sites"

Site Collection Components

```

Site Collection

├── Root Site (top-level)

│ ├── Site Pages library

│ ├── Documents library

│ └── Other lists/libraries

├── Subsites (optional)

│ ├── Child Site A

│ └── Child Site B

├── Site Collection Features

├── Content Types (site collection level)

└── Permissions (site collection admins)

```

Architecture Considerations

Flat vs. Hierarchical

Flat Architecture (Recommended)

• Hub sites for organization
• Independent sites associated to hubs
• Each site is a site collection
• Modern, scalable approach

Hierarchical (Legacy)

• Parent/child subsite relationships
• Inherited navigation
• Complex permission inheritance
• Limited scalability

Hub Sites

Hub Site Benefits

• Logical organization without hierarchy
• Shared navigation
• Aggregated content (news, search)
• Consistent branding
• Easy reorganization

Hub Structure Example

```

Intranet Hub

├── HR Site (associated)

├── IT Site (associated)

├── Marketing Site (associated)

└── Finance Site (associated)

Projects Hub

├── Project Alpha (associated)

├── Project Beta (associated)

└── Project Gamma (associated)

```

Planning Site Collections

Decision Framework

Create New Site Collection When

• New team/project needs workspace
• Different security requirements
• Separate governance needs
• Distinct content domain

Don't Create When

• Content fits existing site
• Would fragment information
• Creates unnecessary complexity
• Subsite would suffice (rare)

Naming Conventions

URL Naming

```

Good: /sites/marketing

Good: /sites/project-alpha

Good: /teams/hr-benefits

Bad: /sites/Marketing_Department_2024

Bad: /sites/john-project

Bad: /sites/new-site

```

Guidelines

• Lowercase with hyphens
• Short and meaningful
• No spaces or special characters
• Consistent pattern across org

Site Types

Communication Sites

• Broad audience broadcast
• Polished pages
• No M365 Group
• Public or private

Team Sites

• Collaborative workspaces
• Connected to M365 Group
• Private by default
• Teams integration

Creating Site Collections

Admin Center

Steps

• SharePoint Admin Center
• Sites > Active sites
• Create
• Select template
• Configure settings:
• Name and URL
• Owner
• Language
• Time zone
• Advanced: Hub association, storage

PowerShell

Create Communication Site

```powershell

New-PnPSite -Type CommunicationSite -Title "Marketing" -Url "https://contoso.sharepoint.com/sites/marketing" -Owner [email protected]

```

Create Team Site

```powershell

New-PnPSite -Type TeamSite -Title "HR Team" -Alias "hr-team" -Owner [email protected]

```

Site Designs

Apply on Creation

• Automate site configuration
• Consistent branding
• Standard lists/libraries
• Governance compliance

Managing Site Collections

Site Collection Administrators

Roles

• Primary Administrator: Main contact
• Site Collection Admins: Full control
• Can add/remove other admins
• Access all site content

Best Practices

• Minimum 2 admins per site
• Use groups where possible
• Regular admin reviews
• Document admin responsibilities

Settings Configuration

Key Settings

• Storage quota
• Sharing level
• External access
• Hub association
• Regional settings

Access Settings

```powershell

# Get site settings

Get-SPOSite -Identity https://contoso.sharepoint.com/sites/marketing | Select-Object *

# Modify settings

Set-SPOSite -Identity https://contoso.sharepoint.com/sites/marketing -SharingCapability ExternalUserSharingOnly -StorageQuota 5120

```

Permissions Architecture

Permission Levels

Default Levels

• Full Control: Complete access
• Design: Create lists, edit pages
• Edit: Add/edit items
• Contribute: Add items
• Read: View only

Permission Inheritance

How It Works

• Sites inherit from site collection
• Libraries/lists inherit from site
• Can break inheritance at any level

Best Practices

• Use groups, not individuals
• Minimize broken inheritance
• Document custom permissions
• Regular permission audits

Security Trimming

What Gets Trimmed

• Navigation links
• Search results
• List views
• Web part content

Content Type Architecture

Site Collection Content Types

Benefits

• Consistent metadata across sites
• Reusable document templates
• Standardized columns
• Workflow integration

Creating Content Types

• Site Settings
• Site Content Types
• Create
• Configure columns
• Publish/syndicate

Content Type Hub

Enterprise Content Types

• Centrally managed
• Syndicated to sites
• Consistent across tenant
• Single source of truth

Site Collection Features

Feature Activation

Common Features

• Publishing features
• Custom scripts
• Site feed
• Workflows

Activation Methods

• Site Settings > Site Features
• Site Collection Features
• PowerShell

```powershell

# Enable feature

Enable-PnPFeature -Identity "feature-guid" -Scope Site

# Disable feature

Disable-PnPFeature -Identity "feature-guid" -Scope Site

```

Governance Framework

Site Lifecycle

Creation

• Request process
• Approval workflow
• Provisioning standards

Active Use

• Content management
• Permission reviews
• Storage monitoring

Archival

• Identify inactive sites
• Archive decision
• Read-only mode
• Retention policy

Deletion

• Confirm no active use
• Backup if needed
• Delete and reclaim storage

Compliance Considerations

Site-Level Compliance

• Retention policies
• Sensitivity labels
• DLP policies
• Audit requirements

Migration Considerations

From Subsites to Sites

Why Migrate

• Modern architecture
• Better scalability
• Hub site benefits
• Feature parity

Migration Approach

• Inventory subsites
• Plan new site structure
• Create destination sites
• Migrate content
• Update links/navigation
• Redirect old URLs

Troubleshooting

Common Issues

"Site Collection Not Found"

• Check URL spelling
• Verify permissions
• Check if deleted

Permission Errors

• Verify group membership
• Check inheritance
• Review custom permissions

Feature Activation Failures

• Check prerequisites
• Review feature dependencies
• Verify admin permissions

Conclusion

Understanding site collection architecture is fundamental to successful SharePoint implementations. By following modern best practices—flat architecture with hub sites, proper planning, and clear governance—organizations can build scalable, manageable SharePoint environments.

Ready to architect your SharePoint environment? Contact our consultants for architecture planning and migration services.