Projects, revisions and collaboration¶
A project groups a design question, sources, requirements, revisions and engineering results. Use stable names and keep the baseline operating conditions with the design family.
Review proposed geometry changes before accepting them as a saved revision. Preserve the parent revision and the reason for the change. A geometry job or stateless design-operation response does not itself approve a Studio revision.
Independent API/MCP work can use a private workflow without an existing project. Jobs and artifacts retain ownership and lineage. Creating a Design project from that workflow can share it with the organization and requires the corresponding explicit sharing decision. Inspecting the workflow does not perform that conversion.
Select existing owned input artifacts rather than uploading duplicate copies. For collaborative edits, re-read after a revision or sequence conflict and reconcile the current state; do not overwrite another person’s newer work.
Permissions and organization roles are enforced by the central service. See resource ownership and authoring drafts.