A knowledge base is the content questions are answered from: one product’s docs site, a repository or a team wiki. It belongs to a workspace and has its own sources, client keys and analytics.
Create a knowledge base
Owners, admins and members can create one. Go to Knowledge Bases, click New Knowledge Base, fill in the fields and click Create Knowledge Base. Then add content on its Sources tab (see Knowledge sources) and test answers on its Playground tab.
| Field | Notes |
|---|
| Name | Required, 2 to 100 characters. Every field can be changed later in Settings |
| Description | Optional |
| Type | External (default) or Internal. See Internal knowledge bases |
| Respect robots.txt | For website crawls. On by default |
Plans limit how many knowledge bases you can have: 1 on Free, 5 on Pro, unlimited on Enterprise. Archived ones do not count. Past the limit, creating one fails with PROJECT_LIMIT_REACHED. See Billing & Plans. Settings
Click Settings on the knowledge base page.
| Section | What it holds |
|---|
| Knowledge Base Details | Name, description and type. Changing the type asks you to confirm |
| Who can reach this | Live client keys, connected chat bots, and the Workspace members switch. See Roles & Permissions |
| Content Settings | Respect robots.txt for website crawls |
| Scheduled Crawling | An extra hourly, daily, weekly or monthly sync of every source, on top of each source’s own refresh |
| AI Persona & Instructions | Persona, tone and standing instructions. See Answer style |
| Starter Questions | Generated from your content, your own list, or none |
| PII Masking | What to mask, custom patterns and an allow-list. See PII & data retention |
| Danger Zone | Archive, restore and delete |
Internal knowledge bases
A knowledge base is external by default: create a client key and publish it through the widget, the SDKs and the API. Set the type to internal and it has no public surface at all.
- Every public surface refuses it: the widget, the form deflector, the public API and SDKs, and API key or Public MCP servers.
- Client keys cannot be created for it. When you switch an existing knowledge base to internal, its live keys stop working as soon as you save.
- Every document it indexes is
restricted. Switching back to external does not make them public again.
Your team still reaches it through the dashboard, Ask, the browser extension, and Internal MCP servers, with the usual chat permission.
Chat bots do not check who is asking. A Slack or Teams bot connected to an internal knowledge base answers from it for everyone in the channel.
Archive a knowledge base
Settings → Danger Zone → Archive pauses a knowledge base without deleting anything. It stays in your list, marked Archived, but it answers no questions, runs no syncs and leaves the Ask assistant. Its settings are read-only.
An archived knowledge base does not count toward your plan’s limit. Restore brings it back, and counts again.
Delete a knowledge base
Deleting is permanent. It removes the knowledge base’s sources, documents, conversations and custom answers, and the client keys, bots, agent apps and form deflectors attached to it, which stop answering at once.
The dialog lists what will be deleted and offers Archive instead. If the knowledge base holds anything, type its name to confirm.
From the API, send the name in the body:
curl -X DELETE https://app.kelu.dev/api/v1/knowledge-bases/$KB_ID \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"confirm": "Product docs"}'
409 CONFIRMATION_REQUIRED. GET /api/v1/knowledge-bases/:id/deletion-preview returns the same counts the dialog shows.
Archiving, restoring and deleting need the Edit Config permission. Each is recorded in the workspace’s Activity Log.
One knowledge base or several?
- Several products or audiences: one knowledge base each, with its own widget, keys and analytics.
- Public docs and internal notes for one product: one knowledge base, with the internal sources’ documents
restricted. See Document visibility for how to set it.
- One product, several docs versions: one knowledge base with source groups, on the Enterprise plan.
