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

# Registration

Before publishing your exercise, make sure to configure your registration settings. This ensures: 

* Your **registration type** matches the scope of the exercise
* The right person is set as **Facilitator** (this isn't a Facilitator in the traditional sense, but the person who can access all the participant data)
* Your participants are set up in the **Teams table** (if necessary)

## How to

In `Configuration` in the Editor, you can tweak the registration settings for your self-paced exercise:

### Registration type

<figure><img src="/files/X4tpXC068a6yTJlFoOdD" alt=""><figcaption></figcaption></figure>

There are many registration types to choose from, but the most popular are:

* **Click to play**
* **Email registration**

This is because they are both simple to set up and to use.

#### Click to play

{% hint style="warning" %}
This is the default option.
{% endhint %}

If you have **hundreds to thousands of participants** (which is likely for a self-paced exercise) Click to play is the easiest registration type for your exercise.&#x20;

<div align="left"><figure><img src="/files/zRDnVvNogT6hbNZH2yFl" alt=""><figcaption></figcaption></figure></div>

:zap:With this registration type, participants will be given a **randomly generated email address** when they log in to the exercise. This doesn't necessarily matter within the exercise, but if you're looking to export results at the end of the exercise, it can prove difficult to identify specific participants. To get around this, make sure to **ask your participants for their name and/or email address via an open-text box question** at some point in the exercise.

{% hint style="info" %}
Find out how to use your participant's entered name within an exercise with smartwords on the page below:
{% endhint %}

{% content-ref url="/pages/4VmDimP83MOaoSFhzn4B" %}
[Smartwords](/colibri/building-exercises/smartwords.md)
{% endcontent-ref %}

#### Email registration

If you have **less participants** and you're looking to **easily track your participants in the reporting phase** of an exercise, we recommend setting your registration type to Email registration. This can also make logging in to the exercise smooth for participants, especially if they're revisiting the exercise multiple times.

<div align="left"><figure><img src="/files/XM7EfRh1voR1Kxgu7kYr" alt=""><figcaption></figcaption></figure></div>

If participants aren't set up in the Teams table beforehand, they'll need to click Register before the exercise to set up their own accounts. But doing it for them makes accessing the exercise much easier and faster.

{% hint style="info" %}
To find out more about preregistering your participants, visit the page below:
{% endhint %}

{% content-ref url="/pages/KHZ6IXsnPuzCMU8HtfHQ" %}
[Teams table](/colibri/building-exercises/registration/teams-table.md)
{% endcontent-ref %}

**Whitelisting domains**

Alternatively, you can restrict registration to whitelisted domains. Only participants with an email address from an approved domain will be able to register for the exercise.

This saves you from preregistering participants individually, while still giving you control over who joins, and keeping everyone identifiable, both within the exercise and in the reports.

<figure><img src="/files/JgiWXA0O0c5lIUoaizRl" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To find out more about reporting in Colibri, visit the page below:
{% endhint %}

{% content-ref url="/pages/HbnsW6lxvcszsWjOskDT" %}
[Reporting](/colibri/reporting/exporting-results.md)
{% endcontent-ref %}


---

# 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/colibri/building-exercises/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.