# How to add Multiple Knowledge Bases & link AI Agents

<figure><img src="/files/3ZIjvSnDJQyJAZTWhse9" alt=""><figcaption></figcaption></figure>

In Tiledesk, you have the flexibility to manage multiple Knowledge Bases (KBs) using namespaces. This feature is incredibly useful for organizing different sets of information and ensuring that specific AI Agents have access to the relevant data. This tutorial will guide you through the process of creating and managing multiple namespaces for your Knowledge Bases in Tiledesk.

#### **Purpose of Multiple Namespaces**

* **Organization**: Separate different types of content, such as FAQs, technical documentation, and product-specific information.
* **AI Agent-Specific Knowledge**: Ensure that each AI agent only accesses the relevant Knowledge Base, improving the accuracy and efficiency of responses.
* **Scalability**: Easily manage and scale your Knowledge Bases as your content grows.

#### Step 1: Log in to Tiledesk and navigate to the Flows Section <a href="#step-1-log-in-to-tiledesk-and-navigate-to-the-bots-section" id="step-1-log-in-to-tiledesk-and-navigate-to-the-bots-section"></a>

1. Open your web browser and navigate to [Tiledesk](https://www.tiledesk.com/).
2. [Log in](https://panel.tiledesk.com/v3/dashboard/#/projects) with your credentials.&#x20;
3. From the left-side menu, click on the **Knowledge Base** with the brain icon.

#### Step 2: Understanding the Default Namespace <a href="#step-2-understanding-the-default-namespace" id="step-2-understanding-the-default-namespace"></a>

In the new page, you will see the list of knowledge bases on the left side. By default, you have a knowledge base ready to be populated, but you can add more.

<figure><img src="/files/H9WnH0lmfyPedbdPuVJH" alt=""><figcaption></figcaption></figure>

### Managing Multiple Knowledge Bases <a href="#managing-multiple-knowledge-bases" id="managing-multiple-knowledge-bases"></a>

#### **1. Changing the Knowledge Base Name (o**ptiona&#x6C;**)**

**Purpose**: Rename the default namespace to better reflect its content.\
**How to Change**:&#x20;

* Click on “**Default**”.&#x20;
* Enter the desired name for your Knowledge Base; it'll automatically get saved.

#### **2. Adding a New Knowledge Base**

**Purpose**: Create additional namespaces for different sets of content.\
**How to Add**:

* From the left-side menu, click on "+ New Knowledge Base".
* In the pop-up window, you have the option to choose the type of knowledge base.
* Enter the name for the new Knowledge Base and click on Create, as shown below.

Note, you can build a standard or [Hybrid search](/ai-chatbots-and-automation/knowledge-base/hybrid-search.md) engine. [You can read more about it here](https://tiledesk.com/blog/tiledesk-hybrid-search-rag-architecture/).

<figure><img src="/files/OlwG0JiNnMd8zkVXzN9N" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/c2durWjK8mHczS7PC5hE" alt="" width="375"><figcaption></figcaption></figure>

**3. Viewing and Switching Between Knowledge Bases**

**Purpose**: Easily navigate between different namespaces to manage or view their contents.\
**How to Switch:**

* From the left-side menu, under Your Knowledge Bases, choose the desired Knowledge Base
* The content and configuration for the selected namespace will be displayed
* Also, you can see which AI agent is connected to this Knowledge Base

<figure><img src="/files/tOmRpUccgi5lf3xf5YGP" alt=""><figcaption></figcaption></figure>

#### Deleting Namespaces <a href="#deleting-namespaces" id="deleting-namespaces"></a>

To empty the entire namespace, simply click on the red Delete button, as shown below.&#x20;

You can also choose to remove the namespace altogether by ticking the box “Also delete the Knowledge Base”.

<figure><img src="/files/A3l47B8vW3KDMdcXhlWR" alt=""><figcaption></figcaption></figure>

**Assigning AI Agents to Knowledge Bases**

1\. When you select a specific namespace, you will see which AI Agent is connected to that particular Knowledge Base.

<figure><img src="/files/4kvq9oLWsLlk5BsXADx2" alt=""><figcaption></figcaption></figure>

\
2\. To assign an AI Agent to a different Knowledge Base:\
&#x20; \- Go to the **Flows** section.\
&#x20; \- Select the AI Agent you want to configure.\
&#x20; \- In the agent flows, choose the appropriate [Block](/ai-chatbots-and-automation/visual-builder-101/how-to-create-a-block.md) with the [Ask Knowledge Base](/ai-chatbots-and-automation/actions-explained/ask-knowledge-base.md) feature containing the linked namespace.

<figure><img src="/files/EEfQl8Pp5hiHm06mT1zF" alt=""><figcaption></figcaption></figure>

#### **Best Practices for Using Multiple Namespaces**

\- **Categorize by Topic**: Create separate namespaces for different topics or departments to keep information organized.\
\- **Agent-Specific KBs**: Assign specific Knowledge Bases to AI agents designed for particular functions, ensuring they have access to the most relevant information.\
\- **Regular Updates**: Regularly update and review each namespace to ensure that the information is current and accurate.

#### Conclusion <a href="#conclusion" id="conclusion"></a>

Using multiple namespaces for your Knowledge Bases in Tiledesk allows for better organization, targeted information delivery, and scalability. By following this tutorial, you can efficiently create, manage, and utilize multiple Knowledge Bases, enhancing the overall performance and effectiveness of your Tiledesk AI Agents.

Send your feedback to <info@tiledesk.com> 👋


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.tiledesk.com/ai-chatbots-and-automation/knowledge-base/how-to-add-multiple-knowledge-bases-and-link-ai-agents.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.