> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/configure/advanced-configuration/enrolment-form.md).

# Enrolment Form

Hosted enrolment forms support secure pass creation and retrieval flows. This section covers customer identification, access control, and form behavior used before wallet delivery.

## Customer registration configuration

Customer registration captures identity before issuing a pass. Use it when a CRM or POS account must be created or updated first. It supports website enrolment and in-store QR-code registration.

### Sign-in options (`signinOptions`)

`signinOptions` controls how returning customers are detected and handled. It can check for an existing session or route to a mobile sign-in journey based on device detection.

### Complete options (`completeOptions`)

`completeOptions` is an ordered list of actions taken after successful registration. Each action has a `type`.

| Type             | What it does                                                                                                        |
| ---------------- | ------------------------------------------------------------------------------------------------------------------- |
| `AddToWallet`    | Presents Add to Wallet buttons. Supports `autoDownloadPass` and an optional post-download form.                     |
| `Redirect`       | Redirects to a fixed URI. It supports Liquid variables, such as `{{['id.y2.customerId']}}`, in the destination URL. |
| `RedirectToPass` | Redirects to a named pass-download layout for immediate pass download.                                              |
| `Reset`          | Resets the form after a configured delay in seconds. Use this for shared in-store kiosks.                           |

### Localize form text and consent wording

All customer-facing text on the enrolment form - field labels, instructions, and consent/opt-in copy - is stored in per-tenant localization files. Access them from **Settings** → **Enrolment** → **Localization files**.

<p align="center"><a href="https://admin.thewalletcrew.io/tenant/~/settings/enrolment/localization-files" class="button secondary" data-icon="angles-right">Open Localization files</a></p>

Most tenants have a `fields` locale file (`locales/fields`), which governs the enrolment form field labels and consent/opt-in text. Edit it inline from the Localization files screen, the same way pass template fields are translated (see [How to Translate a template](/configure/advanced-configuration/wallet/template-configuration/how-to-translate-a-template.md)).

Update the wording for every active language configured on the tenant. A change made in one locale file does not propagate to other languages automatically.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>Enable Email check-in on Enrolment Forms</h4></td><td>Secure hosted enrolments flow, check existing customers by email, add optional verification, and reduce duplicate accounts before pass creation, reterieval, or wallet downolad across campaigns.</td><td><a href="/files/Acd9UnI83Z8OHH65LzU3">/files/Acd9UnI83Z8OHH65LzU3</a></td><td><a href="/pages/QbgmRSWuqATWBWZ5O04w">/pages/QbgmRSWuqATWBWZ5O04w</a></td></tr></tbody></table>

The Enrolment Form section covers the advanced configuration of the sign-up experience. When a customer submits their email address, TWC can automatically check whether they already exist in the system. If they do, an optional verification step — such as a one-time code or magic link — secures access before the pass is issued. If they don't, the form collects the remaining details and creates a new record. This prevents duplicate entries and keeps your customer database consistent, without requiring any additional development on your side.


---

# 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://docs.thewalletcrew.io/configure/advanced-configuration/enrolment-form.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.