Sharing a project
Inviting people to a model, what each role can do, and how to coordinate two engineers in the same structure.
Collaboration & sync 2 min read
A project is shared by inviting people to it, not by sending a file. Everyone invited opens the same model, sees the same state, and sees each other's changes as they happen.
Roles
| Role | Can do | Cannot do |
|---|---|---|
| Owner | Everything, including deleting the project, managing access, and switching sharing off entirely | — |
| Read & write | Model, load, solve, check, export | Manage access or delete the project |
| Read | Open, inspect results, export reports | Change anything |
Give reviewers read access. They can interrogate the model completely — every result, every check, every input — with no possibility of changing it.
Sharing has its own master switch. Turning it off suspends every collaborator's access at once without removing anyone; turning it back on restores the same list.
Real-time editing
Two people in the same model see each other's changes as they are made, with no check-out and no master file. Edits are recorded as operations and merged deterministically:
| Edits touch | Result |
|---|---|
| Different parts of the model | Both edits apply |
| The same property of the same object | Last write wins; every device resolves it the same way, whatever order the updates arrived in |
Solving is per-person and local. Two engineers can solve the same model simultaneously without interfering, because each solve runs on its own machine.
What sharing does not solve
Working with a reviewer
- Give the reviewer read access to the live model.
- Send the exported report as the formal record.
- Let the reviewer interrogate the model directly for anything the report does not answer.
This removes the usual cycle of "can you send me the model", version confusion, and a reviewer looking at something two revisions old.
Access and confidentiality
Only people you invite can open a project. Your models are not visible to us in normal operation and are never used for anything but running the service — the commitments are in the privacy policy. Removing someone's access takes effect immediately.
For work under an NDA, note that inviting someone gives them the whole project. Where only part of a structure should be shared, share an exported report or a separate project, not access to the model.
Ending a share
Remove access from the project's people list. Anything they exported while they had access is already exported, like any other document.
Something wrong or unclear on this page? Tell us, and it gets corrected.