Projects
A project is a container for chats. One piece of work, such as a month-end close, an onboarding or a migration, takes more than one conversation, and those otherwise scatter through your sidebar. A project gives them one name and one member list. Each project also has its own feature (see The project’s feature), and its chats’ files have a place of their own (see The project’s files).
Creating one
Section titled “Creating one”- In the sidebar’s Projects section, click + (New project).
- Give the project a name and an optional Description.
- Click Create.
The project page
Section titled “The project page”- A header line: how many chats the project holds, how many members it has, and who created it. Members are counted as people: an access group counts as everyone in it, and someone covered twice counts once.
- A composer reading Start a chat in the project’s name, which starts a chat already filed into the project. Its + button attaches a File or a Table, and you can drag files onto it.
- The project’s chats, newest activity first, in Today, Earlier this week and Older.
- The project’s files, with what has been saved there (see The project’s files).
Click the project’s name to rename it. The ··· menu holds Delete project.
Members see every chat
Section titled “Members see every chat”Invite opens Share project, which works like sharing a single chat: add people or access groups at View or Full access. A member can open every chat in the project, past and future.
- View: read the transcripts.
- Full access: prompt and work in the chats, start new chats in the project, move your own chats in, and invite further members. Whoever holds it can hand the whole project to anyone else in your organization, so choose View unless someone needs to work in the chats.
A chat can still have shares of its own; someone reaches it if either the chat or its project lets them, at whichever level is higher. Being an Admin doesn’t make you a member: a project’s chats stay out of an admin’s sidebar and project lists until they join, though the admin Activity page lists every chat in the organization. A project’s chats you can open appear in your search results, and you can ask Ronja to read one into the chat you’re in.
Moving a chat in or out
Section titled “Moving a chat in or out”Only the person who started a chat can move it, into a project, out of one or between them. No role changes that, not even Admin.
- Drag one of your chats from the sidebar onto a project, or open its ··· menu and click Move to project (or New project… to make one on the spot).
- Moving a chat in widens who can read it, so Ronja names who gains access: check it and click Move. With no other members, the move happens without asking.
The destination needs your Full access: a project you only have View on isn’t offered. Filing a chat brings its tangents too.
Files the chat already made stay where they are, in or out; new files follow the chat’s project from then on (see The project’s files).
Remove from project takes a chat back out. It never asks, and stays available to you even after you leave the project. A filed chat is listed under its project rather than in Chats; one you starred also stays in Favorites.
The project’s feature
Section titled “The project’s feature”Every project has its own feature, created with the project, named after it and renamed with it. Only the project’s members reach it, at their access to the project. You find it in your feature lists while you’re a member, and lose it when you leave. People who aren’t members, Admins aside, don’t see it.
- Full access members build there: they create and edit its tables, notes, codexes, modules, apps, workflows, Saved Agents, automations, credentials and MCP servers, a colleague’s too, and trash them. That trusts them with the project’s credentials: someone who can edit a workflow, an MCP server or a credential can use it and change where it’s sent, as a maintainer can in a shared feature. Store only what every Full access member may use, and keep a personal login out of the project.
- View members open what’s in it and can use it from their own chat, such as a credential or an MCP server’s tools, but can’t change it.
- Admins see it and can edit what’s in it, but create there only as a member with Full access.
- User Read-Only members open it at most, whatever their access to the project.
Access follows the project, not who made something. When you leave a project you lose everything in its feature, what you made included, straight away. Moved down to View, you can open what you made but no longer change it or run a draft of it, an app’s draft included. A table draft you already hold you can go on editing, but it never lands: committing it needs Full access. Ronja never shows a credential’s stored values, whatever your access.
A workflow writes the tables bound to its outputs by a member with Full access, whoever runs it, an automation included. Saved Agents and automations can’t write rows into a table in a project’s feature themselves; a member with Full access can. Connectors stay with Admins.
It can’t be shared. Making it organization-wide, naming maintainers and adding it to an access group are each refused: move what you want to share into a shared feature first. An app in it can’t be opened to guests. It can’t be moved, renamed or deleted on its own; it follows its project.
Moving things in. A member with Full access moves an item from their own private feature in at once, and requests a move in from a shared feature, which an Admin approves. Everyone else is refused, Admins who aren’t Full access members included. Only a Full access member can add to a request to move something in. What it depends on in a private feature must move with it: a table’s inputs, a workflow’s or app’s credentials, the Saved Agents, codexes and workflows they run, an app’s metrics, an MCP server’s credential, in the same move, or Ronja refuses it and says what is missing. What’s in a shared feature or already in the project can stay. What depends on it stays where it is, unless it’s in a shared feature, which refuses the move. Moved apart, a workflow and the table it writes are refused; moved together they land, and the workflow goes on writing the table. A move takes open drafts with it, so someone who isn’t a member loses a draft they had open. A Ronja API credential or a managed database’s credential can’t move in at all. Check what you move first: nothing moves from a project’s feature straight back to a private one, so taking something out goes through a shared feature, with an Admin’s approval.
A Full access member can use what’s in it from any feature, the way you can use what’s in your own private features: an app, workflow, Saved Agent or Derived table in another feature can read a table in it, and an app’s guests can be given one of its folders. Everyone who can use that app, workflow or Saved Agent then reaches it through them. View members, and Admins who aren’t members with Full access, can’t. A session table can’t be built from a table in it, because a chat can be shared with people outside the project: create the new table in the project’s feature instead.
The project’s files
Section titled “The project’s files”Once your organization keeps its files in features, a project’s files live in its feature, and the project page shows them. Only the project’s members open, list or find them, Admins aside: Full access members save, edit and move files in, and View members open them but can’t move files in.
A file from a project chat, such as an attachment, a Python output or something Ronja saves without being told where, lands in the first of these that fits:
- the folder you name, My Files included;
- when the chat is in a shared feature, that feature for an attachment or a Python output, and your My Files for what Ronja saves without being told where;
- the project’s feature, when you have Full access on the project;
- your My Files. A View member’s files go there, and so do a User Read-Only member’s.
Until then, a project that already has a folder keeps it, and the project page shows it. When your organization’s files move into features, that folder becomes the project feature’s top folder, named after the project (with a number added if another top-level folder already has that name). Its chats save their outputs into it, and files you attach to them land there too; a folder you name, My Files included, still wins. Members get the folder matched to their access to the project: Full access members read and save, View members read. Adding someone to the project hands them the folder, its subfolders and their files, and removing them takes that away; someone who isn’t a member gets nothing from it, even if one of their chats is filed there.
Anyone who can’t write the folder, a View member included, keeps saving to their own My Files; see Folders and who can reach them. A User Read-Only member’s own saves always stay in their My Files; see Files a read-only member makes. A project without a folder has no shared place for files: what its chats save goes to each person’s My Files.
A folder can’t be attached to a project. Over the API, sending a folder when creating or changing a project is refused with “a project’s files live in its feature, so a folder can’t be attached to it”.
Deleting a project
Section titled “Deleting a project”Its chats survive, un-filed and back to their own sharing, for most the owner only. Members lose the access the project gave them. A folder the project had, and its files, are untouched.
While the project’s feature holds anything, deleting the project is refused, and the message names what is in it: move it into another feature or delete it, then delete the project. Items of the feature in the trash count too, so empty them from the trash first. An empty feature is deleted with its project.