> For the complete documentation index, see [llms.txt](https://comunity.gitbook.io/learning.comunitynexus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://comunity.gitbook.io/learning.comunitynexus/26.2/toolkit-guides/intelligence/add-knowledge-to-an-agent.md).

# Add knowledge to an agent

Knowledge is the material an agent reasons against, as distinct from the data it reads through tools.

Tools reach records: a fault, a claim, a user profile. Knowledge holds the material that says how those records should be treated, such as a business policy, an HR process and procedure document, or a set of standards the agent has to apply. An agent asked whether a claim was handled correctly needs both: the claim from a tool, and the policy from knowledge.

It is found under **Intelligence (Preview)**, then **Knowledge Management**.

## Before you start

* A provider, because knowledge is scoped to one. Until one exists, Knowledge Management shows only a prompt to create one. See [Set up a provider and deploy a model](/learning.comunitynexus/26.2/toolkit-guides/intelligence/set-up-a-provider-and-deploy-a-model.md).
* The files already present in your Azure instance. Knowledge does not upload from your own machine.

## What Knowledge Management holds

| Part                | Purpose                                                       |
| ------------------- | ------------------------------------------------------------- |
| **Knowledge bases** | Named collections of material made available to agents.       |
| **Files**           | The documents themselves.                                     |
| **Vector stores**   | The embedded form of that material, which the model searches. |
| **Indexes**         | The searchable structures built over it.                      |
| **Connections**     | Links to where the material is held.                          |

Knowledge is scoped to a provider, so what you set up is available to the agents built under that provider.

## Add knowledge

Knowledge passes through to the same setup a person would perform in Azure AI Foundry directly. The concepts are Foundry's rather than the Toolkit's, and the process is a technical one.

{% hint style="info" %}
Knowledge was not part of the core scope of this release, and parts of it are not yet complete.
{% endhint %}

## Where to go next

* [Create a tool](/learning.comunitynexus/26.2/toolkit-guides/intelligence/create-a-tool.md): reach records, as distinct from the material here
* [Create an agent](/learning.comunitynexus/26.2/toolkit-guides/intelligence/create-an-agent.md): the role that applies this knowledge