Groups, teams, and projects

Organisation records determine where work belongs and who can access it.

• A group is the broad organisational owner of runs. It can define a run-number prefix and group-specific roles.

• A team gathers users for day-to-day work. Team detail pages can show roles, users, quotas, projects, runs, and services.

• A project is the main work context selected on runs, templates, reservations, sensors, substrates, and chemical containers. Projects can define roles, users, tags, work-breakdown entries, quotas, and substrate requirements.

When creating a run, choose the group first, then a compatible team and project. Access checks and approval rules may use all three selections. Project settings can also determine whether substrates are required and how many substrates may be assigned to each experimental part.

See Groups, Teams, and Projects for record-specific fields.