Skip to main content

A SharePoint knowledge base works when structure, publishing control and ownership are designed together. Use a communication site with modern pages for articles, a document library for policies and procedures, and lists for short structured entries. Define content types in the Content type gallery so every item carries the same required metadata, attach document templates, and publish them from the content type hub. Require approval through a Power Automate page approval flow or library content approval, set version history limits, map key columns to refinable managed properties for search, and enforce review with owner columns plus SharePoint Advanced Management ownership, inactive site and attestation policies. EPC Group, a Houston-based Microsoft consulting firm, builds this model for regulated organizations.

Key Facts

  • Content types created in the SharePoint admin center are saved to the content type hub at /sites/ContentTypeHub (Microsoft Learn, Create or customize a content type, accessed 2026-10-20).
  • Site owners configure page approval from Pages > Automate > Power Automate > Configure page approval flow (Microsoft Learn, Manage SharePoint page approvals with Power Automate, accessed 2026-10-20).
  • SharePoint approvals are not available in government cloud environments (Microsoft Learn, Manage SharePoint page approvals with Power Automate, accessed 2026-10-20).
  • SharePoint in Microsoft 365 provides unused refinable managed properties, including RefinableString00 to RefinableString219 (Microsoft Learn, Manage the search schema in SharePoint, accessed 2026-10-20).
  • Result types customize only the classic search experience (Microsoft Learn, Manage result types, accessed 2026-10-20).

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

What a SharePoint knowledge base is built from

A knowledge base in SharePoint is not a single feature. It is a site design that combines modern pages for articles, a document library for controlled documents, content types that force consistent metadata, an approval step before anything reaches readers, search that understands that metadata, and named owners who review content on a schedule. Each of those parts is a standard SharePoint capability documented on Microsoft Learn; the work lies in choosing which to use for which content and in configuring them so they hold up after launch. Organizations replacing a classic wiki, a file share of policy PDFs or an aging intranet usually need the same pieces. EPC Group's SharePoint consulting practice builds them in the order below, because metadata decided late is the most expensive thing to retrofit.

Pages, lists or a document library

The storage choice follows the content. How-to articles, process explanations and troubleshooting guides fit modern pages, which live in the Site Pages library. Microsoft lets a SharePoint Administrator allow or prevent modern page creation for the whole organization, lets site owners turn it on or off per site, and notes that setting the Members group to Read on the Site Pages library stops members from creating or editing pages at all (Microsoft Learn, Allow users to create modern pages, accessed 2026-10-20). That last setting is how EPC Group separates authors from readers on a knowledge site. Policies and procedures that must exist as controlled documents belong in a document library with content approval turned on (Microsoft Learn, Require approval of documents in SharePoint using Power Automate, accessed 2026-10-20). Short, structured entries such as glossary terms, FAQ items or contact directories fit a list, where every entry carries the same columns and views can filter them.

Content types, metadata and templates

Content types carry the metadata model. Microsoft describes them as a way to provide consistency across a site, with a chosen template and specific metadata. Content types created in the Content type gallery of the SharePoint admin center are saved to the content type hub at /sites/ContentTypeHub, can be based on a parent content type, and can have a Word, Excel or PowerPoint template attached so a new Policy document opens in the approved layout (Microsoft Learn, Create or customize a content type, accessed 2026-10-20). Columns are added from existing site columns and can be made required, optional or hidden (Microsoft Learn, Add columns to a content type, accessed 2026-10-20). Publishing makes a content type available to all sites; republishing pushes updates; and unpublishing converts the copies in use into local content types (Microsoft Learn, Publish a content type, accessed 2026-10-20). Pushing published content types to hub sites automatically, so every new library on a hub receives them, requires a pay-as-you-go license (Microsoft Learn, Push content types to a hub, accessed 2026-10-20).

A typical EPC Group policy library uses four content types, Policy, Procedure, Standard and Form, sharing a core set of required columns: owner, approver, business unit, effective date, review-by date and audience. Article pages carry a smaller set: topic, owner and review-by date. Keeping the column names identical across both is what later lets search and views treat the knowledge base as one body of content.

Approval and versioning

Nothing in a regulated knowledge base should publish without review. For pages, a site owner opens Pages and selects Automate > Power Automate > Configure page approval flow, names at least one approver and creates the flow; from then on each added or changed page goes to the approvers before it is visible (Microsoft Learn, Manage SharePoint page approvals with Power Automate, accessed 2026-10-20). Site owners can create more than one approval flow, for example one for news and one for standard pages, using the read-only Promoted State property to tell them apart (Microsoft Learn, Customize SharePoint page approvals to meet your needs, accessed 2026-10-20). Microsoft notes that SharePoint approvals are not available in government cloud environments (Microsoft Learn, Manage SharePoint page approvals with Power Automate, accessed 2026-10-20), which changes the design for GCC and GCC High tenants. For documents, Versioning settings > Require content approval for submitted items keeps pending documents hidden from readers until approved (Microsoft Learn, Require approval of documents in SharePoint using Power Automate, accessed 2026-10-20). Version history limits can be set at organization, site or library level, either Automatic or Manual (Microsoft Learn, Overview of version history limits for document libraries and OneDrive, accessed 2026-10-20); EPC Group sets policy libraries to Manual so the audit trail matches the retention schedule.

Search: managed properties, refiners and result types

Search reads the metadata model through the search schema. When search crawls a library, it automatically creates a crawled property and a managed property for each site column. To filter on a column, map its crawled property to an unused refinable managed property, such as one in the RefinableString00 to RefinableString219 range, give it an alias, and request a reindex of the library, because schema changes take effect only after the content is crawled again. Microsoft recommends mapping refinable properties at tenant level for consistency (Microsoft Learn, Manage the search schema in SharePoint, accessed 2026-10-20). Result types, which choose a display template for a type of result, apply only to the classic search experience; how results display in the modern experience cannot be customized (Microsoft Learn, Manage result types, accessed 2026-10-20). Microsoft Search is managed in the Microsoft 365 admin center, where admins tailor it with features such as search verticals (Microsoft Learn, Differences between the classic and modern search experiences in SharePoint, accessed 2026-10-20). For most knowledge bases, EPC Group relies on modern search, the refinable columns surfaced in library views and the Highlighted content web part, and keeps classic search pages only where a client already depends on them.

Ownership and review cadence

Knowledge bases decay when nobody owns the content. At item level, the owner and review-by date columns drive a scheduled reminder flow. At site level, SharePoint Advanced Management adds three policy types: site ownership policies that require a minimum number of owners or administrators, inactive site policies that detect inactive sites and notify owners, and site attestation policies that ask owners to confirm the site is still needed and that its owners, members, permissions and sharing settings are accurate (Microsoft Learn, SharePoint site lifecycle management, accessed 2026-10-20). If owners do not respond after three monthly notifications, an inactive site policy can do nothing, set the site to read-only, or archive it after a mandatory read-only period (Microsoft Learn, Manage inactive sites by using inactive site policies, accessed 2026-10-20). EPC Group's SharePoint governance consulting team writes these thresholds into the governance plan so reviews happen on a calendar, not after an audit finding.

Documented work

ANON-CASES: EPC Group engagement data for knowledge bases and policy platforms covers a large international nonprofit organization and mid-size and large organizations in healthcare, financial services and the public sector, where scope included content type design, policy library migration, page and document approval, search schema mapping and owner review policies, delivered by the firm's SharePoint consulting and SharePoint intranet consulting practices. Client names are not published here. Engagements are described by industry and organization size only, and no outcome figures are quoted that cannot be traced to a signed deliverable. EPC Group is a Microsoft Solutions Partner with all six Solutions Partner Designations as of October 2026.

Primary sources

Frequently Asked Questions

Pages, lists or a document library: which is right for a knowledge base?

Use each for what it stores. Modern pages suit how-to articles and explanations; Microsoft lets SharePoint Administrators allow or prevent page creation for the organization and lets site owners control it per site (Microsoft Learn, Allow users to create modern pages, accessed 2026-10-20). A document library suits controlled documents such as policies and procedures, with content approval under Versioning settings (Microsoft Learn, Require approval of documents in SharePoint using Power Automate, accessed 2026-10-20). Lists suit short structured entries such as FAQs or glossary terms. EPC Group usually combines article pages with a policy library on one communication site.

How are templates and content types used?

A content type bundles the metadata columns and behavior for one kind of item, such as Policy or Procedure. Created in the Content type gallery of the SharePoint admin center, it is saved to the content type hub and can be published to every site; columns can be made required, optional or hidden (Microsoft Learn, Create or customize a content type, accessed 2026-10-20; Microsoft Learn, Add columns to a content type, accessed 2026-10-20). A Word, Excel or PowerPoint template can be attached so new documents start from the approved layout. Unpublishing converts site copies to local content types (Microsoft Learn, Publish a content type, accessed 2026-10-20).

How are approval and versioning set up?

For pages, a site owner selects Pages, then Automate > Power Automate > Configure page approval flow and names the approvers; changed pages then wait for approval before publishing (Microsoft Learn, Manage SharePoint page approvals with Power Automate, accessed 2026-10-20). Microsoft notes that SharePoint approvals are not available in government cloud environments. For documents, Require content approval for submitted items keeps drafts hidden from readers until approved (Microsoft Learn, Require approval of documents in SharePoint using Power Automate, accessed 2026-10-20). Version history limits are set at organization, site or library level, automatic or manual (Microsoft Learn, Overview of version history limits for document libraries and OneDrive, accessed 2026-10-20).

How is search tuned (managed properties, result types)?

Site columns become auto-generated managed properties when search crawls the library. To use one as a refiner, map its crawled property to an unused refinable managed property such as RefinableString00 and give it an alias, then request a reindex of the library (Microsoft Learn, Manage the search schema in SharePoint, accessed 2026-10-20). Result types and display templates apply only to the classic search experience; how results display in modern Microsoft Search cannot be customized (Microsoft Learn, Manage result types, accessed 2026-10-20). For modern search, EPC Group relies on clean metadata, search verticals and bookmarks instead.

How are ownership and review cadence enforced?

Each article and policy carries an owner and a review-by date column, and a scheduled flow reminds owners before that date. At site level, SharePoint Advanced Management offers site ownership policies that set minimum owner counts, inactive site policies that notify owners, and site attestation policies that ask owners to confirm the site, its members, permissions and sharing settings are still correct (Microsoft Learn, SharePoint site lifecycle management, accessed 2026-10-20). Unanswered notices can lead to read-only mode or archiving (Microsoft Learn, Manage inactive sites by using inactive site policies, accessed 2026-10-20). EPC Group writes the review cadence into the governance plan.

Talk to a senior architect

If your policies live in a file share or your intranet articles have no owners, a 30-minute discovery call with a senior EPC Group architect covers the content inventory, a first-pass content type model and the approval design for your tenant. See the SharePoint consulting service hub for engagement structures.

Email contact@epcgroup.net or call 888-381-9725.

a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.

Documented engagements

Each record publishes a redacted primary-source document — a client purchase order, executed agreement or payment record — with a SHA-256 hash you can recompute, and states what the document does not establish.

All documented client engagements

Related reading

AI assistant — not a human