> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/knowledge-and-retrieval/share-and-reuse-a-knowledge-base.md).

# Share and reuse a knowledge base

Share a knowledge base so several agents and workflows can search the same collection. Maintain its documents, images, and audio recordings in one place.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2F1hcUG7CT7yPW7i4uAoAM%2FG042.mp4?alt=media&token=d62d73d9-e6da-4cc9-aeff-9b2b575e9cce>" %}

## Before you start

Open an existing knowledge base with permission to manage its sharing. Review [Source permissions](https://docs.stackai.com/guides-and-quickstarts/knowledge-and-retrieval/source-permissions.md) if the sources have different reader access, and identify the agent or workflow that will reuse it.

## Share the knowledge base

Open Share, review General Access, and add the intended collaborator with the required role.

![Knowledge base sharing controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/mqEDH9yhSiFmf2mc4PCY/assets/g042-g042-01-share.png)

Save Changes after confirming the person and permission level.

Have the collaborator open the knowledge base with their own account.

![Knowledge base sharing controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/80gW5YROVpyAd1OcX1ld/assets/g042-g042-02-access.png)

Consider any broader organization permissions when evaluating what that account can do.

## Connect it to an agent

In the agent's Knowledge area, choose Add Knowledge Sources → Add Knowledge Base and select the existing base.

![Agent knowledge base selection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/B65f2oGjK7Bh4cKz45pq/assets/g042-g042-03-attach.png)

This reuses the managed collection instead of creating another copy of its files.

## Review a sourced answer

Ask a question covered by the connected knowledge base and open Sources.

![Agent answer source inspection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/JxBllxX7sY1HxiAQ3Pzh/assets/g042-g042-04-sources.png)

Compare the answer with the cited passage to confirm it is grounded in the shared content.

## Find projects that use it

Open References on the knowledge base to see its consuming projects.

![Knowledge base project references](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/t4VzShjrsKdkV7iS8nKG/assets/g042-g042-05-references.png)

Access to the knowledge base does not automatically grant access to those projects.

## Important behavior

Knowledge-base access and project access are separate. Sharing the base does not automatically share projects that use it.

## Continue

* [Source permissions](https://docs.stackai.com/guides-and-quickstarts/knowledge-and-retrieval/source-permissions.md)
* [Inspect knowledge base references](https://docs.stackai.com/guides-and-quickstarts/knowledge-and-retrieval/inspect-knowledge-base-references.md)


---

# 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://docs.stackai.com/guides-and-quickstarts/knowledge-and-retrieval/share-and-reuse-a-knowledge-base.md?ask=<question>&goal=<user_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.
