> 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/facilitation/facilitator-dashboard/positions-and-special-permissions.md).

# Positions and Special Permissions

In the Facilitator Dashboard under `Teams`, positions and special permissions can be assigned to give participants **access to certain features**. 

## The differences

Positions and special permissions have some differences:

**Positions** 

* Can only apply to **one** player (are exclusive)
* The features (permissions) unlocked are specific to the exercise and affect impersonation and possibly content that's received

**Special permissions** 

* Can be applied to **all** participants (not exclusive)

## Positions

Create your positions in the Editor. 

{% hint style="info" %}
To find out more on how to create Positions and what they are, visit the page below: 
{% endhint %}

{% content-ref url="/pages/5mCOD9OeNGKUitI6Kqkt" %}
[Impersonation](/feature-documentation/designing-and-running/teams-roles-positions-and-groups/impersonation.md)
{% endcontent-ref %}

### Assigning Positions

In the Facilitator Dashboard, navigate to `Teams` and click `Edit` in the top right-hand corner.  The team table can now be edited: start typing or select positions from the drop-down, click `Save`. 

{% hint style="success" %}
A position can only be assigned once, but players can be assigned multiple positions.
{% endhint %}

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FYwft8iW44qt9FZ5Z182a%2Fimage.png?alt=media&amp;token=dbecf06a-4570-4061-a040-eb853c32dbb1" alt=""><figcaption></figcaption></figure>

## Special permissions

While special permissions can be applied to any player, some are intended for the exercise control player and some for the training audience.

Special permissions intended to be used by **exercise control**:

* Checklist
* Evaluation (AAR)
* Edit Geolocation
* Spoof Social Engagement

#### Checklist

Displays the Checklist created by the designer and allows player to check/uncheck a Checklist item.

{% content-ref url="/pages/g2U60AiL9vWhxUhhzDrh" %}
[Checklist](/feature-documentation/designing-and-running/channels/exercise-logging-channels/checklist.md)
{% endcontent-ref %}

#### Evaluation (AAR)

Allows a player to make assessment comments on any content and Checklist items.&#x20;

{% content-ref url="/pages/H7o1n3mUcpot6akEztVf" %}
[After Action Review (AAR)](/feature-documentation/designing-and-running/observation/after-action-review-aar.md)
{% endcontent-ref %}

#### Geolocation

Edit a persona's MicroBlog (Twitter/X) account GPS coordinates and hence, location, of that persona's tweets.

#### Spoof Social Engagement

Change the count of likes, retweets, and comments on social media.

{% content-ref url="/pages/tJ7C05QwGdBXrWNwmNzH" %}
[Spoof social engagement](/feature-documentation/designing-and-running/adjudication/spoof-social-engagement.md)
{% endcontent-ref %}

Special permissions intended to be used by the **training audience**:

* Create GoSocial (Facebook) groups&#x20;
* Helpdesk Agent

#### Create GoSocial (Facebook) groups

Allows a player to create new GoSocial (Facebook) groups living during the exercise.

{% content-ref url="/pages/XU5I9KnSWynz9MJNaZv9" %}
[GoSocial (Facebook)](/feature-documentation/designing-and-running/channels/popular-channels/gosocial-facebook.md)
{% endcontent-ref %}

#### Help Desk Agent

Displays the Help Desk channel for the player with this special permission assigned.

### Assigning special permissions

In the Facilitator Dashboard, navigate to `Teams` and click `Edit` in the top right-hand corner.  The team table can now be edited: select special positions from the dropdown, click `Save`.&#x20;

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2F7ZXnbSfGW4JMPfj0im7A%2Fimage.png?alt=media&amp;token=57809e0a-4744-43b9-831a-86cd3c691e1b" alt=""><figcaption></figcaption></figure>


---

# 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/designing-and-running/facilitation/facilitator-dashboard/positions-and-special-permissions.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.