Knowledge collections (RAGs)

Knowledge in your workspace is the place to put text content your apps need but you want to edit without a developer in the loop — launch hooks, brand voice, FAQ snippets, customer profiles, anything an agent reads as context.

A RAG (Retrieval-Augmented Generation collection) is a named bundle of markdown documents. You manage them at Settings → Knowledge (/user/knowledge). Apps you install can bind to your RAGs through “slots” they declare in their manifest — the activation consent dialog asks which RAG to use for each slot, or lets you create a new one inline.

Why this exists

The same “Launch 2026” hooks might feed press-planner, the office assistant’s email drafts, and a social-manager. Without RAGs each app needs its own copy of the content and you re-edit three times. With RAGs, you edit once and every bound app pulls the updated text on the next call.

What a RAG holds

• Up to ~5000 documents per RAG, each up to 256 KB of markdown.
• Each document has a title, body, tags (free-form, case-sensitive), and optionally a source link to a workspace file (PDF, markdown, HTML, JSON, plaintext).
• Tags let apps filter — e.g. press-planner asking for hook_c gets only docs tagged that way.

Two ways to add a document

1. Inline: ”+ Neues Dokument” opens a markdown editor. Type or paste content directly, add tags, save.
2. From a workspace file: ”+ Aus Workspace” opens a picker over your tenant’s files. Pick a PDF or markdown file → the platform extracts the text once and caches it as the document body. The original file stays in your workspace; the RAG holds a snapshot.

Source-backed documents show a status banner in the editor:

• 🟢 Aktuell — the cache matches the source file’s last-modified timestamp.
• ⚠️ Veraltet — the source file was edited after the cache was taken. Click Aktualisieren to re-extract.
• 🔴 Quelle entfernt — the original file was deleted. The cache body stays; the document becomes an inline doc you can edit directly.

App bindings

The RAG detail page shows which apps are bound to it and via which slot. When you uninstall an app or unbind a slot, the RAG and its documents stay — only the binding row goes away. The RAG can be bound to a different app (or a different slot on the same app) later without losing content.

Permissions

• Reading RAG content is open to any member in your tenant.
• Creating / editing / deleting RAGs and documents requires the Admin or Owner role.
• Apps with scope: read on a slot can only call read tools. Apps with scope: read_write (an ingest app, e.g. a research collector) can also write documents via rag_upsert_document. You see the scope per binding on the RAG detail page.

For developers

The platform-side primitive (manifest declaration, tool surface, slot resolution semantics) lives at /developer/reference/rag.