Files
Files is where the documents and data files you and Ronja produce are kept. Open it from Files in the sidebar. It’s a folder browser: folders on top, files inside them, with a search box across the top. If your organization has more than one Space, it shows the folders and files of the Space you’re in.
What lands in Files
Section titled “What lands in Files”| How it arrives | Where it lands, and who sees it |
|---|---|
| You save something in chat, such as “save this as a CSV” or “bundle those exports into a zip”. Any file type works; the name decides the type. | Your My Files, unless you name a folder |
| A workflow produces output, such as a report or an export | The folder the workflow is set up to write to, or else a subfolder named after it under the shared Workflow outputs folder, readable by the people who can see the workflow; see Where a workflow’s report files land |
| Ronja writes a document, such as “draft a monthly report” (see Documents you can download) | Saved as a file you can reopen |
Ronja opens an image or a CAD drawing in a conversation, and saves the picture she rendered so the conversation still shows it later (a drawing’s ends in -preview.png) |
The top level of Files, visible to the whole organization, even when the original is in your My Files (a User Read-Only member’s follows the chat; see Files a read-only member makes) |
| Ronja opens an attachment that arrived in a connected mailbox, for an automation or because you asked | Visible only to whoever or whatever pulled it in, and your admins |
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 says where each file came from: You, a colleague’s email address, or the automation or Agent that wrote it, tagged AUTOMATION or AGENT. A file a guest uploaded through an app shows the app’s name, marked Guest.
Files you upload in a conversation are different: CSV and Excel become tables, and images and text ride along as context; see Upload files. A small zip you attach, or one that arrives as an emailed attachment, is unpacked and its files land in Files; a large one is listed, and Ronja unpacks it on request. See Zip archives.
My Files is private
Section titled “My Files is private”Everything you save without naming a shared destination goes into My Files, your personal folder. Other members can’t see or open what’s there. The one exception is the picture Ronja renders when she opens an image or a drawing you keep there, which lands at the top level of Files (a User Read-Only member’s follows the chat; see Files a read-only member makes).
To share something, ask Ronja to save it into a shared folder, or move it there.
A chat filed into a project saves into the project’s files instead, so the project’s members can find them: its feature once your organization keeps its files in features, or else the folder the project already has; see The project’s files. Once your organization keeps its files in features, a project chat that is also in a shared feature puts an attachment or a Python output in that feature first. If you’re on the project with View only, your saves fall back to My Files. A folder you name, including My Files, wins (a User Read-Only member’s saves stay in My Files).
Files a read-only member makes
Section titled “Files a read-only member makes”Unless their organization turned chat off for read-only members, a User Read-Only member can ask Ronja for documents and files, such as a PDF of a table or an Excel export. What they ask for always goes to their My Files, where only they and admins can open it, even in a project chat; saving anywhere else is refused. Ronja can revise a document in their My Files, but no other file, and they can’t move, rename or share a file. What else a read-only member can do is on Roles.
The files the conversation produces along the way, such as Python outputs, generated images, the picture Ronja renders of an image or a drawing, and files unpacked from a zip, follow the conversation instead:
- In a chat in a shared feature, that feature’s members can open them.
- In a project chat, they go to the folder the project already has, when the member can save there. Once your organization keeps its files in features, they stay in the member’s My Files.
- Anywhere else, including Slack and Teams and a chat someone shared with them directly, they stay in the member’s My Files, and colleagues in the conversation see a link they can’t open.
Nothing a read-only member makes is visible more widely than the conversation’s feature or project.
Folders and who can reach them
Section titled “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, and a Written by list of the workflows that produce files there. Granting access to a folder or file is done in the browser only, while removing a grant stays scriptable; see Actions the API can’t take.
A folder can also be reached in two ways that don’t show in its Access panel:
- Attached to a project, until your organization keeps its files in features. The project’s members reach the folder, its subfolders and its files: Full access members read and write, View members read. Adding someone to the project hands them the folder, and removing them takes it back; the folders listed in the browser don’t change. Members can save files and create subfolders there, but renaming, moving or deleting the folder needs write access of their own, or an Admin.
- Listed on an app opened to guests. The app’s guests and its App Users can open or upload files there, including anything added later. See the Guests section of the app’s Access tab. A folder in someone’s My Files can’t be listed.
Which folders a workflow may write to, and from when, is in Where a workflow’s report files land.
Opening a folder changes the page address, so Back and Forward step through the folders you’ve visited, and you can bookmark a folder or send its link to a colleague who has access.
A folder shows the first 500 subfolders and 500 files; click Load more below the list for the rest. Subfolders load first, then files.
Moving files
Section titled “Moving files”Ask Ronja to move a file, “move the July report into the Reports folder”, or use the move action in Files. Moving needs write access to the file and to the destination folder. Moving a file into My Files makes it private: any sharing it had is dropped, so only you and admins can reach it.
Downloading
Section titled “Downloading”Open in new tab, beside each file’s download control, opens a PDF, an image or an HTML page in your browser, and downloads anything the browser can’t show. A zip Ronja saved for you stays a zip.
Most files download exactly as they were saved. For documents Ronja wrote, and HTML pages you uploaded, the control is a Download as menu that converts the latest version:
- PDF: a print-ready file.
- Word (.docx): an editable Word document.
- Original (HTML): the document as stored.
A document or PDF that Ronja rewrites in place keeps its 25 most recent earlier versions, which you open from History in a conversation’s document panel; see Version history.
Search
Section titled “Search”The search box finds files and folders by name across everything you can reach, and only that. Matching folders come first, each with its location; matching files follow. Folder matches stop at the first 200, so type more of the name to narrow a search many folders match. See also the resource types overview.