Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.wittify.ai/llms.txt

Use this file to discover all available pages before exploring further.

Knowledge Bases is the page that lists every knowledge base in your project. A knowledge base groups related documents your chat assistant will search together. Each KB carries a name, a primary-language hint for the chunker, and chunk-size settings. Open any KB to upload documents, see scope, and tweak settings.

Page anatomy

RegionWhat you see
Topbar breadcrumbChat with Your Documents / / Knowledge Bases.
Page headerTitle Knowledge bases with a brand-gradient + New knowledge base button on the end edge.
List bodyA grid of KB cards.
Empty stateA dashed-border card with a Create a knowledge base button when the project has none.

KB list cards

When the project has at least one KB, each row is a card.
ElementWhat it shows
Card titleThe KB name.
Documents countHow many documents the KB contains.
Chunks countHow many text chunks the documents have been split into.
SizeThe total stored size, in MB or KB.
Created dateA small caption like Created 12 Apr 2026.
ClickOpens the KB detail page.
The list filters out session-scoped knowledge bases (the hidden buckets created when you drop a file into a chat composer mid-conversation). Those never appear here.

Empty state

When the project has no knowledge bases yet:
ElementWhat it says
TitleNo knowledge bases yet.
BodyCreate a knowledge base to upload documents your agent will search.
ButtonCreate a knowledge base. Brand-gradient pill.
The button opens the same dialog as + New knowledge base in the page header.

Creating a knowledge base

The new-KB dialog has three regions: a name field, a description field, and a collapsible Advanced block.
FieldNotes
Name requiredPlain-text input. Placeholder e.g. HR policies. The dialog blocks save until the field has at least one non-whitespace character.
DescriptionOptional one-line summary. Placeholder What lives inside this knowledge base?
Advanced (collapsed by default)Two numeric fields: Chunk size and Chunk overlap. The block carries the helper text Larger chunks carry more context per retrieval but fewer per document. Defaults work well for most cases.
Create knowledge base buttonBrand-gradient submit.
Cancel buttonCloses the dialog.
When the request resolves, the new KB appears at the top of the list.

KB detail page

Click any card to open the KB. The detail page has three tabs: Documents, Scope summary, and Settings.

Documents tab (default)

The Documents tab is intentionally identical in shape to the AI Agents knowledge base step: same stats strip, same drag-drop zone, same file list, same toolbar.

Stats strip

CardWhat it shows
DocumentsThe count.
ChunksThe total chunks across all documents.
SizeTotal stored size.
LanguageThe primary language hint, with a small caption showing the engine’s detected mix.

Upload zone

A dashed-border drop area below the stats strip.
StateWhat you see
IdleAn upload icon plus the label Drop files here, or browse to upload. PDF, DOCX, XLSX, CSV, JSON, TXT, MD, or images (JPG, PNG, WEBP, TIFF). Up to 10 MB per file.
Drag overThe zone tints to the brand color and the label changes to Drop the files here…
PendingA small list of files queued, with a Cancel button per file before they upload.

Toolbar above the file list

ElementWhat it does
Search boxFilters by file name.
Status filterA dropdown: All statuses, Ready, Processing, Failed.
Bulk actionsOnce at least one row is selected: Delete, Clear selection.

File list

ColumnNotes
NameThe file name. Long names truncate.
StatusA chip, see status pipeline below.
SizeIn MB or KB.
UploadedRelative timestamp.
ActionsPer-row menu with Open, Re-train, Delete.
A Load more button at the bottom paginates through long lists, with a small Showing X of Y count.

Status pipeline

ChipMeaningColor
PendingThe file is queued.Muted.
ParsingThe engine is reading the file.Amber.
ChunkingThe engine is splitting the content into chunks.Amber.
EmbeddingThe engine is computing vectors for the chunks.Primary.
ReadyThe document is searchable in chats.Emerald.
FailedThe pipeline errored.Red.

Scope summary tab

A read-only summary of what the KB contains across every document.
SectionWhat it shows
SheetsDistinct sheet names found across spreadsheet documents.
HeadingsDistinct section headings found across structured documents.
LanguagesThe languages detected, with a small percentage per language.
Empty stateThe scope summary lights up once your documents finish processing.
The same scope data feeds the Scope filter in the chat composer (see Chat Canvas).

Settings tab

FieldNotes
NameRename the KB.
Default language hintDropdown: Auto-detect, Arabic, English, Arabic + English, Other. The change applies only to future uploads.
Chunk sizeAffects future uploads only. Existing chunks are not re-split.
Chunk overlapAffects future uploads only.
Save changes buttonPersists the new values. A toast confirms Settings saved.
Delete knowledge baseA separate destructive section at the bottom.

Deleting a knowledge base

Click Delete knowledge base in the Settings tab.
ElementWhat it says
TitlePermanently delete this knowledge base?
BodyThis will delete every document, chunk, and vector for this knowledge base. This cannot be undone.
Confirmation inputType DELETE to enable the confirm button.
Cancel buttonCloses the dialog.
Delete buttonStyled with the destructive (red) background and white text. Disabled until the input matches DELETE exactly.
After confirmation, the KB is removed and the page returns to the KB list.

Common questions

Pending normally moves to Parsing within seconds. If it stays for a long time, the file may be encrypted, password-protected, or a format the engine cannot read. Click the row’s Re-train action to retry, or Delete to drop it.
The engine reads embedded text. Pure scans need OCR; the engine handles common cases automatically but very low-quality scans may produce empty chunks. Re-export the PDF with embedded text or use a higher-quality scan.
Open the Scope summary tab. If your headings or sheets are not in the list, the engine may have failed to extract them. Try Re-train on the document. If the content is in an image-only PDF, see the previous question.
Not from this page. Delete from the source KB and re-upload to the target. KB scope is intentionally local so retrieval boundaries stay clear.
The hint applies to future uploads only. Existing chunks were already produced. Delete and re-upload the document for the hint to take effect on it.
Session-scoped KBs (created automatically when you drop a file into a chat composer) are hidden. They appear only inside the chat that owns them and are not for general project use.
The bulk action confirms before running. If rows were unintentionally selected, they show as a count chip in the toolbar. The select-all checkbox at the top of the table is the most common slip, untick it before clicking Delete.
Not yet. Each project owns its own KBs. Use the project switcher in the sidebar to flip projects, but the KB list resets to the new project’s KBs.

Where to go next

Documents

Per-document detail, scope, tags, chunk inspector.

SQL Sources

Connect a read-only database alongside your KBs.

Chats

Start a conversation grounded in your KBs.

Project Settings

See storage, retrieval features, danger zone.