# Teams

A Team groups coordinated research roles around a stage. Inspect its members, instructions and review criteria before assigning a study. You need workspace access, permission to use the Team and a usable execution machine.

## Inspect a Team

1. Open Teams and choose a Team relevant to your question.
2. Read its stage and description.
3. Inspect the leader and member roles to understand the work each is expected to contribute.
4. Read the available details, instructions, skills and review criteria.
5. Check access before asking colleagues to use it.

Built-in Teams are already available in a workspace and cannot be edited directly. Other Teams may need Add Team before use. If you need a variation, use the supported duplication flow and inspect the resulting configuration.

## Assign stage work

Choose the Team in a new study's assignee picker. Confirm the stage selection: a single-stage Team supplies its own stage, while a broader assignment can require you to choose stages explicitly. Do not leave an unstaged Team's destination ambiguous. See [studies](/docs/studies/).

After submission, inspect Activity to see the actual members' contributions and hand-ins. A Team name alone does not establish that all its work has completed or passed review. The study's configured scope and required review still govern completion.

## Check capability availability

Team skills provide reusable instructions; they do not supply credentials or create a connected runtime. If a needed capability is unavailable, inspect [skills](/docs/skills/), [connectors](/docs/connectors/) and the selected machine before retrying.

You have a suitable assignment when the Team's stage and roles match the study and its first run produces an inspectable hand-in or a clear blocker. For a task designed around a packaged Experimentation workflow, follow [workflows](/docs/workflows/) and its individual-agent assignment requirements.
