Skip to content
BUILD.
← All guides

Team workflow · 6 min read

Share a project with your team

Share within your Agency workspace, hand editing control to a teammate, and make a project private again.

Applies to Build 1.1.0 · Updated September 15, 2026

Download this guide (.md)

1. Check your version and workspace

Use Build 1.1.0 or newer with the matching server and frontend and migration 0012_build_shared_projects.sql applied. The original 1.0.0 ZIP does not include project sharing.

Sharing applies to hosted full-stack Agency projects. Teammates need separate logins and Builder, Admin, or Owner membership in the same workspace. Personal/local projects and Viewer roles do not get shared editing.

You’re ready to continue when: Both people can sign in and use the intended Agency workspace.

2. Share as the project creator

  1. Open a disposable project as its creator and finish any running build or file operation.
  2. Choose Share project in the project header.
  3. Read the confirmation: builders and admins in this workspace will be able to access source, conversation, history, preview and exported code.
  4. Confirm. The page reloads and you keep editing control.
Personal Environment secrets are disconnected from the shared preview. Your vault stays private. Review the source and history for sensitive information before sharing. Copies already exported cannot be recalled.

3. Hand editing control to your teammate

  1. Save your editor drafts and finish the current operation.
  2. Choose Finish editing.
  3. Have your teammate open the shared project from the workspace and choose Take editing control.
  4. They receive the latest files and conversation, make their edits, then choose Finish editing.

You’re ready to continue when: The teammate can edit and export the project while the previous editor cannot make changes. Builds use agency API keys and record the acting teammate.

If someone still has editing control

Closing a browser does not release editing control. Ask the current editor to choose Finish editing. The creator can choose Release idle editor once operations have finished.

A running build, file edit or restore blocks handoff. Close duplicate editor tabs; only one editor socket can join. There is no simultaneous editing, automatic merging, or forced takeover of a running operation.

If a server restart leaves an interrupted-operation message, the installation owner must verify that the old operation can no longer write before recovering the project. Do not edit the sharing table or clear a marker blindly.

4. Make the project private again

Editing sockets close and previous preview capabilities are invalidated. Personal runtime bindings are resolved again only on a subsequent private preview deploy. Sharing does not grant project deletion, production deployment, database reset, or access to another person’s vault.

  1. Finish the current operation.
  2. As the creator, choose Make private and confirm.
  3. Verify that the teammate loses access, including through an old editor tab.

A prompt for your coding assistant

Copy and adapt this prompt
Help me verify shared projects in Build 1.1.0. Read docs/SHARED-PROJECTS.md and docs/UPGRADE-1.1.md. Preserve existing data and credentials. Verify matching frontend/server and migration 0012, then use two test accounts in the same Agency workspace. Test creator share, finish editing, teammate claim, a real edit, preview, export, and creator revocation. Check an unrelated workspace cannot access the project. Use only a harmless dummy Environment binding to test removal on share; never put keys into source or chat. Report actual results and remaining failures.

Keep going