> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/knowledge-bot/functional-documentation/functional-capabilities/knowledge-bots.md).
# Knowledge Bots
A *Knowledge Bot* is a specialized chatbot that leverages a specific database to generate responses to user queries. It is designed to provide targeted, relevant answers based on the data it has access to.
#### 5.2.1 Knowledge bots listing
The listing page displays all the Knowledge Bots available within the current application. The most recently created bots appear at the top of the list. Users can view detailed information, edit, delete, or add new Knowledge Bots.
The list includes the following details for each bot:
* ID
* Name
* Logo (if available)
* Creation date
* Creator’s user role
***Access Roles:***
* **Super Admins**: Can view and manage Knowledge Bots within the current application (he has access to all applications).
* **Admins**: Can view and manage all Knowledge Bots within the current application.
* **Knowledge Managers**: Can view only the Knowledge Bots assigned to them; they do not have permissions to add, edit, or delete.
* **Support Admin:** The Support Admin role is designed to provide full system-wide oversight and control. It enables seamless management across all applications and their associated Bots, ensuring smooth operations, governance, and support across the platform.
* **Agents**: Do not have access to this page.
#### 5.2.2 Add / Edit Knowledge Bot
Only *Super Admins* and *Admins* have permission to create, update, or delete Knowledge Bots.
When creating a new bot, a modal window will open containing the input fields:
* **Name**: The name of the Knowledge Bot.
* **Answer Language**: The default language used by the knowledge bot to respond.
* **Client-specific Instructions**: Additional rules or guidelines for the chatbot.
* **Output Length**: Specifies the approximate length of responses in characters, influencing the level of detail.
* Small: 50 characters
* Medium: 200 characters (default)
* Large: 1,000 characters
* Extra Large: 10,000 characters
* **Formality:** Sets the tone of responses.
* Informal (default)
* Formal
* **Expertise:** Sets the level of details in response.
* Low
* Medium (default)
* High
* **Design:**
* **Logo**: Upload a logo (supported formats: PNG, JPG; max size: 7MB)
* **Background Color**: Customizable via a color picker.
* **Left menu Background & Text Colors**: Customizable via a color picker.
* **Data Masking Fields:** If data masking is activated in the application, a list of available masking flags is provided for selection to secure sensitive information.
* The platform provides a **data masking configuration section**, where administrators can define which entities should be masked when uploading data sources.\
Common examples of maskable entities include:
* Phone numbers
* E-Mail addresses
* Locations
* Dates and times
* When creating a K‑Bot, selected masking entities act as **default settings**. This means that during future uploads, administrators do not need to repeatedly configure the same masking rules for each document.
The design fields allow customization of the chat interface’s appearance, including colors.
When editing an existing Knowledge Bot, the same modal appears with pre-filled information.
To delete a Knowledge Bot, a confirmation modal prompts the user to verify the action by entering the bot’s name.
#### 5.2.3 Knowledge Bot details
The *Knowledge Bot Details* page displays all information about the selected bot: general details and data sources from the current knowledge bot, which will be detailed in *5.3 Data sources.*
The general details of the knowledge bot are:
* Logo and Name
* Creator’s Name
* Answer Language
* Response Output Length
* Creation Date
* Expertise Level
* Application Name
* Formality Level
* Total Data Sources: Number of Files / Web Pages
* Data Masking Status (Enabled / Disabled)
If *Data Masking* is enabled, a tooltip shows the specific flags applied.
If *Client-specific Instructions* are provided, a dedicated section displays these instructions.
#### 5.2.4 PII data masking
Personally Identifiable Information (PII) Data Masking is a feature that can be enabled or disabled at the application level.
When adding or editing a Knowledge Bot, if Data Masking is enabled for the application, users can configure specific masking rules for that bot. These flags are used to anonymize or protect sensitive questions in Chat before they are sent to the LLM.
On the Knowledge Bot details page, if masking flags are in use, the Data Masking field will be *Enabled*. Clicking the info icon reveals which flags are applied, ensuring users understand what data is being protected.
**Predefined Masking Entities**
When creating a Keybot, you may have already selected default masking entities. These act as a **shortcut**:
* They are **automatically applied to newly uploaded documents**
* They eliminate the need to reselect commonly used entities each time
**Document-Level Masking**
You can also apply **additional masking entities** to individual documents:
* These settings apply **only to the selected document**
* They do **not affect other files in the batch**
Example:
* If you select “Crypto” masking for one document, it will **not apply** to others
**Saving Configuration**
Once masking preferences are selected:
1. Click **Save**
2. The ingestion process will begin
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ixhello.com/knowledge-bot/functional-documentation/functional-capabilities/knowledge-bots.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.