Small teams tend to spread internal knowledge across whatever tools are at hand. Documents in one place, announcements in another, policies somewhere else. This works at a certain size, but it doesn’t scale well. As teams grow, the absence of a dedicated system becomes a real operational cost.
An internal knowledge base is a tool built specifically for that job.
What an internal knowledge base is
An internal knowledge base is a structured, searchable home for the information a team needs to operate. Onboarding materials, standard operating procedures, policies, training content, reference guides. The content that answers “how do we do things here.”
The distinction that matters most is between a knowledge base and a document repository. A repository stores files. A knowledge base adds structure, assignment, and accountability. Those three things together are what make it useful as an operational tool rather than a storage system.
Why completion tracking matters
Publishing a document and knowing your team has read it are two different things. Most knowledge base tools handle the first and ignore the second.
For some content, that gap is acceptable. A reference document someone consults occasionally does not need proof of completion. But a policy change, an onboarding module, or a compliance requirement is different. That content needs to be received and acknowledged, not just made available.
The teams that manage this well distinguish between required content and reference content, and they track completion on the required side. That distinction is worth building into the tool rather than maintaining separately in a spreadsheet.
Why WordPress teams are in a specific position
WordPress ships with a user account and permissions system. For a team that already runs WordPress, that infrastructure is already in place. Team members already have wp-admin access.
Most knowledge base tools are separate platforms. For a WordPress team, that means maintaining another account and another login alongside everything already in use. For some teams the tradeoff is worth it. For others, keeping internal knowledge inside WordPress is the simpler answer.
What Keystone does
Keystone is a WordPress plugin that adds an internal knowledge base to wp-admin. It has no front end and requires no external accounts. It extends WordPress’s existing capability system rather than replacing it. By default, Keystone capabilities are assigned to WordPress’s built-in roles, but the assignment is configurable. Any capability can be granted to any role, including custom roles. Administrators always have full access.
Managers organize content into Sections, Modules, and Items. Required modules support completion tracking, due dates, sequential completion, and acknowledgment requirements. Reference modules organize content that doesn’t need assignment-based tracking, though assignment is still supported. Members access everything from the same wp-admin they already use.
It’s built for small WordPress teams that need more structure than a shared folder but don’t need an enterprise training platform. One license covers unlimited team members.
If that fits what your team is looking for, the features page covers the specifics. Or see pricing.