Files

Files is where the documents and data files you and Ronja produce are kept. Open it from the Files entry in the sidebar (just below Apps). It’s a folder browser: folders on top, files inside them, with a search box across the top.

What lands in Files

Files arrive five ways:

You save something in chat. Ask Ronja to save a result — “save this as a CSV”, “bundle those exports into a zip” — and the file lands in Files. Any file type works: the name Ronja gives it decides what it is.
A workflow produces output. Reports and exports a workflow run generates are written to Files, whatever their type. If the workflow is set up to write to a specific folder, they land there; otherwise they go to a per-workflow subfolder — named after the workflow — under a shared Workflow outputs folder, where the people who can see the workflow can read them.
Ronja opens a picture or a drawing. When she looks at an image or a CAD drawing during a conversation, the picture she rendered in order to see it is saved as a file of its own — a drawing’s under the drawing’s own name with -preview.png on the end — so the conversation still shows it when you reopen it later. It lands at the top level of Files, not in the folder the original sits in, and it is visible to the whole organization like any other saved file — even when the original is in your private My Files.
Ronja writes a document. When you ask for a write-up — “draft a monthly report” — she authors a formatted document (see Explorations) and saves it as a file you can reopen later.
Someone emails an attachment to a connected mailbox. When Ronja opens what a sender attached — because an automation ran on the message, or because you asked her to in a conversation — the attachment becomes a file here. These are the one kind of file that is not visible to the whole organization: only whoever (or whatever) pulled it in, and your admins, can see it, because mail belongs to the mailbox rather than to everyone. An attachment that arrived by mail — through a connected mailbox, or on mail sent to your organization’s Ronja address — is cleaned up 1 year after it arrives unless somebody moves it into a folder, which keeps it for good (see Limits and retention).

The Owner column tells you where each file came from: You for your own, a colleague’s email address for theirs, and — for a file a machine produced — the name of the automation or Agent that wrote it, with an AUTOMATION or AGENT tag beside it.

Data files you upload in a conversation are different: CSV and Excel become tables, while images and text ride along as context (an image Ronja opens also leaves the rendered picture behind as a file — see above). Those are covered in Upload files.

A zip you attach — or one that arrives on an emailed attachment — is unpacked automatically while it’s small, and the files inside land in Files like any other. A large archive isn’t unpacked at all: Ronja lists what’s in it and unpacks on request, so you decide whether you want all of it or a few named files. Password-protected archives are listed but can’t be opened. See Zip archives.

My Files — private by default

Everything you save without naming a shared destination goes into My Files, your personal folder. My Files is private to you — other members can’t see or open what’s there. The one thing that escapes it is the picture Ronja renders when she opens an image or a drawing you keep there: that preview lands at the top level of Files, where everyone can see it (above).

To share something, ask Ronja to save it into a shared folder, or move it there (below).

One exception: a chat filed into a project that has a folder attached saves there instead of My Files, so the project’s members can find it. Every member of the project can open that folder, and its Full access members can save into it (below); if you’re there on View, your own saves fall back to My Files rather than failing. A named folder path still wins over the default either way, and asking Ronja to save it to your private home keeps it in My Files.

Folders and who can reach them

Shared files live in folders. A folder decides who can see the files inside it, and access flows downward — reach a folder and you reach its subfolders too.

Admins create the top-level folders and manage their access. Open a folder and an admin sees its Access panel (who can read and write) alongside a Written by list showing which workflows produce files there. You can create a subfolder inside any folder you have write access to.

Granting access to a folder or file is browser-only — it refuses an API token, the CLI and automations, because it expands who can reach your files. Removing a grant narrows access and stays scriptable, as does reading who has one. See Actions the API can’t take.

A folder attached to a project is reachable by that project’s members too, along with its subfolders and the files inside — that is how a project’s chats save their outputs somewhere the whole team can find them. What each member gets matches their access to the project: Full access reads and writes, View reads. It won’t show up in the Access panel, because it isn’t a grant: it comes from the project’s member list, so adding someone to the project hands them the folder and removing them takes it back. (Which folders are listed in the browser hasn’t changed — what the project adds is reach into the files.)

That access covers what’s in the folder, not the folder itself: members can save files there and create subfolders, but renaming, moving or deleting the folder needs write access of your own — or Admin. Pointing a project at a folder is held to the same line, so a folder you can only reach through one project can’t be handed on through another.

Opening a folder changes the page address, so your browser’s Back and Forward buttons step through the folders you’ve visited, and you can bookmark a folder or paste its link to a colleague — they’ll land in it if they have access to it.

A workflow doesn’t reach a shared folder on its own — it’s granted access when its build is reviewed. The draft review dialog has an Access changes section listing exactly which folders the workflow will be allowed to write to, so an approver sees the access being granted before it goes live. See Propose and review changes.

Long lists

A folder shows the first 500 subfolders and the first 500 files it holds. When there are more, a Load more folders or Load more files button appears at the end of that list with the number still to come — Load more folders (120). Click it to add the next batch below what’s already there; keep clicking until the button disappears and you’re seeing everything. Opening a different folder, searching, or flipping Everyone’s files starts the list fresh.

Moving files

Ask Ronja to move a file — “move the July report into the Reports folder” — or use the move action in Files. Moving a file needs write access to the file and to the destination folder. Moving a file into My Files makes it private: any broad sharing it had is dropped so only you can reach it.

Downloading

Not everything has to be saved to be read. Beside each file’s download control is Open in new tab, which opens the file in a new browser tab — so a PDF, an image or an HTML page is readable straight away, and anything the browser can’t render is downloaded instead, in the format the app that opens it expects. (Inside a conversation, Ronja opens a PDF or an HTML page in a side panel beside the chat rather than a new tab; the PDF panel’s own header carries Open in new tab and Download alongside the full-screen and close controls.) A zip Ronja saved for you stays a zip: the automatic unpacking above applies only to archives that arrive, attached to a chat or an email.

Most files download directly — click the download control and you get the file exactly as it was saved. For documents Ronja authored, and for HTML pages you upload yourself, that control becomes a Download as menu that converts on the spot:

PDF — a print-ready file.
Word (.docx) — an editable Word document.
Original (HTML) — the document as stored.

Converted downloads always reflect the latest version of the document.

A document or PDF that Ronja rewrites in place — an edit, or a fresh export to the same file — keeps its earlier versions: the 25 most recent. You reach them in a conversation, from the History button (the clock icon) in the document’s side panel header: Current first, then each earlier version with when it was written and who wrote it. Opening one shows it in the panel with Back to current and Download; people who can edit the file also get Restore this version, which keeps the replaced content as a version so the restore can be undone, and Delete this version, which can’t. Anyone who can open the file can open its earlier versions too, so to remove something from a document’s history, delete the earlier versions that contain it (Delete this version). See Version history.

Search

The search box finds both files and folders by name across everything you can reach — and only what you can reach. Matching folders are listed first, each with the location it lives in; clicking one takes you straight into that folder. Matching files follow below, with the same Load more files button when there are more than a page of them. A file or folder shared narrowly to a place you’re not in, or sitting in someone else’s My Files, won’t appear. See also the resource types overview.

Folder matches are limited to the first 200, and there’s no Load more for them — so if you’re searching a term that many folders share, type more of the name to narrow it down rather than scrolling for one that isn’t there.