> 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/important-foundations/exercise-design.md).

# Exercise design

## The practical aspects involving people

On your exercise you'll have participants performing various functions. The terms we use are:

<table><thead><tr><th width="173.33331298828125">Term</th><th>Description</th></tr></thead><tbody><tr><td><strong>Facilitator</strong></td><td>The person controlling the pace and direction of the exercise (only 1 permitted)</td></tr><tr><td><strong>Observers</strong></td><td>People with the ability to oversee an exercise and with some scope/permissions to modify the exercise</td></tr><tr><td><strong>Players</strong></td><td>These are the target/recipients of the exercise (also called the Training Audience)</td></tr><tr><td><strong>Role-players</strong></td><td>A special type of player who has permissions allowing them to interact with players, but disguise themselves as stakeholders (make up EXCON with the Facilitator and Observers)</td></tr></tbody></table>

## Access to the exercise

Access to an exercise is governed by the **role and registration** method.

Facilitators and Observers are privileged users and must use two-factor authentication (2FA). This means they must use real email addresses and these email addresses must be pre-registered by the designer by uploading (via the Teams table) to the simulation space.

Players can join an exercise via a wide range of registration options. The **benefit of pre-registration is that positions, roles, teams and passwords can be pre-assigned** and hence make the start of an exercise slicker (and usually easier to test).

Role-players can join as players (recommended) or join as a special "persona-as-team member".&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocs.conducttr.com/feature-documentation/important-foundations/exercise-design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.