Self-provisioning
First time the webpart loads, it creates its backing SharePoint list. No admin needs to set up list templates or columns.
Layer 2 · Knowledge Base · Last reviewed May 2026
A knowledge base for SharePoint that doesn't charge per user.
Quick answer: Athena's Knowledge Base webpart provides a rich-text article catalogue with search, attachments, image upload, and deep-linking, inside your existing SharePoint tenant. Self-provisioning backing list. £290/month per tenant. Unlimited users. A Confluence alternative for Microsoft 365 teams paying £5-10 per user per month for a wiki that lives outside their M365 tenant.
SharePoint Wiki was deprecated. Teams replaced it with Confluence, Document360, or Notion: separate platforms, per-user invoices, and the constant problem of staff bouncing out of M365 to find documentation. Athena puts the knowledge base back where it belongs: in the intranet your team already uses.
The Knowledge Base, end-to-end.
Article creation, search, deep-linking, attachments, all from inside SharePoint.
Video walkthrough
Athena Knowledge Base - walkthrough
Coming soon, recording in progress
What Athena's Knowledge Base does.
Rich-text article editor
Full WYSIWYG editing inline. Headings, lists, links, inline images, tables.
Search
Search across all articles from inside the webpart. Microsoft Search also indexes the backing list, so articles surface in tenant-wide SharePoint search.
Attachments
PDFs, documents, images attached directly to articles.
Image upload
Drop images inline; they're stored in standard SharePoint media library structure.
Deep-linking
Link from one article to another, or share a direct link to an article externally.
Single tenant list
The whole KB lives in one place. No separate site collection needed.
Standard SharePoint metadata
Categorise articles using familiar SharePoint columns (category, owner, last reviewed, etc.) for filtering and views.
How Athena compares to dedicated knowledge-base platforms.
| Capability | Athena Knowledge Base | Confluence / Document360 / Notion |
|---|---|---|
| Lives inside Microsoft 365 (no separate login) | Yes: runs in SharePoint tenant | Separate platform; SSO available |
| Per-user pricing | No: flat £290/mo per tenant | Yes: £5-10/user/mo typical for Confluence; varies for others |
| Rich-text article editor | Built in | Native |
| Search | Built in + Microsoft Search indexed | Native |
| Attachments & images | Built in | Native |
| Deep-linking between articles | Built in | Native |
| Customer-facing public help centre | Not included (internal-only) | Available in Document360, Helpjuice; some Confluence configurations |
| Version history / multi-stage approval workflows | SharePoint list versioning only | More sophisticated in Confluence and Document360 |
| Plugin / integration ecosystem | Microsoft 365 / Graph native | Confluence has large Atlassian marketplace |
| Data residency | Inside customer M365 tenant | Vendor-managed, typically US-hosted |
Verify current vendor pricing and feature scope before purchase.
Where a dedicated knowledge-base platform is the better choice.
Frequently asked questions.
SharePoint's classic Wiki page library has been progressively deprecated in favour of modern SharePoint pages. Many existing wikis still function but Microsoft no longer recommends new deployments. Modern teams typically replace SharePoint Wiki with either a dedicated knowledge-base SaaS (Confluence, Document360, Notion), a custom SharePoint page structure, or a third-party SharePoint knowledge-base webpart. Athena provides the third option: a purpose-built Knowledge Base webpart that lives inside SharePoint with a rich-text article editor, search, and attachments.
Your knowledge base, where your team already is.
Athena's Knowledge Base webpart turns SharePoint into a searchable rich-text article catalogue. £290/month per tenant. Bundled with org chart, policy management, noticeboard, and 17 other webparts.
Built by Lewis Enright Limited, United Kingdom. Last reviewed . Confluence, Document360, Helpjuice, Notion, and other product names are trademarks of their respective owners. References describe publicly documented features and typical mid-market pricing at time of writing. See bundled-economics breakdown →