Knowledge bases

A knowledge base is a named collection of files. It doesn't copy anything. It points at files that already live in your Library.

Why use them#

• Focus. An agent that only needs HR documents shouldn't wade through engineering notes.
• Reuse. Pick “Finance” in a playbook, an agent or a search, instead of listing files.
• No duplicates. A file can belong to many knowledge bases, or none.

You don't need a knowledge base to use a file. Files in the Library can be used directly.

Create one#

1. Open Brain › Knowledge bases and create a new one.
2. Choose Add from Library.
3. Tick individual files, folders, or both.
4. Give it a clear name and description.

You can also upload straight into a knowledge base. The new file lands in your Library and joins the collection in one step.

Folders are live#

Select a folder and it includes everything inside, and files you add later. Select individual files for a fixed list.

Rules that keep it safe#

• A collection only narrows. It never widens. Putting a file in a knowledge base doesn't give anyone access to it. Sharing is a separate, deliberate step, done from the file.
• Both checks must pass. To use a file through a knowledge base, a person needs access to the collection and to the file.
• Empty means empty. If nothing in a knowledge base matches or is permitted, the result is empty. Space never quietly searches everything else instead.
• Removing is gentle. Taking a file out of a knowledge base leaves the file and its other memberships alone. Deleting a knowledge base deletes only the grouping, not your files.

Sharing a knowledge base#

You can share a knowledge base so others can see and use the collection. Because membership doesn't carry access, each person still needs access to the files inside. Share the files too (or put them in group or organization scope).

Using them#

Scope#

Like other resources, a knowledge base is personal, group or organization. See Sharing and access.