> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/use-wiclax/entering-importing-participants.md).

# Entering, importing participants

Competitors can be registered on an event either via the registration form or by importing an external list.&#x20;

The registration form can be opened by one of the following means:

* from the ribbon: Participants :: Add :: New
* by double-clicking on the grid of participants
* with shortcut key `[F2]`

## Editing data

{% hint style="info" %}
Input order

If you're not happy with the order of data entry in the form, you can easily adjust it by dragging the fields up or down with your mouse. This way, you can for example match the order with that of a paper entry form.
{% endhint %}

## Event data

### Built-in fields

The `Event Data` screen in the Options window allows you to enable the fields you need, from a predefined list.

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FB8owih7mrXAsDTfgUhAm%2Fimage.png?alt=media&amp;token=43fb0b5a-96b0-4198-9e16-facca0c48cf5" alt=""><figcaption></figcaption></figure>

Please note that the selection does not affect the data itself, which will not be deleted if you deselect a field. Instead, it determines which columns are available in the grids, which fields are offered on the commitment form, and which data may be displayed when the results are posted online.

### Custom data fields

In addition to the standard data offered by the software, you have the possibility to create additional personalized information.

<figure><img src="https://1159484786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJRt17XpwpUQzKYPTGL7Z%2Fuploads%2FlGq1Y4d56z0AAv2SlVV8%2Fimage.png?alt=media&amp;token=bc8a1a0d-7a71-486c-8bf3-d029b2e5e0fa" alt=""><figcaption></figcaption></figure>

For each of these new fields, you can specify:

* its name
* its title for printout
* its possible predefined values ​​and default value
* its format (standard, numerical, date or "yes/no")
* its "scope", that is to say whether the data is expected on the participant lists, the results grids and/or the general rankings. For example:&#x20;
  * a "T-Shirt Size" field only on participant lists
  * a "Company" field on lists of entrants + results grids + general rankings, as it can also be used as a basis for a team ranking
  * a "Total height diff" field only on the results grids
* if this data is specific to a stage (otherwise it is by default common to all stages, that is to say that the value entered for a participant cannot be different in each stage)
* if this data is published on the web. Otherwise this data is not exported at all when the event gets published, and therefore cannot be used as part of a competitor filter condition that you'd expect to be publicly available.
* a possible [calculation formula](https://docs.wiclax.com/en/other-features/calculated-fields.md)


---

# 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://docs.wiclax.com/en/use-wiclax/entering-importing-participants.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.
