# Exercise design

## The practical aspects involving people

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

| Term             | Description                                                                                                                                                                     |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Facilitator**  | The person controlling the pace and direction of the exercise (only 1 permitted)                                                                                                |
| **Observers**    | People with the ability to oversee an exercise and with some scope/permissions to modify the exercise                                                                           |
| **Players**      | These are the target/recipients of the exercise (also called the Training Audience)                                                                                             |
| **Role-players** | 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) |

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


---

# 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/important-foundations/exercise-design.md?ask=<question>
```

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.