> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/teams-roles-positions-and-groups/setting-up-your-teams-table.md).

# Setting up your teams table

The image below shows how to enter your participant details into the Teams table in your Editor. Navigate to `Configuration` > `Teams`.

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** (change the player profile picture if you wish)
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. [Add a password to streamline the player login process](#user-content-fn-1)[^1]
8. You can **add rows** for as many team members as your license allows you to upload
9. [You can **add your personas as team members** for role-playing](#user-content-fn-2)[^2]
10. Remember to **upload all your teams** to your space to run your exercise
11. Wipe entire teams list by selecting `Delete teams`

You must upload the team table separately from uploading the scenario.

<figure><img src="/files/FRkxYr9UuZvUlBx3s585" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
You must upload the teams table separately from uploading the scenario i.e. uploading via `Teams` or selecting *Upload exercise teams* when publishing the scenario.
{% endhint %}

[^1]: Remember to toggle Password on!

[^2]: Players can use Match personas so personas can be added to the table if they wish


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://helpdocs.conducttr.com/feature-documentation/designing-and-running/teams-roles-positions-and-groups/setting-up-your-teams-table.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.