Libraries

#Overview

A library is a standalone collection that groups files and folders in Knowledge for a particular purpose.

Folders answer the question where does this content live? Every file sits in one place in the centralized, file-system-like structure of the knowledge base. Libraries answer a different question: what belongs together for this piece of work? A library gathers related files and folders into a collection of its own, in a decentralized way — so material that serves a shared purpose can sit together without the underlying folder structure having to be rearranged around it.

That matters because Knowledge is not a document archive. It is the operational layer people and agents both work from, and the same content is often relevant to more than one team, project, or process. Libraries give you a second, more flexible way to assemble it, alongside the centralized structure rather than instead of it.

#Key Capabilities

• Group content as a standalone collection. A library is its own collection of files and folders, held alongside the centralized folder structure rather than inside a single branch of it.
• Organize in a decentralized way. Bring related content together for a specific purpose without reorganizing the folder structure that content already lives in.
• Assemble once, come back to it. A library persists as a named collection, so a set of material put together for a team, a project, or a recurring piece of work stays available to return to and share.

#How it Works

1. Start from a purpose, not a place. Libraries are worth creating when a set of material serves one clear purpose — onboarding a new client, running a quarterly review, supporting a product launch — and that material is spread across different parts of the knowledge base.

2. Group the files and folders that serve it. A library collects the existing files and folders themselves rather than duplicating them, so the content stays where it lives in the centralized structure while also being reachable as one purpose-built collection.

3. Keep using the centralized structure for everything else. Folders remain the primary organization of the knowledge base: they are where content lives, and how it is named, moved, and archived. Libraries sit alongside them as a flexible way to group content together.

#Additional Notes

• Choosing between a folder and a library. Use a folder when you are deciding where a piece of content should live. Use a library when you want to bring content from different places together for a particular purpose. Most teams end up using both.
• Getting knowledge to agents. Knowledge is put to work by adding files and folders to a space, where the agents operating there can retrieve and use them. That is covered in Knowledge for Agents and in Spaces.
• Short definitions of the terms used here are in one place: Glossary.

#Related Features

• Files & Folders — The centralized structure for adding, organizing, and managing content, which libraries complement. Files & Folders
• Knowledge Overview — How the knowledge system fits together, and where libraries sit within it. Knowledge Overview
• Knowledge for Agents — How agents retrieve knowledge as grounding context while working, and contribute documents back. Knowledge for Agents
• Spaces — The operational environment knowledge is added to, giving people and agents a shared context to work in. Spaces
• Access & Permissions — The full access model behind plans, role permissions, and per-resource permissions and sharing. Access & Permissions