> For the complete documentation index, see [llms.txt](https://help.chatlyai.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.chatlyai.app/products-and-features/knowledge.md).

# Knowledge

Give the assistant your files and your brand's look and voice.

Knowledge gives Chatly the context it needs: files it can read, and your brand's look and voice. Set it up once and attach it to any chat.

## Create a collection or brand kit

1. Click **Knowledge** in the left sidebar.
2. Choose what to set up first:
   * **Collection**: group files and docs. Chatly reads them when you attach the collection to a chat. Click **New collection**.
   * **Brand kit**: store your colors, fonts, logo and tone of voice once. Chatly applies them to everything it makes. Click **New brand kit**.

![The Knowledge page](https://3503370835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHDPAn3RzU7mRQrMH1UK%2Fuploads%2FNdWhuI8xd0SZVD7Nw6xA%2Fch-knowledge.webp?alt=media)

Knowledge needs a paid plan: Standard includes 2 knowledge bases, Professional 5 and Ultra 25. On the Free plan, the buttons open the plan options.

## Use knowledge in a chat

Click the **Knowledge** button (the books icon) in the chat box, then pick a **Collection** or a **Brand kit**. **Manage knowledge** takes you back to the Knowledge page.


---

# 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://help.chatlyai.app/products-and-features/knowledge.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.
