> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/admin/knowledge-base.md).

# Knowledge base

The **Knowledge base** holds your company's documents, which Astro checks before answering questions about policies, processes, and products.

Here are the available features:

### Turn on the knowledge base

To turn on the knowledge base, follow these steps:

1. In the **Workspace knowledge base** section, turn on **Use in conversations**.
2. Under **Applies to**, choose where the knowledge base is used: **Default chat**, **Experts**, or **Both**.

Below the options, you'll see the number of files and documents and the space used out of the limit (e.g., **1.1 MB of 1 GB**).

### Upload documents

To add documents to the knowledge base, follow these steps:

1. In the **Upload documents** section, drag files into the area shown or click **choose files**.
2. Track indexing progress in the **Documents** list.

{% hint style="info" %}
Each file is indexed in the background. PDF, DOCX, TXT, MD, HTML, CSV, and XLSX files up to 50 MB each (20 MB for spreadsheets) are supported, with a limit of 200 files and 1 GB per workspace.
{% endhint %}

{% hint style="warning" %}
**Important:** keep the knowledge base up to date and remove old versions to avoid outdated answers. If a document shouldn't be available to everyone, use **Restrict access...** after uploading it.
{% endhint %}

### Review documents

The **Documents** list shows the following information for each file:

* **Name** and **Type:** the file name and format.
* **Size:** the file size.
* **Status:** indexing status (e.g., **Indexed**).
* **Uploaded by** and **When:** who uploaded the file and the date and time.
* **Tokens / ≈chunks:** the volume of indexed text and the approximate number of chunks created.
* **Active:** whether the document is being used. Turn off the toggle to exclude the document from answers without deleting it.

#### Manage a document

Click the three-dot icon next to a document to see the following options:

* **Download:** downloads the original file.
* **Reindex:** processes the document again. Useful when search doesn't find passages that should be in the file.
* **Restrict access...:** sets who can get answers based on the document.
* **Delete:** removes the document and its indexed content from the knowledge base.

{% hint style="success" %}
To remove a document from answers temporarily, turn off the **Active** toggle instead of deleting it.
{% endhint %}

### Test search

To see which passages Astro would find for a question, follow these steps:

1. In the **Test search** section, enter a question or term.
2. Click **Search**.

The test only shows the passages found. Nothing is sent to the model. Use it to confirm a document was indexed correctly before you announce the knowledge base to users.

### Delete the entire knowledge base

To delete every document in the knowledge base, click **Delete entire knowledge base** and confirm.

{% hint style="danger" %}
This removes all documents and indexed content, and conversations stop using the knowledge base. This action can't be undone once confirmed.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.skyone.cloud/english/admin/knowledge-base.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
