Plan a useful knowledge base
Organize a help library that makes reliable answers easier to find and maintain.
On this page
Overview
The Knowledge Base at #/kb stores categories and articles. Public help-center slug, search, and feedback are Settings → System → Knowledge Base (feature basic_kb). The same published, allowed articles feed the chat Document tab (real categories, popular articles, article detail) and grounded Chat AI (Fulltext + Chunks). Internal articles stay out of customer Chat AI.
When to use this
Maintain support procedures in the Knowledge Base so customers and agents can find approved answers. Chat AI retrieves only articles permitted by its visibility, AI-access, and indexing rules.
Where to find the controls
Sidebar Knowledge Base → #/kb. Public URL uses the configured slug after permalinks work. Chat Document tab reads the same categories. Settings: #/settings/system/kb.
Who can make these changes
View in admin: elegant_support_view_kb. Publish/edit: elegant_support_manage_kb. Visitors read public articles only.
Before you begin
Enable basic_kb in Feature Manager if the module is gated. Set public slug, search, and feedback in System → Knowledge Base. RAG reindex is Settings → AI after a provider exists.
Follow these steps
- Create categories.
- Write articles.
- Mark internal vs public.
- Publish.
- Confirm the article appears in #/kb, the public help center, and chat Documents.
- If AI is on, wait for index/chunks before testing grounded answers.
Settings reference
Category name, slug, visibility, article title, body, status, internal flag, popularity signals for the chat tab, feedback if enabled.
Example workflow
You publish “How to reset a password” as public. A visitor opens Document in the widget, opens the article, then asks Chat AI the same question and receives a grounded answer with retrieval — or Talk to human if there is no evidence.
Good practices
Put procedures in Fulltext-friendly paragraphs; grounded AI reads Fulltext and Chunks, not marketing PDFs you never ingested.
Important considerations
Internal KB is excluded from customer Chat AI. Unpublishing hides the article from chat Documents. Feature off means the KB screen is unavailable, not “empty”.
If something does not work
KB hidden: basic_kb off, missing view_kb, or permalink 404 on the public slug — flush permalinks. Article missing in chat: not published, internal, documents disabled on the widget, or category empty.