Use with Agent

After binding a knowledge base to an Agent, the Agent can search and read authorized materials in multi-step tasks; when it is clear that the materials need to be updated, knowledge base management can also be enabled.

Ordinary conversations are suitable for one-time Q&A, while Agents are suitable for ongoing research, comparison, file generation, and step-by-step acceptance. An Agent only accesses the knowledge bases bound in its configuration.

The difference between ordinary conversations and Agents

Ordinary conversation	Agent
Temporarily select a knowledge base before each message	Long-term binding in the Agent configuration
Suitable for immediate Q&A and short comparisons	Suitable for multi-step research and file delivery
Mainly answers using retrieved excerpts	Can search materials and manage knowledge bases by permission
The current conversation determines the scope of materials	The Agent configuration determines the accessible scope

Configure a read-only knowledge base Agent

1

1. First make sure the knowledge base has passed acceptance

Confirm that the target materials are ready, and use real questions to complete retrieval testing. The Agent cannot make up for missing full text or incorrect chunking.

2

2. Open the Agent editing window

Go to [Work], select the target Agent, and open [Edit Agent] from the menu.

3

3. Bind the minimum necessary knowledge base

Open the [Knowledge Base] tab and click [Add Knowledge Base]. Only bind the libraries needed for this task to avoid interference between materials from different departments or versions.

4

4. Enable knowledge base search

Open [Built-in Tools] and enable [Knowledge Base Search]. For read-only research, Q&A, summarization, and comparison, this is usually enough.

Search is for reading, management is for changing materials; start with the minimum permissions by default.

5

5. Test with a clearly bounded task

Ask the Agent to list sources first, then give the conclusion; if the materials do not support it, state that clearly and do not fill in the gaps from common sense.

6

6. Verify sources and deliverables

Check which knowledge base each conclusion comes from, whether facts and recommendations in the file are separated, and whether unsupported parts are marked.

How to choose between built-in tools, knowledge bases, skills, and MCP

Use a knowledge base to look up information, skills for repeatable methods, and MCP to access external systems; do not use expanded permissions to replace a clearly defined task.

Knowledge base search and management

Capability	What it can do	Applicable tasks	Default recommendation
Knowledge base search	Search, list, and read bound knowledge bases	Q&A, research, summaries, comparisons	Keep enabled
Knowledge base management	Add, delete, or refresh knowledge base documents	Approved material maintenance	Disabled by default, enable temporarily as needed

Binding a knowledge base only grants access scope; it does not copy out another knowledge base. After materials are updated or re-indexed, the Agent's next search will use the updated content.

After enabling [Knowledge Base Management], adding, deleting, and refreshing will change the materials or the index. Before approval, confirm the target knowledge base, the specific entries, how same-name conflicts will be handled, and the rollback plan.

How the Agent's configurations work together

The model determines understanding and generation, the knowledge base provides evidence, and permissions determine how far the Agent can act.

Recommended task templates

Research and generate a report

Find all rules about overseas business trip approvals and insurance in the bound knowledge bases. First list the sources and conflict points, then generate a Markdown checklist. Do not fill in unsupported content.

Update FAQ

Search the existing items for accommodation reimbursement and compare the latest policy with the old FAQ. First provide a list of proposed changes; after approval, refresh the relevant documents.

Comparison across multiple knowledge bases

Find evidence separately from the "Product Manual" and "After-sales Cases" knowledge bases, and organize it into three columns: "Official rules / Real cases / Suggested wording." Keep the source name for each conclusion.

Configuration notes

Configuration item	Recommended starting point	When to add	Risk control
Bind knowledge base	1 task-related library	There is a real need for cross-library comparison	Write the purpose of each library clearly in the prompt
Knowledge base search	Enable	As long as the task requires looking up materials	Verify whether the sources come from the bound scope
Knowledge base management	Disable	Explicitly need to add, delete, or refresh	Approve item by item, and back up important materials first
Output requirements	Separate facts, inferences, and recommendations	Need to generate a report or file	Keep the source name for each fact

User case

Xiaolin bound [Official Manual] and [Review Cases] to the after-sales Agent, and only enabled knowledge base search. He asked the Agent to list safety warnings, official steps, and case recommendations by device model, and keep the three separate. Only when he found old cases that needed updating did he temporarily enable the management tool, first review the list of proposed changes, and then approve it.

The acceptance standard is: the Agent does not access unbound materials, does not write case recommendations as official rules, and all write operations have a clear target and acceptance result.

Result acceptance

• Sources come only from the knowledge bases currently bound to the Agent.
• Search results cover every condition in the task.
• The deliverable separates material facts, Agent inferences, and recommendations.
• The management operation explains the target, impact, and result.
• After updating the materials, rerun the fixed retrieval questions.

Common questions

Why can ordinary conversations find it, but the Agent cannot?

Check whether the target knowledge base is bound to the current Agent, and whether [Knowledge Base Search] is enabled. The bound scope of different Agents is not inherited from one another.

When should knowledge base management not be enabled?

For read-only research, team-shared policy libraries, and material libraries that retain historical versions, only search is enabled by default. When updates are needed, temporarily enable management and approve item by item.

What should I do if the Agent wants to operate on an unbound knowledge base?

Do not expand to all knowledge bases. After confirming the task truly requires it, add the target library to the current Agent, or switch to an Agent that already has that library bound.

Continue reading

Use in conversation

Complete one immediate, source-backed Q&A.

Data, privacy, and maintenance

Understand the boundaries of permissions, cloud services, and backups.

Knowledge base application cases

Refer to after-sales and research workflows.