SharePoint Best Practices

Analogy categoryAnalogies

Information Architecture Foundations

SharePoint Online favors a flat, hub-and-spoke architecture over deeply nested subsites. Each team or project should get its own site collection, associated to a hub site for shared navigation, theming, and search scoping, rather than being buried three levels deep as a subsite. Inside each site, use metadata columns and content types instead of folder hierarchies to organize documents — folders break permission inheritance awkwardly and don't support the filtered, sortable views that column-based metadata does.

🏏

Cricket analogy: It's like the IPL running as independent franchise teams (Mumbai Indians, CSK) under one BCCI hub for scheduling and branding, instead of forcing every player into a single nested club hierarchy.

Establish naming conventions and reusable content types before content starts flowing in — retrofitting them across thousands of existing documents is far more expensive than defining them up front. A content type like 'Project Charter' or 'Client Contract' bundles a document template with a consistent set of columns (Client Name, Status, Review Date), and when defined at the hub level and pushed to associated sites via content type publishing, every site inherits the same structure without manual re-creation.

🏏

Cricket analogy: It's like the ICC defining a standard pitch report template (soil type, grass cover, expected turn) once, so every venue from Lord's to Chepauk fills in the same fields instead of inventing their own format.

Permissions and Governance

Grant access through SharePoint groups (Site Owners, Site Members, Site Visitors) rather than assigning permissions to individual users directly. Direct, one-off permission grants are invisible in bulk audits and multiply quickly, whereas group-based access means adding or removing a person from one group updates their access everywhere that group is used. Avoid breaking permission inheritance on individual libraries or items unless there's a genuine business need — every broken inheritance point is a place where an access review can silently miss someone who shouldn't have access, or block someone who should.

🏏

Cricket analogy: It's like managing team access to the dressing room by squad membership (Test squad, ODI squad) rather than handing individual keys to each player — drop someone from the squad and their access is revoked automatically.

A written governance plan should define site lifecycle (who can create sites, how long an inactive site lives before archival), external sharing defaults (whether guests can be invited, and at what scope — anyone, existing guests only, or organization only), and retention policies applied through the Microsoft Purview compliance center. Without this, organizations accumulate hundreds of orphaned sites with no clear owner, external sharing links that never expire, and no consistent record-retention schedule — all of which become compliance and security liabilities during an audit.

🏏

Cricket analogy: It's like a cricket board setting clear rules for domestic team registration and player eligibility windows, rather than letting anyone form a 'team' with no oversight and no deregistration process.

Performance and List Design

SharePoint lists and libraries enforce a 5,000-item list view threshold — any single query that would need to scan more than 5,000 items in an unindexed way is blocked outright rather than allowed to run slowly. The fix is to add indexed columns on the fields you filter by most often (Status, Department, Due Date) so the query engine can seek directly to matching rows instead of scanning the whole list, and to design views with filters that stay under the threshold by default.

🏏

Cricket analogy: It's like a scorer refusing to manually tally a stat across 5,000 unindexed match records — instead you build an indexed database by season and team so a query like 'Kohli's centuries since 2015' resolves instantly.

powershell

# Connect and provision a new team site associated to an existing hub, with indexed columns
Connect-PnPOnline -Url "https://contoso.sharepoint.com" -Interactive

New-PnPSite -Type TeamSite `
  -Title "Project Falcon" `
  -Alias "project-falcon" `
  -Description "Workspace for the Falcon rollout"

Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/project-falcon" -Interactive

# Associate to the Marketing hub
Add-PnPHubSiteAssociation -Site "https://contoso.sharepoint.com/sites/project-falcon" -HubSite "https://contoso.sharepoint.com/sites/marketing-hub"

# Add an indexed column to keep the library under the 5,000-item view threshold
Add-PnPField -List "Documents" -DisplayName "Status" -InternalName "Status" -Type Choice -Choices "Draft","In Review","Approved"
Set-PnPField -List "Documents" -Identity "Status" -Values @{Indexed=$true}

Hub sites don't just share navigation — they also scope search results and push a consistent theme to every associated site, so users searching from any spoke site see results from the whole hub family by default.

Breaking permission inheritance on a document library or individual item creates a unique permission set that must be maintained manually forever after. At scale, these become the single biggest source of access-review failures and accidental oversharing — prefer separate libraries or sites with clean inheritance over item-level permission breaks.

Use hub sites and flat site collections instead of deeply nested subsites for information architecture.
Prefer metadata columns and content types over folder hierarchies for organizing documents.
Define naming conventions and content types before content creation begins, and publish them from the hub.
Grant access via SharePoint groups, not direct per-user permissions, to keep audits manageable.
Write a governance plan covering site lifecycle, external sharing defaults, and retention policies.
Add indexed columns on frequently filtered fields to avoid hitting the 5,000-item list view threshold.
Avoid breaking permission inheritance except when there is a genuine, documented business need.