Skip to content
home

SharePoint Intranet Examples: 9 Layouts That Work (2026)

A good SharePoint intranet is not one big site. It is a small set of sites, each with one job: a home page everyone opens, a few department hubs, and libraries where the current version of every document is easy to find. Below are nine layouts I build again and again for clients, starting with a real one, and what goes on each page so you can copy the parts you need.

Quick answer

Real SharePoint intranet examples: a company home page, HR hub, policy library, department and project sites, onboarding and mobile, with what each page needs.

Daniel AwokunleDaniel AwokunleUpdated 19 November 2026 8 min read
Watch first: the whole guide in 100 secondsFull steps below
Video transcript

Looking for SharePoint intranet examples people actually open? Here are the ones that work.

Meet Olivia, head of operations at Harlow and Pine in Toronto. Their intranet is a page of links from twenty nineteen. Zero visits this week. Her CEO asks: show me what a good one looks like.

First, the company home page. Big news at the top, quick links to the tasks people do every day, and what's coming up. It fits on one screen.

Second, an HR and people hub. The handbook as pages, who's who, and the request forms. Contracts and salaries stay in a separate, locked site.

Third, a policy library with columns instead of folders. Owner, department and review date. One click shows every policy that's due for review.

Fourth, department sites joined to one hub. Each team owns its own site, and the hub shares the navigation and search.

Fifth, an onboarding hub. New starters get a checklist, and Power Automate reminds their manager when something is due.

Sixth, mobile. Frontline staff see the same news and links inside Teams on their phone, with Viva Connections. No new app to learn.

My tip: start with three. The home page, the HR hub and the policy library. Then check that your top ten staff questions are answered within two clicks.

The full guide, with all nine examples, is free at winstack365.com.

1. Company home page (the front door)

This is the page set as the start page for everyone. It answers three questions in seconds: what's happening, where do I go for X, and who do I ask.

  • Top: company news, three to five stories, with the newest one large.
  • Quick links to the ten tasks people do most: book leave, submit expenses, IT help, find a policy.
  • Upcoming events and a short 'new starters' strip.
  • Search box in the header, so people search the whole intranet from one place.

Real example: NJF Connect, an intranet I built for NJF, uses exactly this pattern: branded home page, quick-task tiles, company news and events. The full case study with screenshots is on the Samples page of this site.

2. HR and people hub

The most visited site after the home page. It holds the staff handbook, policies, benefits, the org chart and the forms people need for leave, expenses or changes to their details.

  • Handbook and policies as SharePoint pages, not PDFs, so they are searchable and always current.
  • People web part or org chart for who's who.
  • A Forms or Power Apps link for requests, with approvals handled by Power Automate.

Keep salary, contracts and case files out of this site. They belong in a separate, locked-down HR site that only the HR team can open.

3. Policy and procedure library

One document library with metadata columns instead of folders: policy owner, department, review date and status. Views filter by department, and an 'expiring soon' view shows what needs review.

Turn on versioning and approval so only the approved version shows to staff. A short Power Automate flow can email the owner 30 days before the review date.

4. Department sites under a hub

Finance, Operations, Sales and IT each get a communication site joined to one hub. The hub gives them shared navigation, branding and search, so the intranet feels like one place even though each team owns its own site.

Each department page follows the same simple template: what we do, how to ask us for something, key documents, and the team.

5. New-starter onboarding hub

A site a new hire opens on day one: a welcome video, a first-week checklist, who to meet, IT setup steps and links to the systems they will use.

Pair it with a SharePoint list of onboarding tasks per starter. Power Automate creates the tasks when HR adds a new person and reminds managers about anything overdue.

6. Project or client site template

For firms that run projects or client matters, one template site per project keeps files, decisions and status together. A provisioning flow or site template creates each new site with the same libraries, columns and permissions.

Link each project site to a Team, so chat happens in Teams and the files stay organised in SharePoint underneath.

7. Contract or document register

A library where every contract has vendor, start date, end date, value band, status and owner as columns. NJF Connect's Contract Library works this way. Views show contracts by status and renewals due, and a flow warns the owner before a renewal date.

8. Mobile and frontline intranet

For staff who work from a phone, the intranet appears inside Teams through Viva Connections. They get the same news and quick links in a mobile-friendly dashboard, without learning a new app.

Keep the mobile view short: news, the five links frontline staff actually use, and shift or safety notices.

9. Team space for one office or location

Multi-site businesses often add a small page per office: local contacts, opening hours, parking, local news and the noticeboard. It reduces 'who do I ask in Leeds?' emails and makes remote offices feel included.

Which examples need which SharePoint parts

ExampleSite typeMain web parts or tools
Company home pageCommunication site (hub)News, Quick links, Events, Highlighted content
HR and people hubCommunication sitePages, People, Document library, Forms link
Policy libraryLibrary in HR or hub siteMetadata columns, views, versioning, approval
Department sitesCommunication sites joined to hubHub navigation, News, Quick links
Onboarding hubCommunication siteVideo, list of tasks, Power Automate reminders
Project or client sitesTeam site from a templateLibraries with columns, Teams link, provisioning flow
Contract registerLibraryMetadata columns, views, renewal flow
Mobile intranetViva Connections in TeamsDashboard cards, News, Quick links
Office pagesPages in the hubText, Events, Contacts

Where to start

Most companies should start with three: the home page, the HR hub and the policy library. Together they answer most of the questions people currently send by email. Add department sites once those three are used every day, and the rest as real needs appear.

Before building, list the ten questions staff ask most and check every one is answered within two clicks of the home page. That single test does more for adoption than any design choice.

Frequently asked questions

Is SharePoint good for a company intranet?

Yes, for most companies already on Microsoft 365. It is included in Business and Enterprise plans, works with Teams and Outlook, respects the permissions you already have and works on phones through the SharePoint app and Viva Connections.

Are there free SharePoint intranet templates?

Yes. SharePoint includes site templates such as Department, Human resources, Event and Crisis management, and the Microsoft SharePoint look book has more designs you can add to your tenant. They are a good start, but you still need to plan navigation, permissions and content owners.

How long does it take to build a SharePoint intranet?

A home page, HR hub and policy library can go live in two to four weeks for a small or mid-sized business, once the content is ready. Larger intranets with many departments take longer, mostly because of content clean-up rather than building.

Do I need SharePoint developers for an intranet like these?

Not for most of it. Every example on this page uses standard SharePoint pages, web parts, lists and Power Automate. Custom code is only needed for unusual designs or integrations.

Want this done for you?

I build this for clients every week. Book a free 30-minute call and I'll tell you exactly what your team needs.

Free: the Microsoft 365 clean-up checklist

The 12 checks I run before building anything in a client's tenant: security, sharing, files and quick wins. Two pages, PDF.

Used only to send the checklist and the odd useful tip. Never shared or sold.

Daniel Awokunle · replies within a day

Tell me what's slowing your team down.

Thirty minutes, no cost, no pitch deck. You'll leave knowing exactly what to build and what it should cost.

Book a free 30-min call
  1. Step 1

    Free 30-min call

    Show me the problem. I'll tell you what I'd build and how long it takes.

  2. Step 2

    Clear quote

    A fixed price and timeline in writing, usually within a day.

  3. Step 3

    Built and handed over

    Built in your own Microsoft 365, with a walkthrough for your team.