An internal knowledge base your team will actually use
Put policies, processes and how-tos in one searchable place, decide who can read each article, and keep every page current.
14-day free trial · No credit card required
Company knowledge gets lost in chat and old docs
Everyday answers live in a dozen places, so people ask a colleague instead, and the colleague answers the same question again next week.
Lost in chat
The answer was posted once, in a busy thread that nobody can find again three months later.
Nobody owns it
Pages go stale because no one is asked to check them, so people stop trusting all of them, even the good ones.
All or nothing
Shared drives make it hard to keep salary bands or incident notes away from everyone else.
Search that misses
One typo in the search box, and the page you need never comes up, so people give up and ask.
We give company knowledge one home: searchable, access-controlled and reviewed on a schedule.
A wiki collects pages. A knowledge base answers questions.
| Compared on | Wiki | Internal knowledge base |
|---|---|---|
| Structure | Open pages, anywhere | Categories with an owner |
| Freshness | Edited when someone remembers | Review dates and flags |
| Access | Usually the whole workspace | Per article, category or help center |
| Finding things | Browse the page tree | Typo-tolerant search |
What goes in an internal knowledge base
- Onboarding guides and first-week checklists
- HR policies, benefits and time off
- IT setup and security rules
- Processes and runbooks for each team
- The questions people keep asking in chat
Decide who can read every article
Available on Growth and CatalystSet access at three levels and combine them, so one help center can serve your customers and your staff.
Articles
Public; Anyone with the link, hidden from navigation and search and opened by a share link; or Private, for the author and the teammates they choose.
Categories
Everybody, Everybody with a link (hidden from navigation), Team members only, or Me and selected team members.
The whole help center
Public, private or password-protected.
Public and internal together
Keep customer docs public and share internal categories with your team, in the same help center.
Employees sign in with the login they already have
Available on CatalystJWT single sign-on signs readers in with your own login, so there is no extra password to hand out or reset.
How it works
Your app signs a token (a JWT) with a secret you share with us and sends the reader to the help center. They arrive signed in.
With a private help center
Pair the two, so only your team and the people signed in through your login can read it.
In the widget too
The widget signs readers in the same way inside your app, so help opens already signed in.
Keep it on your network, or inside your app
Available on Growth and CatalystIP allowlist
Only the IPv4 addresses you list can open the help center. Enter exact addresses; ranges, CIDR blocks and wildcards are not supported. It covers the help center, the widget and embeds, and your team members too, but not the dashboard. Turning it on switches off the public MCP.
JS-only access
Keeps the help center off the open web: it opens only inside your app or the widget. JS-only access is not a security control, because it relies on the referrer. For content that must stay private, pair it with a private help center and single sign-on.
Keep it current, and write it together
Available on every planReviews
Flag an article for review, or give it a reviewer and a date, so someone checks it before it goes stale.
Version history
See who changed what, compare versions and restore one. How far back it goes depends on your plan.
Ratings and feedback
Readers rate each article and leave feedback, so you can see which pages need work.
Team notes
Leave notes on an article for your team, such as what to change next; readers never see them.
Live collaboration, editing the same article at the same time, is available on Catalyst on request.
Flag an article for reviewBring your docs in, and reach them from AI tools
Free migration
We move your content for you, free on every plan, including from Confluence (done for you only) and Notion.
Self-service import
Import from Zendesk Guide, Intercom, Document360, Help Scout Docs, Front Knowledge Base or HelpDocs yourself, on every plan.
Internal content in AI tools
Connect an AI assistant to mcp.helpcenter.io with OAuth or an API key, on Growth and Catalyst only, to reach your internal articles.
The public MCP
On every plan, a public help center has a read-only MCP at its own address plus /mcp. It serves public content only, and switches off with an IP allowlist or JS-only access.
Set up your internal knowledge base
-
Bring your content in
Import it yourself, or we move it for you, free on every plan.
Set up your help center -
Choose who sees what
Make the help center private, or share internal categories with your team only.
Private categories -
Sign people in
Turn on JWT single sign-on on Catalyst, or list your office and VPN addresses in the IP allowlist.
JWT single sign-on
One way to organize an internal knowledge base
This is an example: a private help center with the sharing setting each category might use. Rename, merge or split categories to fit your company.
Which plan fits your internal knowledge base
Every plan has unlimited articles and viewers, typo-tolerant search, version history and reviews.
Bootstrap
For public docs one person writes
- 1 team member
- Public content only
- Custom domain with SSL
- Free migration, done for you
Growth
For a team that keeps internal docs private
- Up to 10 team members
- Private or password-protected help center
- Private and link-only categories and articles
- IP allowlist and JS-only access
- Authenticated MCP for AI tools
Catalyst
For a whole company on one login
- Unlimited team members
- Everything in Growth
- JWT single sign-on for readers
- Staged changes
- Semantic search included
- Live collaboration on request
Semantic search: included on Catalyst, an add-on on Bootstrap and Growth. Compare every plan
Internal knowledge base questions
Can internal and public docs live in one place?
How do employees sign in?
Can I restrict it to the office network or VPN (IPv4 addresses)?
How is it different from a wiki?
Can I migrate from Confluence or Notion?
Still deciding? Talk to us.
Give your team one place to look
Bring your docs in and decide who sees what.
No credit card required · Free migration on every plan