Setup Stash is your personal workspace. Team Setups is the shared team library.
The two are connected so you can refine setups privately, then share them with your team when ready.
Common flows
Promote to Team Setups
Use this when a personal stash setup is ready to become a team setup.
Typical flow:
- Open a setup in Stash
- Choose Send to Team Setups
- Pick the destination team
- Confirm the version to share
This creates the first shared team-side setup, or links into an existing one depending on the situation.
Push a new version to Team Setups
After a Stash ↔ Team Setups link exists, later sends usually push a new version into that linked team setup instead of creating a separate unrelated entry.
This keeps collaboration history together.
Pull or send from Team Setups into Stash
From Team Setups, you can bring a setup back into your personal library when you want to:
- test it privately
- make personal changes
- compare it against your own baseline
Durable links
MyLMU can keep a durable relationship between:
- one personal stash setup
- one team setup
That relationship helps later pushes and pulls land in the expected paired records.
Conflict behavior
When the same name + track + car already exists in Team Setups, MyLMU may ask you to choose between:
- Link & add version
- Create new
Use Link & add version when the existing team setup is clearly the same baseline you want to extend.
Use Create new when the setup should stay separate for strategic or organizational reasons.
Permissions and plan rules
Keep in mind:
| Rule | Detail |
|---|---|
| Setup Stash | Requires your account to have Pro |
| Team Setups | Requires the team owner to have Pro |
| Sharing | You still need the correct team membership and permissions |
If a push or pull option is missing, check your team role and the owner’s plan state.
Best practice
- Use Stash for experimentation and personal references
- Push to Team Setups only when the setup is shareable and clearly labeled
- Add notes before pushing so teammates understand the change