A useful SharePoint knowledge base is a governed collection of modern pages, not a large folder labelled “Knowledge”. Give every topic an owner, use consistent page fields, provide a clear route from search to answer, and remove or review stale material.
Classic wiki libraries still exist in older sites, but they are not the right default for a new SharePoint Online knowledge base. Modern Site Pages provide responsive authoring, web parts, version history and publishing controls.
Decide what belongs
Write down the reader, the questions the site will answer and what it will not contain.
A support knowledge base might hold procedures, troubleshooting and ownership. It should not quietly become the home for every policy, project file and team note. Those content types have different approval and retention needs.
Choose a communication site when a small author group publishes to a broad audience. Choose a team site when the same group primarily collaborates on the material. Microsoft's modern SharePoint permissions guidance explains the difference.
Build a simple page model
Create a modern page template with:
- a question or task-based title
- a short answer at the top
- prerequisites and permissions
- numbered steps where a procedure is involved
- failure and recovery guidance
- owner, review date and topic
- related pages and primary sources
Modern pages live in the Site Pages library. Add columns there for Topic, Content owner, Review date and Status. Keep required fields limited to information authors will maintain.
Control publication
Use SharePoint Owners for the small group administering the site and Members for approved authors. Visitors should normally read.
Page approval can be configured with Power Automate by a site administrator. Microsoft's page approval guidance notes that it is not available in government cloud environments.
Approval proves that a named reviewer accepted that version. It does not prove the answer is legally compliant or factually current forever.
Make answers findable
Navigation should reflect common tasks, not the internal organisation chart.
For each important page, confirm an intended reader can open it directly, search for the title and important terms, understand its search summary, and recover a previous version. Also confirm that a user without access does not receive the result.
Search is security trimmed and indexing is not instantaneous. Test direct permission separately from search freshness.
Add review and retirement
Every page needs a human owner and review date. Create a view of overdue pages. Ask owners to confirm, revise, replace or retire each one.
Do not update a review date merely because a reminder fired. A date change without source checking makes the signal meaningless.
Useful measures include failed searches, repeated support questions, pages with no owner and reports that a procedure did not work. Page views show attention, not correctness.
Document how to restore a version, recover a deleted page and replace a departed owner.
This design can create a dependable publishing process. It does not prove that every answer is correct, that search will surface every page immediately or that SharePoint is the right specialist knowledge platform for every organisation.
For help turning scattered SharePoint pages into a supportable knowledge base, join the SharePoint & Teams Admins Space.