Documents

The documents page is the workspace's library. Everything you upload is encrypted at rest, indexed for search, and usable from chat, agents, workflows, and analysis grids.

The library and its three kinds of folder

Every folder tree is one of three kinds, chosen when its top-level folder is created and a document always has the visibility of the folder it lives in:

A document in your private folders is invisible to everyone else, admins included, the only time they become visible is within the data package provided when the owner performs a full export of data from Ferrith. Agents folders keep agent knowledge material out of everyday browsing, they're the folders an agent can be linked to.

A document's kind is fixed when it's uploaded. To move something from private to workspace, upload it to a workspace folder if you have the required permissions.

Upload, versions, and re-process

1. Click Upload, choose the destination folder, and pick the file (PDF, Word, Markdown, or plain text).
2. The document appears immediately with a Processing chip while it's read and indexed. If processing fails, the chip says why in plain words, and Re-process retries it.
3. To update a document, upload a new version on the document itself rather than uploading a separate file. Earlier versions are kept and anything that referenced the old version (a conversation, an agent's knowledge base) keeps working against exactly what it referenced, while new uses get the latest.

Advanced parsing (Automation plan) reads difficult PDFs properly, complex tables, and scanned documents via text recognition. Re-processing a document applies it retroactively.

Folder access: who can read, who can edit

On workspace folders, admins control two things (folder → Access):

• Who can read. A restricted folder is visible only to the members and roles on its list. Everyone else doesn't see it at all.
• Who can edit. Separately, an edit list names who may upload into the folder, add new versions of its documents, and delete its documents (to the workspace recycle bin). Edit access includes read access. With no edit list, only admins write there.

Subfolders inherit their parent's lists and can only narrow them, a subfolder can't be opened wider than its parent. Changing a folder's access applies down its whole tree.

Moving documents and folders

Moving things is folder housekeeping, kept separate from editing content: admins arrange workspace trees, agent authors arrange Agents trees, and you arrange your own private folders. Documents move only between folders of the same kind — visibility never changes.

The recycle bin

Deleting a document moves it to the bin, where it stays restorable for 30 days: your bin for private documents, the workspace bin (admins) for shared ones. After 30 days it's deleted fully; deleting from the bin, or choosing permanent delete in the first place, removes it immediately.

Binned documents still count toward the workspace's storage.

Storage

Your plan includes a storage allowance (expandable from the account portal). A banner appears on this page as the workspace passes 80%, 90%, and 100% of it. At the limit, new uploads pause, nothing already stored is ever deleted or locked, and reading, chat, and search continue as normal. Free space (empty the bins, delete old versions) or add storage, and uploads resume immediately. Admins get a full breakdown, including per-member private storage size and what's sitting in bins.

Workflow inputs (admins)

Documents uploaded for workflow runs, through a workflow's form, or through the API by an integration, are kept apart from the library and count toward storage. Admins can see all of them behind Workflow inputs at the top of the Documents page. Each card shows the same facts and actions as a library document, plus the document's id and version id (with Copy buttons as these are what an integration passes to a run via the API), where it came from (Uploaded by a member, or an API badge naming the key), and the latest run that used it, with +N more when other runs used it too. In use / Not used yet finds the ones no run needs. A document a run still references can't be deleted while that run exists: an admin deletes those runs first (Delete run on a finished run's page), and the document goes with the last of them. The rest can be moved to the bin or deleted permanently.

Finding things

The library filters by folder and searches titles, content of files is not included in the search.