> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/channels-integrations/dialogue-ai-assist/manage-dialogue-ai-assist-knowledge-bases.md). # Manage Dialogue AI Assist Knowledge Bases Create, process, and maintain Deepdesk Knowledge Bases for Dialogue AI Assist assistants. Knowledge Bases provide controlled source material for Dialogue AI Assist assistants. Use them when an assistant must answer from your own content, such as public web pages, PDF documents, or documents uploaded through an API. Knowledge Bases are managed from **Admin Settings** > **Knowledge Base**. After a Knowledge Base is created and processed, attach it to an assistant from **Behavior** > **Knowledge** when that option is available in the environment. ## Create a Knowledge Base Choose a name and code for the Knowledge Base. | Field | Description | | -------- | ------------------------------------------------------------------------------------------------------------- | | **Name** | Required. Helps administrators recognize the Knowledge Base in the portal. The name is not visible to agents. | | **Code** | Identifies the Knowledge Base in configuration and should be unique. | {% hint style="warning" %} The code must be unique for each Knowledge Base. Use a stable code so assistant configuration can continue to reference the Knowledge Base. {% endhint %} Knowledge Base edit pages use a route pattern similar to: ``` /admin/settings/knowledge-base/assistant/[code] ``` ## Configure answering behavior Configure guidance for how answers should be generated from the Knowledge Base. Use clear wording that tells the assistant to answer from the provided source material and to avoid guessing when the source does not contain the answer. ``` Use the provided context to answer the user's question. If the answer is not available in the provided context, say that you do not know. Do not make up an answer. ``` Example fallback answer: ``` I do not know. ``` ## Process sources Source processing scans and analyzes the online sources or PDFs added to the Knowledge Base. This processing extracts and comprehends information from the sources so the Knowledge Base can generate relevant responses. The page shows processing status and last job details. Select **Start Processing** when sources are added or changed so the Knowledge Base uses the latest content. {% hint style="warning" %} Processing duration depends on the size and complexity of the sources. Process sources again after source content changes. Plan ahead for product launches, policy changes, and large content updates so assistants do not rely on outdated Knowledge Base content. {% endhint %} ## Manage Knowledge Base sources Knowledge Base sources are organized in **Online Sources**, **PDF Sources**, and **API** tabs. ### Online sources Add URLs of publicly available sources, such as a website or community page. 1. Open the **Online Sources** tab. 2. Add one URL per line in the text area labelled **urls**. 3. Select **Save**. 4. Start processing after sources are added or changed. ### PDF sources PDF sources are accessible to Deepdesk users and cannot be shared or viewed by external parties, such as customers. 1. Open the **PDF Sources** tab. 2. Drag PDFs into the window to upload, or select **Add PDF**. 3. Review the PDF table. The table contains a **Name** column, row actions to open or delete a PDF, and pagination. 4. Start processing after PDFs are added or changed. ### API sources API sources are documents uploaded through the API. The API table contains **Title**, **Url**, and **Last Crawled**. When no API sources are available, it shows **No rows**. ## Attach a Knowledge Base to an assistant 1. Go to **Agentic AI** > **Assistants**. 2. Open the assistant that should use the Knowledge Base. 3. Open **Behavior** > **Knowledge**. 4. Use **Select a base** to connect the assistant to the Knowledge Base or decision tree. 5. Test the assistant with representative questions before production use. ## Delete a Knowledge Base Deleting a Knowledge Base permanently removes its configurations, settings, and sources. {% hint style="danger" %} Deleting a Knowledge Base is permanent. Save any required configuration details or source records elsewhere before deleting it, and confirm that no assistants still depend on the Knowledge Base. {% 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://atlas.anywhere.now/channels-integrations/dialogue-ai-assist/manage-dialogue-ai-assist-knowledge-bases.md?ask=&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.