Skip to main content

Forms - Article

Configure forms for persistent profile data, account entry, enrollment and other business moments, including current editability and source-ownership rules.
Updated: 14 Nov 2026
11 min read

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.

FormBusiness momentWhat the information belongs to
ProfileA person reviews or maintains their persistent information.The user account and profile.
SignupA person creates their own account.The new user account and supported profile fields.
Create userAn authorized role creates an account for someone else.The new user account and supported profile fields.
LoginA person chooses an available sign-in method.The access experience; it does not collect general profile information.
EnrollA person enrolls or purchases in an Individual, Company, Government, or Other context.The enrollment or Transaction. Checkout edits do not rewrite the profile.
ContactA person sends a request to the organization.The contact request. Known profile information can be prefilled without becoming a profile update.
Activity tagsAn 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 sourceExamplesImportant consideration
System fieldsFirst name, Last name, Email, Username, Role, Status, PasswordSome are essential to account creation or access and have special rules.
Profile fieldsPhone, address, Company, Immediate Manager, lifecycle datesAvailability and editability depend on the Profile form and supported context.
Vocabularies and tagsDepartment, Job function, Workplace, Unit, Location Code, TypeControlled values improve consistency for filtering, reporting, and audience logic.
Feature-dependent fieldsBankID, Contact Manager, selected preferences or integration optionsThey appear only when the related feature and configuration are available.
Customer-specific fieldsFields introduced for an agreed implementationCheck 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

  1. Open Settings → Forms.
  2. Choose the form you want to configure.
  3. Enable the fields that are relevant to that process.
  4. Make only the fields required at that moment mandatory.
  5. Drag fields into an order that follows the user’s task.
  6. Adjust labels, help text, and translations where available.
  7. For the Profile form, decide whether end users may edit each supported field.
  8. 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:

OptionEffect
Enable or disableShows or removes the field in that form.
Required or optionalDetermines whether the form can be submitted without a value.
OrderPlaces the field in the sequence users will follow.
Label and help textUses language appropriate to the business process without changing the underlying field.
TranslationsSupplies the supported labels and guidance for each language.
Allow end users to edit this fieldControls 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:

GroupStandard fields and examplesTypical purpose
Identity and accountTitle, First name, Last name, Username, Email, Role, StatusIdentify the account, support sign-in and communication, and define account access.
Contact and addressMobile Phone, Phone, Country, State or Region, City, Street, Street Number, Postal CodeCommunication, location context, logistics, and supported regional processes.
Business relationshipsOrganization, Company, Immediate Manager, Contact ManagerManaged-customer or partner relationships, staff oversight, and supported promotion flows.
Controlled organizational attributesLocation Code, Workplace, Department, Type, Job Function, UnitConsistent segmentation, reporting, audience selection, and integrations.
Employment and lifecycleHire Date, Birthday, Graduation Date, Probation End Date, Audit Date, Last Working Day, Active, User Type, Employment Type, Employee IDOnboarding, employment context, review processes, and lifecycle reporting.
Feature-dependent identityBankID and other implementation-specific identity fieldsSupported 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 tabTypical information
IndividualPersonal contact and address information used for the enrollment or order.
CompanyCompany, registration and VAT information, purchase-order reference, address, and contact details.
GovernmentGovernment or public-sector identifiers, EAN or purchase-order references, VAT information, address, and contact details.
OtherAdditional 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.

PracticeWhy it matters
Define the authoritative owner of important dataPrevents imports, SSO, questionnaires, and manual edits from competing for the same field.
Collect information at the moment it becomes usefulReduces friction and improves the quality of submitted values.
Prefer controlled vocabularies for operational classificationsProduces dependable filters, audiences, reports, and integrations.
Keep transaction information out of the persistent profile unless it has lasting valuePreserves accurate order history and avoids turning one purchase into a permanent identity change.
Test with the intended role and organizationConfirms that field visibility and editing rights match the real operating context.
Download fresh import templates after field changesKeeps the spreadsheet structure aligned with the active Profile form.

Verify a form change

After saving a form:

  1. Open the form in the intended workflow and role.
  2. Confirm that fields appear in the expected order with the correct labels and translations.
  3. Test required-field validation.
  4. Submit a safe test value when appropriate.
  5. Verify the correct destination: profile, new account, Transaction, contact request, or activity.
  6. Confirm that imports or integrations still use the intended fields and identifiers.

Troubleshooting

ProblemWhat to check
A field is not available in a formConfirm 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 editedCheck 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 importCheck Settings → Forms → Profile. After changing Username, download a new import template.
Signup or Create user shows unexpected fieldsCompare the individual form configuration with the Profile form and enabled vocabularies; each context is configured separately.
Checkout information differs from the profileThis 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 resultVerify the record that received the value and the separate rule, audience, integration, or report that consumes it.

FAQ