What a project gives you
When your work on a client is bigger than one conversation — a QBR cycle, a channel launch, an ongoing analysis — a project keeps it all in one place:
Standing instructions you write once apply to every chat in the project, so you stop re-explaining the brief at the top of each thread.
Pinned documents ride along too — Iris reads them as context on every turn.
Outputs are filed automatically — decks, docs, and other deliverables produced by the project's chats land in the project, not scattered across your history.
Everything lives together — the project page lists its chats, its pinned documents, and everything it has produced.
Most projects belong to one client. You can also create a project that spans a chosen set of clients for portfolio-style work.
Creating a project
In the Chat rail, find the Projects section and click the + button.
Give the project a name and click Create.
If you have a client pinned, the project belongs to that client. With no client pinned, you'll choose the set of clients it covers instead.
You land in the new project's workspace, ready to add instructions, pin documents, or start the first chat.
Instructions and pinned documents
From the project page, the owner can edit the standing instructions and pin documents from the client's document library. Keep instructions short and directive — the audience, the tone, what "good" looks like. Pin the documents you'd otherwise attach to every chat: the brief, the media plan, the style guide.
Chatting and scheduling inside a project
Start a chat from the project page and it automatically carries the project's instructions, pinned documents, and client scope. Scheduled agent work can belong to a project too, and its outputs file into the project just like chat outputs.
Tip: When a pinned client has exactly one project of yours, new chats for that client default into it — a chip on the composer says In [project name] before you send. Click the × on the chip to start that chat outside the project instead.
Sharing with teammates
Projects are built to be shared:
Open the project and find the Members section.
Add a teammate by email.
Members can chat inside the project with all its context applied, and they can see the instructions and pinned documents. Editing those stays with the owner. A member who's done with a project can leave it at any time from the project page.
Archiving, restoring, and deleting
Archive a project from its menu when the work wraps. Everything stays readable for everyone, but nothing new can be added — and the owner can restore it later if the work picks back up.
Delete is permanent. Omega asks you to confirm and spells out what will be removed before it goes.
Note: Projects belong to the Chat product — you'll always find yours (and the ones shared with you) in the Projects section of the Chat rail, one click from any conversation.