Manage Knowledge Content — Documents & Chunks

View, add, modify, or delete documents and chunks to keep your Knowledge Base current and accurate.

Table of Contents

· [Manage Documents](#manage-documents)

· [Manage Chunks](#manage-chunks)

· [Best Practices](#best-practices)

Manage Documents

On the Knowledge Base detail page, you can manage all uploaded documents:

Document Actions

Action	Description
View	View all documents, processing status, and details
Add	Upload new documents to the Knowledge Base
Enable / Disable	Toggle documents. Disabled documents won't be retrieved but are still stored
Archive	Archive documents no longer frequently used
Delete	Permanently delete documents from the Knowledge Base
Re-index	Re-index documents when settings are changed

Document Status

Status	Description
Queuing	Waiting to be processed
Processing	Being chunked and indexed
Available	Ready for retrieval
Error	Processing failed — click for details
Disabled	Turned off — excluded from retrieval
Archived	Archived

💡 TIP: Use Enable/Disable instead of Delete when you want to temporarily remove documents from retrieval. You can re-enable them anytime without re-uploading.

Manage Chunks

Click on a document to view and manage its chunks:

Chunk Actions

Action	Description
View	View detailed chunk content
Edit	Modify chunk content
Add	Manually add a new chunk
Enable / Disable	Toggle individual chunks
Delete	Delete a chunk
Add Image	Attach images to a chunk

Notes on Editing Chunks

With Parent-Child Mode:

· When editing a parent chunk, you can choose to regenerate its child chunks or keep them unchanged

· Editing a child chunk does not update its parent chunk

⚠️ IMPORTANT: When editing chunks, new content is re-embedded automatically. However, test retrieval after editing to ensure results remain accurate.

Best Practices

Check Chunk Quality

After creating a Knowledge Base, review chunks to identify issues:

· Chunks too short — May lack sufficient context, leading to semantic loss and inaccurate answers

· Chunks too long — May include irrelevant information, introducing semantic noise and lowering retrieval precision

· Semantically incomplete chunks — Caused by forced chunking that cuts through sentences or paragraphs

Use Child Chunks as Retrieval Hooks for Parent Chunks

In Parent-Child mode, child chunks serve as "hooks" — retrieval entry points, after which the parent chunk provides fuller context.

Effective child chunk types:

Type	Example
Keywords	blinking light, won't turn on, red light, connection error, frozen
Summaries	Guide to interpreting LED colors and troubleshooting hardware issues
Queries	What does a solid red light mean?

Use Summaries to Bridge Query-Content Gaps

Summaries are especially useful when:

· User queries differ from document language: Add summaries in the way users actually ask questions

· Concepts are implicit or buried in details: Add high-level summaries that surface core concepts

· Raw text is non-textual: When a chunk is primarily code, tables, or logs — add descriptive summaries

· Related chunks should be retrieved together: Apply identical summaries for grouped retrieval

📖 Previous: [External Knowledge API](./07-external-knowledge-api.md) · Next: [Metadata](./09-metadata.md)