> 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.md).

# Teams, roles, positions, and groups

Conducttr is designed with **flexibility** in mind, so the multiplicity of options you see in the *To* field for an inject is to ensure **you're able to send content in a way that suits your exercise and training audience**. 

You can set up teams, roles, positions, and groups under `Configuration` in your Editor. You can assign roles and positions live during the exercise from the `Teams` tab of your Facilitator Dashboard.

{% hint style="warning" %}
There's **no requirement to use all of these different options** unless your training objectives demand it. Only use when it's necessary to send specific content to specific players.
{% endhint %}

<table><thead><tr><th width="98.9554443359375">Option</th><th width="226.0001220703125">Description</th><th width="266.5556640625">Use</th><th>Any limitations?</th></tr></thead><tbody><tr><td><strong>Teams</strong></td><td><p></p><p>Teams are for humans. All of your exercise participants will be in a team. You can set up multiple teams.</p></td><td><p>Using more than 1 team can:<br></p><ul><li>Help organise participants better so that you can find them more easily during an exercise should you wish to modify their permissions</li><li>Allow content to be published to specific teams (e.g. "legal", "IT")</li><li>Allow teams to exercise in parallel  (e.g. "syndicate 1", "syndicate 2")</li></ul></td><td>Up to 64 teams are allowed.</td></tr><tr><td><strong>Roles</strong></td><td>Can be assigned to multiple players who perform the same functional role in the exercise</td><td>Best when you're running syndicates and you want to publish across all the teams to the same functional role</td><td>There are 5 role slots (Role 1 is the default)</td></tr><tr><td><strong>Positions</strong></td><td>Unique to one player - usually based on their job but is also used to define a player permissions </td><td>When you want to send content to a single unique player (because their job or exercise activity is unique). It also allows players to impersonate personas</td><td>Up to 1000 positions allowed. The same player can have multiple positions assigned but the position can only be assigned once.</td></tr><tr><td><strong>Groups</strong></td><td>A dynamic way of sending content to multiple players</td><td>Players arrive in one of three groups based on their response to click-button answers </td><td>There are 3 group slots. Group 1 is the default.</td></tr></tbody></table>

{% hint style="info" %}
Remember that "**job role" might be achieved by either roles or positions**, so it's likely you'll be using one or the other, depending on the requirements of your exercise - see table above.
{% endhint %}

The image below shows how the team-role-positions relate to each other:

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

{% hint style="info" %}
To find out more about dynamic publishing, visit the page below:
{% endhint %}

{% content-ref url="/pages/MXwSnJU1rqjmYUfNQ1Xe" %}
[Dynamic publishing](/feature-documentation/designing-and-running/teams-roles-positions-and-groups/dynamic-publishing.md)
{% endcontent-ref %}


---

# 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.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.