Creating a base

In the dashboard, click Knowledge Base in the sidebar. You'll see the list of your bases (up to 3 on the Business account) and a button to create a new one.

Step 1 — Click Create base

On the base list, click the create button.

Step 2 — Name it

The name shows in the public portal's header, e.g. "Acme Help Center".

Step 3 — Check the slug (address)

The slug is generated from the name and forms the public address of the base:

You can change it — lowercase letters, digits, and hyphens are allowed (3-60 characters). Slugs are global: if someone already took an address, pick another.

Step 4 — Pick the content language

Each base has one language — it sets the language of the public portal's interface. Multilingual documentation is published as separate bases.

Step 5 — Add a description (optional)

A short description shown on the base's home page.

Step 6 — Save

The base is ready — you can add categories and entries.

⚠️ Warning: Changing the slug after publishing changes the base's public address — old links stop working. Settle on a slug early and stick with it.

The base has an Active toggle. An inactive base serves no content at its public address — useful while you're still building the structure and don't want to show an unfinished portal.

💡 Tip: A typical workflow: create the base as inactive, add categories and entries, review everything, then flip it to active.

Deleting a base removes its categories and entries, but does not delete documents or share links — those exist independently and keep working at their /s/... addresses.

• The account owner — always.
• Workspace members with the Manage Knowledge Base permission — they can create and edit bases owned by the workspace owner. Owner and editor roles have it by default; adjust it in team settings.

Short, generic slugs (e.g. help, docs, support, api) are reserved by the platform. Add your company name, e.g. acme-help.

The Business plan includes 3 Knowledge Bases per account. If you need more, reach out at support@clarife.app.

Creating and deleting a whole base happens in the dashboard. Through the API and MCP you manage an existing base's settings, categories, and entries.