Add Signup Profile Fields
Create custom signup fields and configure validation for each field type.
Use this guide when you need to add a new field to the self-service signup form.
Before you begin
You need:
- Admin access to registration settings.
- A stable field key.
- A user-facing display label.
- The field type and validation rules.
- A decision about whether the field is required.
Required fields block signup until the user enters a valid value.
Plan and create the field
Choose a field type
Built LMS supports these custom field types on the registration page:
| Type | Best for | Options |
|---|---|---|
| Text | Short free-text values such as employee ID, region code, location, or team name. | Min length, max length, optional regex pattern. |
| A second email-style field, such as manager email or approver email. | Email format validation. | |
| Select Dropdown | A controlled list such as department, region, cohort, partner tier, or role family. | Add one or more options. |
| Checkbox | Yes/no acknowledgements or simple attributes. | Default checked or unchecked. |
| Textarea | Longer free-text details. | Number of rows. |
Prefer Select Dropdown when the value will be used for filtering, reporting, imports, learning path conditions, or integration matching.
Add a custom field
- Open Registration settings.
- In Profile Field Configuration, select Add Field.
- Enter Field Key.
- Enter Display Label.
- Choose Field Type.
- Configure any type-specific options.
- Turn on Required field if users must complete it to create an account.
- Select Create Field.
- Review the field in Signup Form Preview.
If the field key or display label is missing, Built LMS blocks the save and shows a validation error.
Configure field behavior
Configure validation
For Text fields, you can add:
- Min Length
- Max Length
- Regex Pattern
Use length limits for values with known boundaries, such as employee IDs or cost center codes.
Use regex patterns only when the format matters and your admins can maintain the pattern. A bad pattern can block valid signups.
Examples:
| Need | Example pattern |
|---|---|
| Letters and numbers only | ^[A-Za-z0-9]+$ |
| Three uppercase letters plus three numbers | ^[A-Z]{3}[0-9]{3}$ |
| Two-letter region code | ^[A-Z]{2}$ |
Test any regex pattern with a sample user before making the field required.
Configure non-text field options
Choose Email when the additional field should contain an email address, such as manager email, approver email, work email alias, or partner contact email. Do not use this field for the user's primary login email.
Choose Select Dropdown when users must choose from a controlled list:
- Select Select Dropdown as the field type.
- Enter an option in Add option.
- Select Add.
- Repeat until every option is listed.
- Remove any option that should not appear.
- Select Create Field or Update Field.
Choose Checkbox for a yes/no value. Use required checkboxes for explicit acknowledgements, not ordinary profile data.
Choose Textarea for longer responses. Use textarea fields sparingly because they are harder to filter and compare.
Verify success
The new field is ready when:
- The field appears in Signup Form Preview.
- Required markers match your intent.
- Dropdown options are complete.
- Regex and length validation pass realistic sample values.
- The form still feels short enough for signup.
Troubleshooting
Open the field, check the field type and validation options, and test a value that should pass. If users are blocked unexpectedly, make the field optional until the validation rule is fixed.
Edit the dropdown field and add at least one option. A select field without options cannot collect a useful value.
Check the regex pattern. Test the pattern with realistic sample values before making the field required.