# User Registration & Verification

This workflow covers creating a user account with email/password and verifying the email address before allowing login.

## Prerequisites

* Users table in the helper file with fields for: `email`, `passwordHash`, `isVerified`, `isEnabled`, and timestamps
* Email delivery configured in `onAuthNotifier` (server-side) for verification messages

## Workflow

1. User submits the registration form
2. Run `authRegister` action
3. Helper file creates the user (password stored as a one-way hash)
4. System sends verification email with a time-bound verification link
5. User clicks the link and lands on a verification page
6. Run `authVerify` action on page load to confirm the token
7. Mark the user record as verified (`isVerified = True`)
8. Optionally sign the user in or redirect to login

## Page Actions

* Registration page: `authRegister`
* Verification page: `authVerify` (recommended to run in an onFormLoad named action)
* Optional resend-verification UI: `authResend` (requires `email`)

## Hooks (FileMaker)

* `onRegistration`: optional post-registration business logic
* `onAuthNotifier`: send verification email and any admin notifications

## Data Considerations

* Verification tokens should be treated as secrets; avoid logging or storing them in cleartext
* Verification tokens should be time-bound and single-use

## Practical Notes

* Registration pages must provide `email` and `password` in the page model before running `authRegister`
* If you want a second "confirm password" field, use a custom validator to compare `password` and `password2`
* Authentication feedback can be shown with `model.authMessage`, or more robustly with `model.authMessageCode` and `model.authMessageType`
* Verification pages usually run `authVerify` automatically in `onFormLoad`
* The verification action reads the token from the URL; you generally do not need to parse it manually
* Users must still be enabled (`isEnabled = true`) to sign in after verification

## Related Pages

* [Authentication](/reference/authentication.md)
* [Authentication Actions](/reference/actions-processor/authentication-actions.md)
* [Custom Login Pages](/reference/authentication/custom-login-pages.md)


---

# Agent Instructions: 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:

```
GET https://docs.klai.studio/reference/authentication/basic-auth/user-registration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.