Team
Inviting collaborators and managing team member roles on a project.
Project sharing lets you invite other users to view or contribute to a project. Sharing is managed from the project's Team page, which sits behind the Settings row in the sidebar's Project group.
Roles
| Role | Permissions |
|---|---|
| Owner | Full access. Whoever created the project. Cannot be changed. |
| Contributor | Read and write access. Can edit project content, but not the project's own details (name and so on). |
| Reviewer | Read-only access. Can view all project data but cannot make changes. |
Inviting a collaborator
Only the owner can invite. Under Invite by email, enter the collaborator's email address, pick Reviewer or Contributor, and click Send invite.
The invitation is stored as a pending invite. The recipient sees it on their Projects page and can accept or decline.
Accepting an invitation
When you're invited to a project, an invite card appears above your project list, naming who invited you and the access offered. Click Accept to gain access or Decline to dismiss.
Managing members (owner only)
Below the invite form, one People and access table lists everyone -- members and outstanding invites together -- with four columns: Person (their email), State (pending, declined, or accepted), Time, and Access.
For the owner, the Access cell is a single dropdown, and it is the whole control:
- Pick Reviewer (read-only) or Contributor (can edit) to set or change what someone has.
- Pick Revoke to cancel a pending invite or remove an accepted member's access.
- On a declined invite the dropdown starts at None; picking a role invites that person again.
Anyone who is not the owner sees their own access as plain text instead.
How shared access works
Shared projects appear on the collaborator's Projects page alongside their own projects. The collaborator works directly on the owner's copy of the project, so all reads and writes happen against the owner's data.
Media files (images, video, audio) are served through a server that checks your access before returning each file -- the underlying storage locations are never exposed to collaborators.
Who pays for AI use inside a shared project follows one rule, and each cost has exactly one payer. A contributor's own AI use -- asking the assistant, rewriting a prompt, the screenplay and plan tools -- is their own cost: it counts in their usage and monthly cap, and shows on their Costs page with the project's name beside it. Voice generation is the project's cost: when a contributor makes speech in your project, it is a project cost you, the owner, see on your Costs page, with the contributor's email in the Who column. Members cannot see a project's costs, only the owner can.
As the owner you can take on a member's whole bill. On the project's Team page, each member has an Owner pays this member's costs switch (visible to you only). With it on, everything that member spends in this project, the Assistant included, is a project cost: you see it on your Costs page with their email in Who, and their own Costs page shows nothing for the project. The Team page also has a Project AI cap (shown once the project has a member) that stops the project's costs for everyone on it, you included; only you can raise it. See Costs.
Conversations and AI Assistant sessions are private per user -- they are not shared between collaborators.