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

# Project Knowledge Base of aqua Intelligence

The project knowledge base lets project administrators upload files that are used exclusively **within** a **specific project**.&#x20;

aqua Intelligence uses these files only when generating content or answering questions **inside** that **project** — keeping responses relevant and specific to that project's domain, terminology, and processes of each project — without affecting other&#x73;**.**

### What aqua Intelligence can do with project knowledge base files

Files uploaded at the project level are only used by aqua Intelligence when:

* A user asks a question in the **aqua Intelligence Chat** within that project
* A user generates **requirements**, **test cases**, or **test data** inside that specific project

This keeps responses relevant and localized to the project’s specific domain.

#### **How to upload**

1. Navigate to **Integrations → aqua Intelligence**
2. Under **aqua Intelligence knowledge base**, click **Upload file** and select the target project

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FTlIwnlMnwCDU8N6nkINM%2Fimage.png?alt=media&amp;token=10a44635-8dd7-4c69-a7c8-62fb8fdac0fd" alt=""><figcaption></figcaption></figure>

3. Upload and click **Add and Process**

Processing runs in the background. Processing status is shown directly in the interface — you will see whether a file is Processing, Ready, or has an Error.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FgMX9kpHsuw20XuoxURqo%2Fimage.png?alt=media&amp;token=480a75fd-b096-455b-8320-02d45c2af755" alt=""><figcaption></figcaption></figure>

#### **Supported file formats**

* PDF, DOCX, XLSX, Markdown, and TXT

#### **Reusing files across projects**

If the same file is relevant to multiple projects, you can reuse it without re-uploading.

To reuse a file:

1. Open the three-dot menu next to the file
2. Select **Share file**
3. Choose the projects you want to attach it to

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2F35iwaQaRQoXJLX0dovuD%2Fimage.png?alt=media&amp;token=73a23828-db14-47a9-a5f0-16cd96f29b25" alt=""><figcaption></figcaption></figure>

When a file is shared across projects:

* Deleting it from one project **removes** it **only** from that project
* The file remains **active** in **all other projects** where it is in use
* To remove it completely, delete it from **every project** it is linked to

#### **Managing your files**

* Regularly review and update files to ensure aqua Intelligence is working from current, accurate material

For guidance on preparing files for best results, see [Best practices for the Knowledge Base in aqua](/documentation/aqua-intelligence/knowledge-base-with-aqua-intelligence/best-practices-for-the-knowledge-base-in-aqua.md)


---

# 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.aqua-cloud.io/documentation/aqua-intelligence/knowledge-base-with-aqua-intelligence/project-knowledge-base-of-aqua-intelligence.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.
