# Some definitions of who does what

The diagram below shows all the human entities in an exercise:

* there is only 1 **facilitator** role in Conducttr. Their job is to manage the exercise.
* there can be multiple **observers**. Their job is to observe the training audience and report on their performance (although some facilitation privileges can be delegated to them too - see below)
* there can be multiple **adjudicators**. Their job is to observe the evolution of the information space and actions/inaction of the training audience and determine how the information space should change (for example decide which PoL stack to run or actions of role-players)&#x20;
* there can be multiple **role-players**. Their job is to pretend to be a persona and communicate or affect the information environment so as to make the players feel the exercise is realistic.
* there can be multiple **players** - sometimes called the "training audience" and they are the reason the exercise is taking place - to rehearse, exercise or train them.

{% hint style="info" %}
In many exercises someone might perform multiple jobs - for example facilitator, observer and role-player.

In larger exercises there might be a dedicated team of observers and role-players.
{% endhint %}

<img src="/files/miQUp1PJoYx3F5HW0oRY" alt="" class="gitbook-drawing">

## Observers & Adjudicators

In Conducttr the observer & adjudicator functions can be accomplished in either or both of the following ways:

* via a privileged role allowing log in to the *Facilitator Dashboard* and *Pulse*&#x20;
* via the *Virtual Desktop* with *special permissions*
* both

{% hint style="info" %}
For observers that need use the special permissions like Checklist and AAR and have access to the facilitator dashboard and/or Pulse, they will need two log ins - one for the privileged observer role and one as a player with the special permissions assigned.
{% endhint %}

### Privileged observer role

If a person needs **the ability to see whole exercise in progress** then in the Conducttr team table they will likely need to have the observer role. This role will grant them access to Pulse and the Review tab.&#x20;

Some AAR capability is available in the Review tab.

### Special permissions

Only the player role can be assigned special permissions.  The relevant special permissions for observers & adjudicators will be:

* After-Action Review (AAR)
* Checklist
* Spoof engagement
* Change GPS location


---

# 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/some-definitions-of-who-does-what.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.
