> ## Documentation Index
> Fetch the complete documentation index at: https://docs.behaviq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge base

> Upload workspace files for BehavIQ to use in chat.

The knowledge base lets admins upload files that BehavIQ can retrieve from when answering workspace questions.

<img src="https://mintcdn.com/petruslabsptyltd/ZqiV5LlbuV-wxLL4/assets/business-knowledge-base.png?fit=max&auto=format&n=ZqiV5LlbuV-wxLL4&q=85&s=74e76bbebd506519b2cb9ae02318aa60" alt="The BehavIQ customization page with workspace knowledge base and response personalization controls." width="1024" height="1202" data-path="assets/business-knowledge-base.png" />

## Upload files

Open `Settings -> Customization`, then use the knowledge base upload area.

Supported file types include common document, text, slide, spreadsheet, and code formats. PDFs, Word documents, PowerPoint files, plain text, markdown, CSV, and similar files are the main use cases.

## Indexing status

After upload, each file moves through processing before it is available in chat.

Common states are:

* uploaded
* processing
* ready
* failed

Large PDFs and slide decks can take longer than text files. Use refresh if the page has not updated.

## Failed files

A failed file was uploaded but could not be indexed. This can happen when the file is corrupted, password protected, too large, or uses a format the indexing service cannot read.

For PDFs, converting to text or markdown can be a useful fallback when the file content matters more than the original layout.

## How chat uses it

When a member asks a question, BehavIQ can retrieve relevant workspace knowledge before writing the answer. The file does not need to be attached to each prompt once it is indexed.

Good knowledge base files are specific and current. Remove outdated policies or duplicate versions so answers are less likely to pull from the wrong source.

## Response personalization

The customization page also has response personalization fields. Use these for organisation context, preferred wording, and escalation guidance.

Keep this text short and practical. It is read by the assistant on many answers.
