Projects

A project is a container for chats. One piece of work — a month-end close, an onboarding, a migration — takes more than one conversation, and those otherwise scatter through your sidebar. A project gives them one name, one member list, and one folder in Files. It is chats + people + a folder — not tables, apps or workflows; that is a feature (Project vs Feature).

Creating one

Projects live in their own Projects section in the sidebar, between Favorites and Chats. Click the + (New project) beside the section header, then give the project a name and an optional Description, choose its Project folder, and click Create.

No folder is the default; attach one later from the project page.
Otherwise pick any shared folder you have your own write access to. A folder you can only reach because you’re in someone else’s project isn’t offered — attaching hands it on, and that isn’t yours to pass along. Your private My Files — and anything inside it — isn’t offered either: only you can reach it, so it would be no use to anyone else.
Create a new folder makes one for the project, named after it, and a second dropdown — Create it in — chooses where it goes. That list is every folder you can write to — including the folder of any project you have Full access on — and Admins also get Files (top level). If you can’t write to a shared folder yet, the option isn’t offered at all and the line under the dropdown tells you to ask an Admin for access to one.

The project page

A header line under the project’s name: how many chats it holds, how many members it has, and who created it. The member count is people, not entries on the share list — an access group counts as everyone inside it, and a small group icon beside the avatars shows that some of the access arrives that way. Somebody covered by both a group and their own share is counted once.
A composer at the top, its placeholder reading Start a chat in the project’s name, opening a conversation already filed into the project. The + button attaches a File or a Table to that first message, and you can drag files straight onto the composer — an overlay reads “Drop files to attach”. Attachments upload as you add them; the send button waits until they finish.
The project’s chats, newest activity first, in Today, Earlier this week and Older. Each row shows the avatar of whoever started it; your own say You.
The attached folder on the right, with what has been saved there and an Open link into Files.

Click the project’s name to rename it. The ··· menu holds Attach folder… (or Change folder…) and Delete project. The folder overlay offers the same choice as the create modal — No folder, any shared folder you have your own write access to, or Create a new folder with the same parent dropdown plus a New folder name field. It shows the folder that’s attached now even if it isn’t one you could have picked yourself.

Members see every chat

Invite opens Share project — the same shape as sharing a single chat: add people or access groups at View or Full access. The difference is what it covers: a member can open every chat in the project, past and future, so nobody has to remember to share the next conversation.

View — read the transcripts.
Full access — prompt and work in them, start new chats in the project, move your own chats in, and invite further members. Full access is a transitive grant: whoever holds it can hand the whole project — every chat in it, past and future — to anyone else in your organization. Choose View unless someone needs to work in the chats.

Being able to work in a project’s chats does not let you rearrange them: a member can prompt in a colleague’s chat, but cannot move it out of the project or into another one. Only the person who started a chat decides where it is filed.

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 does not make you a member: a project’s chats stay out of an admin’s lists until they join (see the roles capability matrix). Whatever you can open you can also find: a project’s chats appear in your own search results, and you can ask Ronja to read one of them into the chat you’re in — as you can with any conversation you can open, in a project or not.

Moving a chat in or out

Only the person who started a chat can move it. Where a conversation is filed — and so who can read it — stays with whoever began it. On chats other people started, the ··· menu has no Move to project and the row cannot be dragged; that is not a role limit, and an Admin cannot do it either.

Drag one of your chats from the sidebar onto a project row, or use its ··· menu → Move to project (or New project… to make one on the spot). Either way the destination needs Full access: filing a chat pushes it at every member, the same decision as starting one there. A project you only have View on is not offered — it is missing from the Move to project list and its sidebar row will not take a drop. If none of your other projects will accept the chat, the list says No project you can file this into, and New project… is still there.

Moving a chat in widens who can read it, so Ronja asks first and names who gains access; with no other members there is nothing to widen and the move just happens. Filing brings the chat’s tangents too — a tangent inherits access from the conversation it was forked off — and the dialog says so.

Remove from project takes a chat back out; that only narrows access, so it never asks — and it stays available to you even if you later leave the project, so filing a chat is always undoable. A filed chat is listed under its project rather than in the flat Chats list — unless you starred it, in which case it also stays in Favorites.

The project folder

Chats in a project save their outputs into its folder by default. Ask Ronja in a project chat to “save this as a CSV” and the file lands there instead of your private My Files, where the rest of the team can find it.

Files you attach land there too. A file you drag onto a project chat’s composer, pick with +, or paste in goes into the project folder, not your private My Files — so the document you asked a question about sits beside the answer Ronja saved, and the rest of the project can open both.
A named path still wins — the project folder is the default, not a redirect. Asking for a specific folder saves it there, and asking Ronja to keep the file in your private home leaves it in My Files.
Members get the folder, matched to their access. Adding someone to the project hands them its attached folder, its subfolders and the files in them; removing them takes that away again. Full access members can read and save into it; View members can read it. Somebody who isn’t a member gets nothing from it, even if one of their chats is filed here. The access follows the member list, so there is nothing to grant separately and nothing to tidy up afterwards.
View is not a write role. A View member can open what the project’s chats have saved — the same information they can already read in the chats themselves — but saving there needs Full access. Anyone who can’t write the folder keeps saving to their own My Files rather than failing — see Files.

Attaching a folder hands it out, so you have to be able to write it yourself: you created it, you were granted write on it directly, or you’re an Admin. Write you only hold through another project’s membership doesn’t count — you can pass on a folder you were given, not one you can only reach because you’re in someone else’s project.

On a project that already has members, saving the change shows a confirm step naming who gains access, exactly as filing a chat into a project does; its button reads Share folder. Detaching is never gated — it only takes access away — and detaching or changing the folder leaves every file already in it where it is.

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. The folder and its files are untouched.