Projects and collaboration

Studio is designed for engineering work that crosses people and design iterations. An organisation owns the shared workspace; projects hold the technical work.

Choose a project boundary

Create one project per product, component, benchmark or design question. Keep geometry revisions and comparable cases together when they share output definitions and acceptance criteria. Separate projects when access, physics or data retention requirements differ.

Invite colleagues

Organisation owners and permitted administrators can invite members by email. Roles distinguish organisation management from engineering participation. Invited members work in the same project record instead of exchanging mesh and result files out of band.

Typical team patterns include:

• a CAD engineer prepares and names geometry,

• a simulation engineer owns meshing and physics,

• a technical lead reviews convergence and validation,

• a project manager follows run status and usage.

Maintain traceability

Use clear names for geometry, meshes, simulations and outputs. Include the operating condition or design revision rather than relying on dates alone. Before changing a validated setup, create a new revision so the accepted result remains reproducible.

Ownership and access

The organisation owner controls subscription and ownership transfer. Member removal affects access to the organisation but does not rewrite the project history. Transfer ownership deliberately and confirm the receiving user is an active organisation member.