Forms - Article
Summary
Forms control which information is requested at important points in the user journey and how each field is presented. Some forms create or maintain persistent user information; others collect information for a specific enrollment, order, contact request, or activity.
Use this article to:
- Choose the correct form for the business moment.
- Understand which fields can be made available and where their values are stored.
- Configure visibility, requirement, order, labels, translations, and user editability.
- Keep profile information, authentication, and Transaction information under clear ownership.
Choose the form by purpose
Forms are not interchangeable. Begin with the record or process you intend to support.
| Form | Business moment | What the information belongs to |
|---|---|---|
| Profile | A person reviews or maintains their persistent information. | The user account and profile. |
| Signup | A person creates their own account. | The new user account and supported profile fields. |
| Create user | An authorized role creates an account for someone else. | The new user account and supported profile fields. |
| Login | A person chooses an available sign-in method. | The access experience; it does not collect general profile information. |
| Enroll | A person enrolls or purchases in an Individual, Company, Government, or Other context. | The enrollment or Transaction. Checkout edits do not rewrite the profile. |
| Contact | A person sends a request to the organization. | The contact request. Known profile information can be prefilled without becoming a profile update. |
| Activity tags | An authorized role classifies an activity using supported tag fields. | The activity and its content classification, not the user profile. |
A field displayed in a form does not by itself show where the submitted value is stored. Confirm whether that form writes to the profile, a Transaction, or another record before relying on the value.
Understand where fields come from
A form presents fields supported by its context. The available choices can come from several sources:
| Field source | Examples | Important consideration |
|---|---|---|
| System fields | First name, Last name, Email, Username, Role, Status, Password | Some are essential to account creation or access and have special rules. |
| Profile fields | Phone, address, Company, Immediate Manager, lifecycle dates | Availability and editability depend on the Profile form and supported context. |
| Vocabularies and tags | Department, Job function, Workplace, Unit, Location Code, Type | Controlled values improve consistency for filtering, reporting, and audience logic. |
| Feature-dependent fields | BankID, Contact Manager, selected preferences or integration options | They appear only when the related feature and configuration are available. |
| Customer-specific fields | Fields introduced for an agreed implementation | Check which process owns each field and when it applies; these fields are not universal defaults. |
Use Settings → Tags to maintain the controlled values behind vocabulary- or tag-based fields. Activating a field makes it available only in the forms and workflows that support it; it does not make every form write to the same record.
Configure a form
- Open Settings → Forms.
- Choose the form you want to configure.
- Enable the fields that are relevant to that process.
- Make only the fields required at that moment mandatory.
- Drag fields into an order that follows the user’s task.
- Adjust labels, help text, and translations where available.
- For the Profile form, decide whether end users may edit each supported field.
- Save the form and verify the result in the intended role and process.
The exact controls depend on the form and field. Common options include:
| Option | Effect |
|---|---|
| Enable or disable | Shows or removes the field in that form. |
| Required or optional | Determines whether the form can be submitted without a value. |
| Order | Places the field in the sequence users will follow. |
| Label and help text | Uses language appropriate to the business process without changing the underlying field. |
| Translations | Supplies the supported labels and guidance for each language. |
| Allow end users to edit this field | Controls self-service editing on the Profile form for supported fields. |
Role, Status and BankID cannot be made editable by end users. Participants and Auditors cannot edit Organization even when Allow end users to edit this field is enabled. A separate configuration can give selected administrative roles access to other fields that are disabled for the user, but it does not override a value locked by SSO or another authoritative integration.
Design the Profile form as the persistent user record
The Profile form defines which supported fields appear when a user or authorized role edits persistent profile information. It should contain the information that remains useful beyond one signup, enrollment, order, or support request.
Standard profile-field groups
The fields available on a specific platform depend on its features, vocabularies, and implementation. The standard catalogue includes the following groups:
| Group | Standard fields and examples | Typical purpose |
|---|---|---|
| Identity and account | Title, First name, Last name, Username, Email, Role, Status | Identify the account, support sign-in and communication, and define account access. |
| Contact and address | Mobile Phone, Phone, Country, State or Region, City, Street, Street Number, Postal Code | Communication, location context, logistics, and supported regional processes. |
| Business relationships | Organization, Company, Immediate Manager, Contact Manager | Managed-customer or partner relationships, staff oversight, and supported promotion flows. |
| Controlled organizational attributes | Location Code, Workplace, Department, Type, Job Function, Unit | Consistent segmentation, reporting, audience selection, and integrations. |
| Employment and lifecycle | Hire Date, Birthday, Graduation Date, Probation End Date, Audit Date, Last Working Day, Active, User Type, Employment Type, Employee ID | Onboarding, employment context, review processes, and lifecycle reporting. |
| Feature-dependent identity | BankID and other implementation-specific identity fields | Supported verification or regulated processes where the related feature is enabled. |
Do not assume that a descriptive field creates a relationship. For example, Company is information on the profile, while Organization membership and Immediate Manager are managed relationships that can affect scope and workflow.
For day-to-day profile maintenance and source ownership, see Maintain User Profiles and Information. To understand how these areas appear to the user, see Use Your Profile and Account Settings.
Control who may edit profile fields
For a supported Profile field, Allow end users to edit this field controls whether the person can change their own value. Authorized administrative roles can maintain supported fields according to their role, organizational scope, and the configured Roles with access to edit disabled fields on the profile setting.
Use this separation deliberately:
- Let users maintain personal preferences and contact information where self-service is dependable.
- Protect Role, Status, organization relationships, employment data, and other governance-sensitive values.
- Keep integration-owned fields read-only locally so the next synchronization does not reverse an apparent correction.
- Explain the owner of any field used for eligibility, reporting, access, or automation.
Configure Username and User import
Username can be enabled or disabled on the Profile form. This setting affects both profile editing and the current User import template:
- When Username is enabled, the import template includes a Username column.
- When Username is disabled, the column is removed from a newly downloaded template.
- After changing the setting, download a new template before the next import.
Keep Username enabled when the platform permits non-unique email addresses. In that identity model, Username is the unique account identifier.
The Signup and Enroll forms have their own Username visibility settings. Disabling Username in one form does not by itself remove the field from every other context. For the import workflow, see Import and Update Users in Bulk.
Keep Signup focused on successful entry
The Signup form creates the first version of a self-registered user account. Collect only the information needed to create a dependable identity and support the first experience.
Depending on configuration, the form can include:
- Name and contact fields.
- Email, Username, and Password for the supported local-login model.
- Language, time zone, notification scheme, and interests.
- Organization and controlled attributes such as Department, Workplace, Unit, Location Code, Type, or Job Function.
- Supported address, relationship, employment, and feature-dependent fields.
Every required field adds friction. Use later profile updates or a questionnaire when information is useful after access has been established but is not essential to create the account.
Configure Create user for an assisted onboarding process
The Create user form is used when an authorized administrator or other permitted role creates an account on someone else’s behalf. It can include more structured information than Signup because the operator may already know the person’s role, status, organization, manager, language, time zone, and business context.
The form can also control whether the user creates their own password through the first-access email or whether a local password is set during creation. Include only information the operator can provide accurately. Unknown values are usually better completed later than guessed at account creation.
For the complete procedure and first-access options, see Create a User and Support First Access.
Configure Login as an access experience
The Login form controls which available authentication methods, labels, instructions, and translations are shown. Depending on the platform, these can include regular email-and-password login, SSO, and supported social or external login methods.
Login configuration expresses the organization’s identity and access strategy; it does not extend the general profile-field catalogue. Use the live preview to check clarity before leaving the page. Login-form changes are applied immediately, so confirm that the intended primary and secondary methods remain understandable and reachable.
Use Enroll for Transaction-specific information
The Enroll form collects information needed for a particular enrollment or purchase. It can be configured for several business contexts:
| Enroll tab | Typical information |
|---|---|
| Individual | Personal contact and address information used for the enrollment or order. |
| Company | Company, registration and VAT information, purchase-order reference, address, and contact details. |
| Government | Government or public-sector identifiers, EAN or purchase-order references, VAT information, address, and contact details. |
| Other | Additional context such as a comment. |
The form can begin with known profile information, but a change made during checkout is stored with the resulting Transaction. It does not update the person’s profile. This preserves the historical information used for the specific order.
Use Enroll for billing, buyer type, order contact, and other transaction-specific facts. Use the Profile form, an authenticated profile-update process, or a supported questionnaire when the intention is to maintain the person’s persistent data. See Transactions for the order record and its personal information.
Configure the Contact form for useful requests
The Contact form collects a subject, message, and the supported identity or context needed to route and answer a request. For authenticated users, known profile values can be prefilled to reduce repetition. The form can include name, Company, email, phone, activity context, address fields, organizational vocabularies, and selected employment classifications.
Contact submissions are requests, not profile-maintenance operations. A corrected value typed into a support request should be verified and updated through the appropriate profile or source process.
The available subject categories and recipients are maintained through the supported service configuration. Use subjects that help users recognize the request type and route messages to an accountable team.
Configure Activity tags for content classification
The Activity tags form controls which supported tag fields are presented when an activity is classified. These values belong to the activity and can support storefront organization, discovery, reporting, audience logic, and other configured content behavior. They do not become profile fields merely because the same vocabulary is also used for users.
Coordinate Activity tags with the vocabulary design in Settings → Tags so labels and values remain consistent across content and user contexts.
Apply form governance
Review forms whenever audiences, integrations, commercial processes, regulations, or reporting needs change.
| Practice | Why it matters |
|---|---|
| Define the authoritative owner of important data | Prevents imports, SSO, questionnaires, and manual edits from competing for the same field. |
| Collect information at the moment it becomes useful | Reduces friction and improves the quality of submitted values. |
| Prefer controlled vocabularies for operational classifications | Produces dependable filters, audiences, reports, and integrations. |
| Keep transaction information out of the persistent profile unless it has lasting value | Preserves accurate order history and avoids turning one purchase into a permanent identity change. |
| Test with the intended role and organization | Confirms that field visibility and editing rights match the real operating context. |
| Download fresh import templates after field changes | Keeps the spreadsheet structure aligned with the active Profile form. |
Verify a form change
After saving a form:
- Open the form in the intended workflow and role.
- Confirm that fields appear in the expected order with the correct labels and translations.
- Test required-field validation.
- Submit a safe test value when appropriate.
- Verify the correct destination: profile, new account, Transaction, contact request, or activity.
- Confirm that imports or integrations still use the intended fields and identifiers.
Troubleshooting
| Problem | What to check |
|---|---|
| A field is not available in a form | Confirm that the field type is supported in that form, the related feature or vocabulary is enabled, and the platform does not use a customer-specific alternative. |
| A field appears but cannot be edited | Check the field’s Profile editability, the user’s role and organizational scope, and whether SSO or an integration owns the value. |
| Username is missing from User import | Check Settings → Forms → Profile. After changing Username, download a new import template. |
| Signup or Create user shows unexpected fields | Compare the individual form configuration with the Profile form and enabled vocabularies; each context is configured separately. |
| Checkout information differs from the profile | This is expected when a user changed details for that enrollment or order. The Transaction retains its own personal information. |
| A form change does not produce the expected downstream result | Verify the record that received the value and the separate rule, audience, integration, or report that consumes it. |
FAQ
-
Can different audiences use different registration methods on the same platform?
Yes, where the relevant routes are configured. For example, employees can use a connected identity while customers register through an enrollment journey. Define identity matching and support responsibilities so the routes do not create unnecessary duplicate accounts.
-
Does SSO update every profile field whenever someone signs in?
No universal behavior should be assumed. The connection's mapping and update configuration determine which fields are supplied and when. Confirm ownership and timing with the integration owner before correcting a mapped field locally.
-
Do changes made during checkout update the user's profile?
No. Edits to personal information during checkout are stored with the Transaction rather than written back to the current profile. Maintain the profile through its appropriate editing or source-system process.
-
Can a questionnaire replace existing profile information?
Yes. Supported questions configured to update a profile can overwrite the corresponding values when an authenticated user fully submits the questionnaire. Anonymous responses do not provide the authenticated identity required for this update.
-
Why is a profile field visible but not editable?
Visibility does not always include permission to change the value. Check the support role, organizational scope, field configuration, account context, and whether an import, SSO mapping, integration, questionnaire, or another process owns the field.
-
Which form controls the persistent user profile?
The Profile form controls the fields presented as the person’s persistent profile record. Other forms such as Signup, Create user and Enroll use fields for a particular journey. A field shown in another form does not create a separate copy of the information; verify whether that route writes to the profile before treating it as persistent user data.
-
Does making a field required in one form make it required everywhere?
No. Visibility and requiredness are configured for each form within the platform’s rules. A field may be required during self-registration but optional when an administrator creates a user. Review and test every route used by the intended audiences.
-
Can Forms create completely new profile fields?
Forms controls which available fields are shown and how they behave. It does not by itself create arbitrary new data types. Availability depends on enabled features, platform configuration and supported field sources. If a needed field is absent, verify the configuration or contact Eurekos about a specialized requirement.
-
What happens to User import when Username is disabled?
When Username is disabled in Forms, the Username column is omitted from a newly downloaded user-import template. Use this only when the identity model supports it. Where non-unique email addresses are permitted, keep Username enabled because it provides the unique account identifier. Download a fresh template after changing the setting.
-
Does changing a form remove existing user data?
No. Hiding a field or changing whether it is required changes collection and presentation; it does not automatically erase stored values. Values may still be updated through authorized profile editing, user import, SSO or another integration, or a questionnaire rule according to the field’s ownership.
-
Why is a field missing from the Forms editor?
The field may not apply to the selected form, an optional capability may be disabled, or the field may only be available for a supported identity or data configuration. Confirm the correct form, enabled feature, source ownership and the administrator’s role and scope.
-
How should I verify a Forms change?
Use a representative test account and the exact route the audience will use. Check visibility, requiredness, validation, the saved profile value, and any identity or notification consequence. Repeat the test for relevant roles, organizations, SSO or integrations and screen sizes. Do not rely only on the editor view.