> Index of every Falcon docs page, for assistants: https://falcon.com/docs/llms.txt

# Add a knowledge base

Add a knowledge base the company owns, or connect one that already lives in the company's account.

Open **Knowledge**. The page says **Documents your agents can look things up in, like help articles or policies. Each agent chooses which ones it uses.** The list ends with **Knowledge is about your company and the world; memory is about people. Knowledge never holds what members said.**

## Start

- Choose **New knowledge base**. With none yet, the page says **No knowledge bases yet** and **Add documents your agents can search for answers.**
- The new page is titled **New knowledge base**. It says **Documents your agents look things up in when they answer, like help articles, policies or product guides.**
- **How do you want to start?** is **Start a new one** or **Connect an existing one**.
- **Start a new one** says **Tell Studio where your documents are. It keeps your agents’ copy up to date.**
- **Connect an existing one** says **Already have one in your company’s account? You keep running it; Studio only reads from it.**

## Name it

The step is **Name it**. The note says **A short name your team will recognise, like “Help articles” or “Returns policy”.** The field is **Name**. **Who can change its documents** is folded under it. The note says **People allowed to edit this group of instructions can change it. Most keep the default.**

## Where the documents are

For a new base, the next step is **Where are the documents?** The note says **Pick where they live now. You can add more places later.** The choices are **Upload files**, **A website**, **Google Drive**, **SharePoint**, **GitHub** and **Amazon S3**. **Create and add documents** makes the base and adds what you picked. **Create without documents** makes it empty. **Choose the files** appears when files are still needed. The page then says **Created. Add documents and your agents can start using them.**

## Connect an existing one

- The step is **Which one?** The note says **Pick the account, then the knowledge base in it.**
- **AWS account**, then **Knowledge bases in this account** or **Knowledge base id** when the list cannot be read.
- The note says **It stays yours: you keep adding documents and pay for it in your account, and Studio only reads from it. Take Studio’s access away and its searches stop at once.**
- Choose **Connect**. The page says **Connected. Your agents can search it now.**

Until the name is filled, the page offers **Give it a name**. Until who may change the documents is chosen, it offers **Choose who can change its documents**. An agent uses the base only after a search is added. See [Knowledge searches](https://falcon.com/docs/knowledge-searches).

## Related

- [Build an agent](https://falcon.com/docs/build-an-agent)
- [Base agent parts](https://falcon.com/docs/base-agent-parts)
- [Write a skill](https://falcon.com/docs/write-a-skill)
- [Add a skill to an agent](https://falcon.com/docs/add-a-skill)
- [Skill categories](https://falcon.com/docs/skill-categories)
- [Knowledge searches](https://falcon.com/docs/knowledge-searches)
- [Start a workflow](https://falcon.com/docs/start-a-workflow)
- [Before the agent](https://falcon.com/docs/preprocess)
- [Agents](https://falcon.com/docs/agents)
- [Workflows](https://falcon.com/docs/workflows)