Page
Common Use Cases
- Intranet content pages: informational pages for policies, procedures, and guidance
- Landing pages: entry points for departments, projects, or initiatives
- Knowledge base articles: how-to content, FAQs, and reference documentation
- Campaign and announcement pages: change management, launches, or internal programs
- Department and team content: supporting pages linked from Team or Communication Sites
- Rich storytelling: combine text, images, video, and web parts into a single experience
Benefits
- Modern authoring experience: easy, no-code page creation directly in the browser
- Automatically created homepage: every new site includes at least one page (the homepage)
- User-created pages: additional pages can be created by users as needed
- Flexible layouts: multi-column sections, full-width layouts, and vertical sections
- Web Part driven: mix and match web parts to build rich, dynamic content
- Version history: track changes and restore previous versions when needed
How It Works
- Homepage included: every site starts with one page, the homepage, and authors add more pages or copy existing ones as the site grows
- Draft first: a new page begins as a private draft visible only to its author, then becomes a shared draft that anyone with edit permissions can see and work on
- Publish to go live: publishing makes the page visible to all site visitors, and later edits stay hidden as a new draft until the page is republished
- Sections and web parts: pages are assembled from one to three column, full-width, and vertical section layouts filled with web parts for text, images, news, events, and documents
- News promotion: any page can be promoted to a news post, which pushes it to the News web part, the SharePoint start page, hub news rollups, and Viva Connections
- Co-authoring: several people can edit the same page at the same time on sites that support simultaneous editing
- Version history: every save creates a version, so editors can compare drafts and restore an earlier version of the page at any time
Limits and Nuances
- Site-bound: pages exist only inside a site, stored in its Site Pages library, and cannot be created as standalone objects outside SharePoint
- Open by default: pages inherit the parent site’s permissions, so anyone in the Site Members group can add, edit, and delete them; set the Site Pages library permission for Members to Read to restrict authoring to owners and designated authors
- Published version only: visitors see the last published version; saved edits remain an invisible draft until someone republishes the page
- Scheduling and approval are opt-in: a site owner must enable scheduling on the Site Pages library (it is not available on subsites), and an optional Power Automate approval flow can require sign-off before pages go live
- Protected homepage: the page set as the site’s homepage cannot be deleted; make another page the homepage first, then delete the old one
- Templates are site-specific: a page template saved on one site does not appear on any other site, so recreate shared layouts per site
- Per-page options: each page header offers layout choices, a custom banner, a changeable displayed author, and the option to show or hide the published date, and comments are on by default (turn them off per page or tenant-wide)
- Keep pages lean and consistent: there is no hard cap on web parts per page, but heavy pages load slowly, so keep high-traffic pages like the homepage lean and use page templates to keep authors on rails
Common Questions About Pages
What is a page in SharePoint?
A page is the modern content canvas of a SharePoint site – a browser-based layout made of sections and web parts that presents text, images, video, documents, and dynamic content. Every site includes at least one page (the homepage), and authors can add as many more as they need for news, policies, knowledge articles, and landing pages, all without writing any code.
Where are SharePoint pages stored?
Every page lives in the Site Pages library of its parent site. Because the Site Pages library is a regular library, pages get version history, permissions, and metadata like any document. Pages cannot exist outside a site – they always inherit the permissions and navigation of the site that contains them, which keeps access management simple and predictable.
Who can create and edit pages on a site?
Out-of-the-box, anyone in the Site Members group can create, edit, and delete pages. If that is too open for an intranet, set the Site Pages library permission for Members to Read so only owners and designated authors can publish, or have a tenant admin switch off page creation for the entire tenant.
What is the difference between a page and a news post?
A news post is just a page with extra distribution. When you publish a page with Post news, it appears in the News web part, on the SharePoint start page, in hub news rollups, and in Viva Connections. Regular pages stay put and are reached through navigation and links, which makes them better for evergreen content like policies and reference material.
Can I schedule a SharePoint page to publish later?
Yes. A site owner first enables scheduling on the Site Pages library, and then authors can set a future publish date and time in the page details. If page approval is also configured, the page must be approved before the scheduled time for it to go live. Note that scheduling is not available on subsites.
How do I keep pages consistent across an intranet?
Use page templates so authors start from an approved layout instead of a blank canvas, limit who can create pages, and add an approval flow for news. Consistency is what separates a polished intranet from a cluttered one – the intranet examples on LookBook 365 were all built by Greg Zelfond using out-of-the-box pages and web parts, with no custom code.