Skip to content

Application Form Settings

The public apply form requires applicant identity fields before an application can be created:

  • attributes.firstName
  • attributes.lastName

Application form settings must always include these two fields. They are saved as required fields, shown as required in the admin form-fields list, and cannot be removed from that list.

The admin API normalizes ApplicationFormSettingsDto.Fields on both GET and POST for /v2/organisations/{organisationId}/membership/applications/settings:

  • missing First Name or Last Name fields are restored;
  • IsRequired and IsIncluded are forced to true;
  • IsDeleted is forced to false;
  • legacy raw ids FirstName and LastName are converted to the canonical attributes.* ids and duplicate identity fields are collapsed.

The selectable field catalog (GET /v2/organisations/{organisationId}/membership/applications/settings/fields) still offers First Name and Last Name, because the same catalog also feeds the plan signup form and group membership form field pickers, where these fields remain freely selectable. The application form invariant is enforced by the GET/POST normalization above plus the admin UI locks; in the application form "Add Field" modal the two identity fields therefore always appear under "Already Selected Fields" and cannot be added twice.