Documentation
Folders and versions
Folders — the core concept
It's folders and files, all the way down. A top-level folder is the unit an agent connects to and reads from, and it nests folders and files inside it, just like a filesystem. History is kept per document: each document has its own line of versions, so editing one never rewrites another and nothing is ever silently overwritten. A folder is a location, not a version. Everything else in this console — Files, Permissions, Access, Audit — is scoped to whichever top-level folder you have selected in the switcher at the top of the Files view. Permissions attach to folders and inherit down the tree, so you set access at the coarsest level that works and let nesting carry the rest.
example is just the default folder name the console falls back to on first load. It may not exist yet in your organization — if the Files view looks empty, you probably need to create your first top-level folder.
A top-level folder comes into existence the moment it gets its first content, so there's no separate "create empty folder" step — you name it and add files in one flow:
- 1Go to Files and click New top-level folder (top-right — admins only).
- 2Enter a name — lowercase letters, digits, dash, underscore or dot (e.g.
acme-handbook). This is the identifier your agents will use. - 3Drop in one or more files and click Create folder. The folder is created with that first commit, and the console switches to it automatically.
The uploaded files are live immediately, and reachable by you — uploading grants you each new document. Widen that in Permissions (see the lifecycle below).
How content goes live
New content — whether uploaded here or synced from a Connection — is live the moment it lands. What decides who can see it is not a review step but the grants written at that moment:
Uploading a file grants you access to it. Connecting a source grants the readers you chose at install. Nobody else can read any of it until you widen that in Permissions — which is the same mechanism that governs every other file, so there is one place to look and one answer.
There used to be a quarantine step here, and a Triage inbox to clear it. It was a second visibility system beside this one, and the two disagreed: the file tree listed content the editor then refused to open. Reach is the only gate now.