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

# Registration

Registration is how you identify participants in your exercise. Conducttr offers several options to suit different needs of security, privacy, and convenience. 

| Benefit                                      | Feature                                                                                                                                                                                                 |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Allows the exercise to identify participants | <ul><li>Seven types of registration available</li><li>Customisable welcome and password reset emails</li><li>Whitelist players/domains</li><li>Add the prompt for team members to join a team</li></ul> |

## 🔀Which registration type should you use?

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2F5zKZ6mJuhdMBpE1K5Mlx%2FChatGPT%20Image%20Aug%2027%2C%202026%2C%2012_41_20%20PM.png?alt=media&amp;token=abb1d55e-c975-42f4-bd1c-cd3464acead3" alt=""><figcaption></figcaption></figure>

### Options & benefits

<table><thead><tr><th width="129.55560302734375">Registration type</th><th>Benefit/s</th></tr></thead><tbody><tr><td><strong>Click-to-play (Default)</strong></td><td><ul><li>Fast and easy access for players</li><li>Players are <strong>anonymous</strong> unless they update their profile</li><li>Roles and positions can be added via the Facilitator Dashboard</li></ul></td></tr><tr><td><strong>Email registration</strong></td><td><ul><li>Player history is remembered across devices</li><li>Player <strong>identified by email address</strong></li><li>Email address doesn't need to be player's real-life email address</li><li>Access can be restricted to whitelisted email addresses</li><li>Pre-assign roles and positions in the teams table</li><li>Password required</li></ul></td></tr><tr><td><strong>Email registration with click-to-play</strong></td><td>Players offered chance to <strong>try the experience</strong> with click-to-play before committing their email address with registration</td></tr><tr><td><strong>Access with passcode (no email required)</strong></td><td><ul><li>Email address is not required</li><li>Only passcode set by designer is mandatory</li><li>Able to <strong>add first and last name</strong> as optional, or can be made mandatory</li></ul></td></tr><tr><td><strong>Single sign-on only</strong></td><td><ul><li>Able to restrict access to whitelisted email addresses</li><li>Available as an <strong>additional registration for email</strong>/can be used on its own</li></ul></td></tr><tr><td><strong>2FA (2-step) Email registration</strong></td><td><ul><li><strong>Email address must be verified</strong> by the player</li><li>Password is required and reset will be sent to verified email address</li><li>Welcome email and password reset emails are customisable</li><li>Able to restrict access to whitelisted email addresses</li></ul></td></tr><tr><td><strong>2FA (2-step) Email and mobile</strong></td><td><ul><li>Please see above (same applies)</li><li><strong>Phone number</strong> must also be verified by the player</li></ul></td></tr></tbody></table>

{% hint style="success" %}
Most of our clients use **Email registration with pre-set passwords**, making the login process quick and simple for players while still reaping the benefits:

* Players are immediately identifiable and their history is remembered
* Designers can pre-assign roles and positions in the teams table and pre-register fictional email addresses if they wish
  {% endhint %}

## Configuration (How to)

You'll find all registration options in `Configuration` > `Participants` > `Registration`:

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FXgvhevtZDUxFIeDMvQBK%2Fimage.png?alt=media&amp;token=853831fc-f08d-4ee9-8e6b-811dac08b2d9" alt=""><figcaption></figcaption></figure>

### Pre-registration

Navigate to `Teams` to set up your teams table and preregister participants.

{% hint style="info" %}
For more information on the teams table, visit the page below:
{% endhint %}

{% content-ref url="/pages/ezFsBUecds4TROGiLo7j" %}
[Setting up your teams table](/feature-documentation/designing-and-running/teams-roles-positions-and-groups/setting-up-your-teams-table.md)
{% endcontent-ref %}

### :star:Whitelisting

Whitelisting options can be found in the Registration area:

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FJ9PRfzz21mwUY6b2LyD8%2Fimage.png?alt=media&amp;token=aef2fc92-0201-4f71-80e0-5631da2c1736" alt=""><figcaption></figcaption></figure>

### :zap:Allow players to select their team

If you don't have player details in advance of the exercise and it's desirable to put players into different teams, you can move them in the Facilitator Dashboard.&#x20;

You can also ask players to select a team on registration. To turn on this option, click the selector shown in the image above.


---

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