Configure the public site
- Open Knowledge base → Settings.
- Enter the public title and a concise description of what customers can find.
- Copy the public link and keep it ready for testing.
- Save the content settings.
- Turn on Public knowledge base only when the initial library is ready.
The public URL returns a not-found response while the knowledge base is disabled. After enabling it, visitors can browse categories and published articles and use the site's search. Draft articles never appear publicly.
Who can do this
- Required access: an access level that includes Knowledge Base - Full Access.
- Default access levels that include it: System Administrator.
- Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
- Knowledge Base - Standard Access can write and edit articles; publishing and delivery settings need Full Access.
- Personal accounts: Not available. This is a work feature, so it is hidden in personal (family) spaces.
Owners and admins review and change access levels in Settings → Administration → Members → Access levels.
Run a launch review
- Open the public link in a private browser where you are not signed in.
- Test desktop and mobile widths.
- Open every launch article and verify internal product links, external links, formatting, and images.
- Search for the phrases customers actually use and confirm the right answers appear.
- Check that draft or internal notes are not visible.
- Ask a teammate outside the authoring group to complete a task using only the article.
Maintain the library
| Trigger | Documentation action |
|---|---|
| Product or policy change | Update affected articles before or alongside the release. |
| Repeated ticket question | Create or improve the article that should have prevented the ticket. |
| Broken link or outdated screenshot | Correct it immediately and review nearby articles for the same issue. |
| Article no longer applies | Unpublish or delete it, then update links that pointed to it. |
| Quarterly review | Check owners, freshness, search language, and low-value duplicate content. |
Use views thoughtfully
View counts help identify high-traffic content, but they do not prove an answer worked. Compare popular articles with support volume and customer feedback. A high-view article with many follow-up tickets may need clearer steps; a low-view article may need a better title, category, or search language.
Ownership practice: Assign a business owner for each category even if one documentation lead edits everything. Accuracy improves when the team responsible for a workflow is accountable for reviewing its explanation.
Troubleshooting
| Problem | What to check |
|---|---|
| The public link returns 404. | Confirm Public knowledge base is enabled in Settings. |
| An article is missing. | Confirm it is Published, not Draft, and refresh the public page. |
| The category is empty. | Check that its articles are assigned to it and published. |
| Search does not find an article. | Use the customer's terms in the title, excerpt, headings, and body. |