Collaboration
Collaborate in a project
Share a project so collaborators can inspect the same project or help implement and test it. The owner controls membership for each project.
Requirements and seats
Section titled “Requirements and seats”| Owner’s plan | Non-owner teammates per project |
|---|---|
| Free plan | 0 |
| Basic | 1 |
| Pro | 2 |
The owner does not consume a teammate seat. A Basic or Pro owner can invite anyone with a Buildryn account, including Free users. When an invitee accepts, Buildryn checks the project’s current capacity under the owner’s plan.
A shared project does not count toward an invitee’s owned-project limit. An independent duplicate does.
Choose a role
Section titled “Choose a role”| Capability | Owner | Editor | Viewer |
|---|---|---|---|
| Inspect accessible source/history and download artifacts | Yes | Yes | Yes |
| Edit source and plugin dependencies | Yes | Yes | No |
| Send chat requests and build | Yes | Yes | No |
| Keep/undo generated changes and use permitted recovery actions | Yes | Yes | No |
| Manage deployments | Yes | Yes | No |
| Change owner-controlled project details or delete the project | Yes | No | No |
| Invite/remove members or change their roles | Yes | No | No |
| Transfer ownership | Yes | No | No |
| View/export project activity | Yes | No | No |
Choose Viewer for someone reviewing files or artifacts. Choose Editor for someone who needs to implement, prompt, build, or manage testing.
Invite a member
Section titled “Invite a member”- Open the project as owner.
- Choose Share, or open Project settings → Users and choose Invite members.
- Enter the email of the collaborator’s existing Buildryn account.
- Select Viewer or Editor.
- Choose Invite.
- Check that the member is listed as Invite pending.
If sharing is unavailable, review the owner’s plan. If you can’t find the invitee, ask them to finish account setup and confirm their account email. If the project is full, remove an unneeded member or use a suitable plan.
Accept or decline an invitation
Section titled “Accept or decline an invitation”- Sign in with the account whose email was invited.
- Open application notifications.
- Open the project invitation.
- Choose the accept or decline action.
- If accepted, open the shared project and check your role.
The inviter receives the response. An invitation is not active membership until accepted. Capacity or plan changes between invitation and acceptance can prevent acceptance; the owner can review and resend as appropriate.
Change roles, cancel invitations, or remove access
Section titled “Change roles, cancel invitations, or remove access”- Open Share or Project settings → Users as owner.
- Find the member, using search when needed.
- Use Make Viewer or Make Editor to change the role.
- Use Cancel invite for a pending invitation.
- Use Remove to revoke a member’s access.
Role changes affect the permitted actions, including live access. A member should save work before a planned role reduction. Removing access does not transfer ownership or make a private copy for the removed person.
Who pays for shared work?
Section titled “Who pays for shared work?”- Chat requests use the credits of the workspace that owns the project, whoever sends them.
- Each deployment launch counts toward the applicable plan’s deployment allowance.
- Owned-project capacity and artifact/dependency limits use the project owner’s plan where applicable.
- Projects do not have their own credit balance; all projects in a workspace share its credits.
Before a testing session, agree who will launch it and check the remaining deployment allowance.
Coordinate implementation
Section titled “Coordinate implementation”- Agree on the next task and the files involved.
- Check collaborator presence/activity.
- Let one person submit the implementation request; only one run can be active in a project.
- Review the result together and let an authorized member resolve the review.
- Build and test the agreed state.
- Share a message link and build/deployment number for review notes.
Use realtime updates and presence to coordinate work. Members edit their own file views, and concurrent saves can conflict. Compare your edit with the latest saved content before saving again.
For handing over ownership and inspecting activity, see project activity and ownership.