Collaboration
Invite people to a project as editors or viewers, see what each role can do, and discuss with labeled comments and mentions.
Work on a project with other people. You invite them, choose what they can do, and talk in comments.
Roles
| Capability | Owner | Editor | Viewer |
|---|---|---|---|
| See the chat, code and last preview | Yes | Yes | Yes |
| Use the simulator | Yes | Yes | Yes |
| Write to the agent, edit files, restore versions | Yes | Yes | No |
| Builds and Asset Studio | Yes | Yes | No |
| Read the V2 Cloud console | Yes | Yes | No |
| V2 Cloud changes, Secrets | Yes | No | No |
| Publish, App Store, Google Play, RevenueCat | Yes | No | No |
| Invite people, change roles, rename, visibility, delete | Yes | No | No |
| Leave the project | n/a | Yes | Yes |
Everything the agent does for a collaborator uses the owner's usage, including the simulator. See Plans and usage. Viewers see a read-only chat: the agent and editing are disabled for them.
Invite people
Use Invite collaborators in the project header.
- Enter an email address, or copy an invite link.
- Choose Editor or Viewer.
- Send it. An email invite is sent to the address; the person gets access when they sign in with that email.
Shared projects appear in the dashboard of everyone who has access. The owner can change roles, remove people and revoke invites. A member can leave.
Comments
Open Comments in the header to discuss the project without editing it.
- Labels: mark a comment as Idea, Bug, To do, Question or Done.
- Mentions: write
@and a name to mention a collaborator. They get notified, by email too. - Unread badge: the Comments button shows how many comments are new, and the list updates live.
- On an element: in the simulator, select an element to comment on exactly that part of the screen.
Common uses
- Founder and developer: the founder as viewer, the developer as editor.
- Client review: viewer access to follow progress.
- Pair building: two editors; agree on who asks for changes to avoid conflicts.