The Knowledge Base is where your organization writes things down: runbooks, how-tos, policies, troubleshooting guides, onboarding notes, answers to the questions your customers keep asking.
You write an article once. Then you decide who reads it:
That last point is the whole idea. A troubleshooting guide your support team relies on is usually the same guide a customer needs at 2am. Instead of maintaining two copies that drift apart, you maintain one and point it at both audiences.
It helps to know these by name, because they behave differently and the documentation refers to them constantly.
Knowledge Base in the left navigation.
The Library is the reading room. It lists the published articles you can read, browsable by category and searchable by keyword. Every member of your organization can open it — no special permission required. Out of the box everything is shared with the whole organization; when an article or category is shared more narrowly, members it is not shared with simply do not see it.
The Library shows internal articles and customer-facing ones, so your team gets the complete picture. They are split across three tabs: Internal Articles, External Articles and Specifications. Internal-only articles carry an Internal badge so a reader can tell at a glance whether a customer could also be looking at it.
The Library never shows drafts — not even to the person who wrote them. Drafts are previewed while you are editing them, not published to a reading surface.
Manage articles, reached from the button at the top right of the Library.
This is the authoring surface: a table of the articles you can see in every state, under the same three tabs as the Library, the editable category tree, and the controls for filing, ordering, sharing, and publishing. It is also where you turn on approval for published changes in a category, and watch the categories you care about. The stages your specs move through are set up in Configure Settings → Knowledge Base → Stages. It requires at least one Knowledge Base permission, so members who only read never see it. The article editor is also where reviewers leave review comments.
/portal/<your-portal-slug>/kb, reached from Help center in the portal's menu. Articles in a category that holds specs are listed on the portal's Specs page instead.
Customers see a deliberately narrower slice: only articles that are published, marked for the portal, not hidden by a category, and shared with their company. Everything else is invisible to them — not greyed out or locked, but genuinely absent.
::alert{type="note" title="Customers see "Help center", not "Knowledge Base""} The customer-facing surface is branded Help center throughout the portal. The two names refer to the same articles; only the wording and the visible subset differ. ::
Every article carries three independent settings. A reader sees the article only when all three allow it. This is the single most important thing to understand about the Knowledge Base, and it has its own page.
| Setting | Question it answers | Applies to |
|---|---|---|
| State | Is it finished? (draft / published / archived) | Everyone |
| Visibility | Is it for customers, or team-only? (Portal / Internal) | Customers |
| Category audience | Is the section it lives in customer-facing? | Customers |
| Companies | Which customer companies may read it? | Customers |
Visibility, category audience, and companies do not decide whether a member can read an article in your team's Library. They exist to control the customer side, though visibility and category audience also decide which tab lists the article. Which members can read, comment on, or edit an article is a separate control, Sharing — see Sharing articles and categories.
You click New Article and get a draft called Untitled article. You type a title and body; it saves as you go. You file it into a category, choose whether it is for customers or internal only, and click Publish — which mints a permanent URL slug. From then on it appears in your team's Library immediately, and on your customers' Help center if you pointed it at them. Later you can unpublish it back to a draft, or archive it when it is no longer relevant. Nothing is ever deleted.
Worth knowing up front so you can plan around it:
Template health
What the Healthy, Needs review and Broken badges mean, which configuration changes repair a template automatically and which only flag it, and the limits a template must stay inside.
Write and Publish Your First Article
A step-by-step walkthrough: create a draft, write it, file it, choose an audience, publish it, and confirm your readers can see it.