Configure Signup Profile Fields
Plan custom fields shown during self-service signup and route to the right setup task.
Use Profile Field Configuration to add organization-specific fields to the signup form.
Custom signup fields are useful when admins need consistent profile attributes before a user receives access. They can also support reporting, integrations, SSO mappings, and learning path conditions.
Before you begin
You need admin access to change registration settings.
Before adding fields, decide:
- Which profile details are truly needed before first access.
- Which fields should be required.
- Whether each field should be free text or a controlled dropdown.
- Whether reports, imports, integrations, learning paths, or SSO mappings will depend on the field key.
Do not add required fields casually. A required field blocks account creation until the user enters a valid value.
Choose the field task you need
Use the focused guide that matches the job:
- Add Signup Profile Fields to choose field types, create fields, and validate text, email, dropdown, checkbox, or textarea inputs.
- Maintain Signup Profile Fields to edit, reorder, preview, or delete existing signup fields.
Understand signup fields
Built LMS always includes these system fields:
| Field | Required | Can admins remove it? |
|---|---|---|
| First Name | Yes | No |
| Last Name | Yes | No |
| Yes | No | |
| Password | Yes | No |
Custom fields appear under Additional Information on the signup form. They are also used elsewhere in the product where custom user attributes are available, such as user management, reporting, integrations, and learning path conditions.
Plan field keys carefully
The Field Key must contain only letters, numbers, and underscores.
| Good field key | Avoid |
|---|---|
department | Department if you prefer lowercase conventions |
employee_id | employee id |
partner_tier | partner-tier |
manager_email | manager.email |
Use short, stable keys. Avoid names tied to a temporary campaign, team reorganization, or one-time import.
Verify success
Signup field planning is ready when:
- Every required field is genuinely needed before first access.
- Field keys are stable and use only letters, numbers, and underscores.
- Dropdown fields have planned option lists.
- Reporting, integration, SSO mapping, or learning path dependencies are known.
Troubleshooting
Move optional fields out of signup where possible. Keep signup focused on fields needed before first access.
Make the field optional first, then review whether missing values actually block the downstream workflow.