Skip to main content
A knowledge base grows fast. Folders let you keep it shaped — by topic, by brand, by project — so when you attach documents to an agent you can grab a whole group instead of clicking through dozens of individual files.

​
Creating folders

Open the Knowledge base page and choose Create folder. Give it a name. To nest, open the parent folder first, then create the new folder inside it. Names must be unique among siblings. Slashes (/) aren’t allowed in folder names — they used to be path separators in our legacy URL scheme, and a slash today would make folder breadcrumbs ambiguous.

​
Moving documents into folders

From a document’s three-dot menu, choose Move to folder… A folder picker opens. Pick the destination and confirm. The document’s status doesn’t change; only its placement does.

​
Deleting a folder

The delete confirmation has two modes:
  • Move contents to parent (default) — your sub-folders and direct documents shift up to the deleted folder’s parent. Nothing is lost.
  • Delete everything inside — the entire subtree is removed. Direct documents fall back to the root of the knowledge base rather than being deleted (no implicit data loss).
Pick the default unless you really mean it.

​
URLs and deep linking

Every folder has a stable URL like /knowledge-base/<folderId>. Rename the folder and the link still works. Share the URL with a teammate and they land in the right place.

​
Folders and agents

Folders are an org-level Knowledge base concept. The per-agent Knowledge base tab shows a flat list of the documents attached to that agent — there is no folder tree in the agent view. Attachments are per-document: detaching a document from an agent leaves it in its org-level folder, and deleting a folder does not automatically detach its documents from agents.