Team
Shared chains
A chain travels on the board it sits on. There is no team chain library, and the workaround is better than it sounds.
Chains travel on boards. A chain library is personal to the person who saved it, so there is no team list you can publish a chain into and no way to push one into a colleague's library. Saying that plainly up front, because the workaround is genuinely good and hunting for a sharing button that does not exist is a bad way to start. ## What does work **A chain on a shared board is shared.** Everyone who can open the board sees it, and anyone who can edit the board can press Run on it. That covers most of what a team actually needs. The finishing pass, the mesh preparation sequence, the restyle-and-grade combination: put the chain on the board where the work happens and the team uses it there. :::tip[Make a chains board] One board per workspace holding the sequences the team relies on, named after outcomes rather than tool lists. Anybody can open it, run a chain on the spot, or copy the arrangement onto their own board. It is a shared library made out of a board. ::: ## What does not work - **Publishing a chain to the team.** Your saved chains are yours - **Pushing an update.** Even in your own library, a saved chain and a chain on a board are independent copies, so improving one never reaches the other - **A teammate spawning your chain from their own library.** They would have to build it once themselves ## Giving somebody a chain to keep If a colleague wants a chain in their own library rather than on a board: 1. Put your chain on a board they can open 2. They read the steps, which each show the tool, the model pill and any tuned settings 3. They build it once on their board and save it Tedious for one person, and it is done once. A chain is a handful of steps rather than a document. :::caution[Running a chain spends the board's credits] A chain is a generation like any other, charged to the workspace that owns the board. On a shared board, a teammate pressing Run on your four-step chain spends four steps' worth from the team pool. ::: ## A read-only viewer sees it and cannot run it Someone on a public link sees the chain sitting there and every edit affordance is inert for them: no drag, no Run, no removing steps. That is the same rule the rest of the read-only viewer follows, and it means a chains board is safe to share outward as a demonstration of process. ## Where this may go Nothing about the current shape prevents a shared chain library later; the record is just scoped to a person today. If your team is working around it in a way that hurts, that is worth telling us, because the workaround being liveable is the reason it has not moved.Chains travel on boards. A chain library is personal to the person who saved it, so there is no team list you can publish a chain into and no way to push one into a colleague’s library.
Saying that plainly up front, because the workaround is genuinely good and hunting for a sharing button that does not exist is a bad way to start.
What does work
Section titled “What does work”A chain on a shared board is shared. Everyone who can open the board sees it, and anyone who can edit the board can press Run on it.
That covers most of what a team actually needs. The finishing pass, the mesh preparation sequence, the restyle-and-grade combination: put the chain on the board where the work happens and the team uses it there.
What does not work
Section titled “What does not work”- Publishing a chain to the team. Your saved chains are yours
- Pushing an update. Even in your own library, a saved chain and a chain on a board are independent copies, so improving one never reaches the other
- A teammate spawning your chain from their own library. They would have to build it once themselves
Giving somebody a chain to keep
Section titled “Giving somebody a chain to keep”If a colleague wants a chain in their own library rather than on a board:
- Put your chain on a board they can open
- They read the steps, which each show the tool, the model pill and any tuned settings
- They build it once on their board and save it
Tedious for one person, and it is done once. A chain is a handful of steps rather than a document.
A read-only viewer sees it and cannot run it
Section titled “A read-only viewer sees it and cannot run it”Someone on a public link sees the chain sitting there and every edit affordance is inert for them: no drag, no Run, no removing steps. That is the same rule the rest of the read-only viewer follows, and it means a chains board is safe to share outward as a demonstration of process.
Where this may go
Section titled “Where this may go”Nothing about the current shape prevents a shared chain library later; the record is just scoped to a person today. If your team is working around it in a way that hurts, that is worth telling us, because the workaround being liveable is the reason it has not moved.