Sharing builds with your team
Every build in your library has a sharing scope that controls who, beyond you, can find and load it. The default is private. Share a build with your group or your whole organization and it appears on your teammates' Team builds tab; publish it and it goes to the community for any pilot to browse and fork.
Sharing never hands out edit rights. Only the owner can change the original: teammates load a shared build read-only or copy it into their own library and change the copy.
The four scopes#
| Scope | Who can find and load it |
|---|---|
| Private | Only you. The default for every build. |
| Your group | Everyone in your group inside your organization. |
| Organization | Everyone at your organization. |
| Public | Published to the community for any pilot to browse and fork, and still visible to your organization. |
A group is a smaller team inside your organization. The scope always refers to your own group and your own organization: you cannot share into a team you do not belong to. If you are not in a group yet, the group option is disabled ("You are not in a group yet"); if you are not in an organization, group and organization sharing are unavailable. Group membership is managed by your organization admin; see Managing users.
Public sharing is gated separately: it requires that community publishing is available on your account. When it is not, the option is disabled with "Community sharing isn't available on your account right now." Publishing a build also snapshots it into the community, and the dialog then offers a View it in the community link.
Changing a build's scope#
- Open the Build menu on the Builder page, then Build library.
- On the My builds tab, every row carries a scope pill (a lock for Private, or the group, Organization, or Public label). Click it.
- The Share build dialog opens, listing the four scopes with a description of exactly who would see the build. Click a scope to apply it immediately.
- The line at the bottom confirms the result: "Right now this build is visible to only you", "everyone at your organization", and so on. Press Done to close.
Setting a build back to Private withdraws it from the Team builds tab.
The Team builds tab#
The Build library panel has a second tab, Team builds, showing builds your teammates have shared: organization-wide builds and public builds from your organization, plus group builds from your group. Your own builds never appear here; they are on My builds. Each row names the build, shows its scope tag, and says who shared it ("shared by ...").
Two actions are available on a shared build:
- Load puts the shared build onto your bench so you can inspect and analyze it. You cannot save over the original: saving from the bench writes into your own library under whatever name you give it.
- Copy to my library forks the build into your own library as a private copy that you own outright. If you already have a build with that name, the copy is named with a "(copy)" suffix. The panel switches to My builds so you can see it land.
If you are not part of an organization, the tab explains there is no team workspace; if nobody has shared anything yet, it says so.
Access rules, precisely#
- The owner always sees and edits their own build, whatever its scope.
- Group builds are visible only to members of that same group; organization and public builds are visible to members of that same organization.
- A build id from outside your organization resolves to nothing: shared builds cannot be reached by guessing links.
- The scope you set is recorded server-side against your own organization and group, never a value chosen by the browser.