Skip to main content
A project has one owner and any number of invited collaborators, each holding a role that decides what they can do.

​
The Three Roles

Owner is not granted, it is earned by creating the project. The two roles you can hand out are Editor and Viewer.

​
Inviting Someone

The Manage Collaboration drawer showing an Invite Collaborators card with an email field and Viewer and Editor permission options, a Shareable Link Access toggle, and a members list below.

Manage Collaboration. Invitations take a role; the members list shows who already has one.

Open Manage Collaborators from the panel rail inside a project, or Manage Collaborations from a project card on the dashboard. Both open the same drawer. Enter one or more email addresses, choose Viewer or Editor, and invite. The invitation arrives by email and appears in the recipient’s Invitations tab.
The members list showing Active Members and Pending Invites tabs, a search field, and rows with each member's name, email, date added, and role.

Members are separated into those who have accepted and invitations still outstanding.

An invitation can be accepted or rejected by the recipient, or withdrawn by you before they respond. Someone who has accepted can later leave, or be removed.

​
Who Pays for a Collaborator’s Work

Each collaborator carries a billing preference, set when you invite them. It decides whose credit balance an agent run draws from: the project owner’s, or the collaborator’s own. This matters on a project where several people are prompting the agents. A collaborator set to pay for themselves draws on their own balance; one set to be paid for by the owner draws on the owner’s.

​
What a Role Changes

Roles are checked wherever an action would alter the project. A Viewer can open the workspace, read the CAB, and look at Tickets; the controls that change things are unavailable to them. Read-only questions are treated separately from changes, so a collaborator may be able to ask the agent about a codebase on a project where they cannot build.

​
Two Ways to Share

These are different mechanisms for different audiences, and confusing them is the easiest mistake to make here. Shareable Link Access is a toggle in the drawer. Any signed-in user holding the link can ask to join the project. Nobody gets in without approval. Read-only share links are per item and need no account. This is how a blueprint reaches a client or a business stakeholder who never uses the platform. See Editing your CAB.
A read-only share link needs no account and no approval. Anyone holding the URL can read that item. Enable one only where you are content for the content to travel.

​
Your Next Step

Copy a project for another client

What a clone brings with it, and what it leaves behind.

Share a blueprint for review

How a specification reaches people who are not platform users.

Related topics

Troubleshooting & FAQCommon Workflows by RoleEditing your CABWeekly release notesBlueGenAI Documentation