# Teams
### Teams are for humans
All your exercise participants will be in a team.
Using more than one team can:
* Help organise participants better so that you can find them more easily during an exercise should you wish to modify their permissions
* Allow content to be published to specific players
* Allow teams to exercise in parallel with some channels that restrict player activities to their specific team without impacting other teams
### 🔀Publishing options
**Teams** allow you to publish to everyone in a specific team but typically Teams are used to better organise your participants or for reporting purposes.
**Roles** allows publishing to all participants in the same Role
**Positions** allows publishing to a specific person (because a position is unique)
**Groups** are used for dynamic publishing because players can be moved to a Group dynamically based on a button press in a message. See below.
#### ⚡Limitations
**Teams** are unlimited
**Roles** are limited to 5 roles (Role 1 is the default)
**Positions** the same player can have multiple Positions but a Position can only be assigned to one player.
**Groups** are limited to 3 groups (Group 1 is the default)
The image below shows how these options relate to each other.
There is no requirement to use Roles, Positions or Groups unless your training objectives demand it. Only use them if it's necessary to send specific content to specific players.
### Teams table in the Editor
The image below shows how to enter your participant details into the Teams table. The numbers in the following list refer to the pointers in the image:
1. Add the name and email address of your exercise **facilitator**.
2. Add the name and email address of your **observers**
3. Add **teams** - they appear as tabs in the table. Double-click the tab to rename or delete a team
4. In each team's table, there is **a row per team member**
5. After adding their names and email addresses, you can assign **positions** per player
6. You can also select a **role** per each team member (optional)
7. You can **add rows** for as many team members as your license allows you to upload
8. You can **add your personas as team members**, this will be useful for role-playing
9. Remember to **upload all your teams** to your space to run your exercise
You must upload the team table separately from uploading the scenario.
### Dynamic Team Actions
Players can be moved to Role or Group depending on their actions.
| Benefit | Feature |
| ------------------------------------------------------------------------------------------------------------------------ | ------------- |
| Players enjoy a personalised experience based on their decision | Move to Role |
| Anticipates uncertainty around exercise attendence such that whoever attends can select a role without EXCON involvement | Move to Group |
#### Move to Role
Players can be moved into a *Role* based on clicking a *Question* button.
1. Click the question button
2. Select Move to Role Action
This feature can be useful when used with a *Click to Play* registration type and you'd like players to select their own Roles.
#### Move to Group
Players can be moved into a *Group* as the consequence of clicking a *Question* button.
1. Click the question button and select Move to Group Action
2. Select the group
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://helpdocs.conducttr.com/feature-documentation/designing-and-running/registration/teams.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
