The Builder and Preview

The Edit Form view is in two columns. On the left side, you have the Builder where you can create and edit all the fields for your form. On the right side, you have the Preview to see how the Form will look to the candidates.

The Builder column starts with two important fields: Title and Candidate Target Stage.

Title
- internal name in Teamdash
- could refer to the general purpose of the Form, e.g an automatic form called "Basic Application Form / ENG".
- could refer to the specific project with name and time references.
Candidate Target Stage (Only for Application forms)
- default option "Automatic - inherit from landing". Read here about the Automatic Form type.
- a specific project/stage - the Candidate Target Stage offers a drop-down list of all your active projects with their stages. This is legacy option to link one Form with one specific target project.

Fields

All fields in the Preview are set in the Builder column.

For each field, you can choose:

Type. It can be a variety of field types:
Read more about these below.
Label - it is the field name that is visible to applicants.
Candidate profile target field - it will determine if and where should the submitted information be added to the Candidate Profile in Teamdash.
For example, you can ask an additional question and set the answer to be visible under the Comments tab on the Profile:

Rules - if the answer is required or not.

Field Types

Each field in your form can be set to one of the following types. The right type depends on what kind of answer you want to collect, and where that answer should end up.

Basic input

Text – a short, single-line answer field. Best for names, short answers, or anything free-form and brief.
Long text field – a multi-line text area for longer answers, like a motivation letter or a detailed response.
Phone number with area code – a phone input with a built-in country/area code selector.

Choices

Select – a dropdown with a single answer, chosen from a list of preset options.
Multiselect – a dropdown allowing several answers, shown as tags once selected.
Multiselect (with checkboxes) – the same multiple-answer functionality as Multiselect, but displayed as a checkbox list instead of a dropdown.
Checkbox – a single yes/no toggle. Useful for confirmations or agreements.
Checkbox with number – a checkbox paired with a number value, most commonly used to set the length of an extended GDPR consent period.

Files

File uploader – lets the applicant upload a single file (e.g. CV, cover letter).
Multiple files – lets the applicant upload several files in one field (e.g. portfolio samples).
File (legacy) – an older file upload field type.

Other

Date (calendar) – a date picker, for example for availability or a preferred start date.
Location – lets the applicant enter or select a geographic location.
Numeric rating – a numbered scale, often used for satisfaction or self-assessment questions.
cNPS score – the standard 0–10 scale field used specifically in Candidate Net Promoter Score surveys.
Static text – displays text only; the applicant doesn't fill anything in. Used for instructions or additional context.
Privacy policy – a dedicated field for linking to your organization's privacy notice, so applicants can confirm they've read it.
Hidden – a field that isn't shown to the applicant at all, but can still carry a value (e.g. a source tag or campaign ID) into the candidate profile.

Position select fields

There are four position-related field types, split along two dimensions: how the list of positions is built (manually vs. automatically from a feed), and how many positions the applicant can pick (single vs. multiple).

Position select – a dropdown where you manually choose which positions appear as options. Applicants can select multiple.
Position select (single) – the same manual setup, but applicants can only choose one position.
Position select from feed – a dropdown that populates itself automatically from a feed, the same feed mechanism used to publish job ads to job boards. Applicants can select multiple positions.
Position select from feed (single) – the same feed-based setup, but limited to a single selection.

When to use manual vs. feed-based:

Use Position select or Position select (single) when you want full control over exactly which positions show up, regardless of what's currently live on a feed — for example, a short curated list for a specific campaign.
Use Position select from feed or Position select from feed (single) when you want the list to stay current automatically, with zero manual upkeep.

How the feed-based types work: when you assign a feed to one of these fields, every job ad you export to that feed automatically appears as an option in the dropdown — no need to edit the form itself. When a job ad is unpublished or removed from the feed, it disappears from the list just as automatically.

Why it's useful — the internal referral form example:
This is especially handy for building an internal employee referral form. Add a field like "What role would they be a great fit for?", set its type to Position select from feed, and assign it to your referral feed or any active feed that you already publish to(e.g. Career page feed). From then on:

You export a new job ad to your job boards and to the feed in the same flow.
The job ad instantly appears as an option in the referral form's dropdown.
Employees can immediately refer a friend for that role — without you ever touching the form again.

This removes the manual step of updating the form every time a new project opens or an old one closes, keeping the referral form always up to date.

Conditional fields

A conditional field is a form element that appears based on a user’s previous input, allowing the form to dynamically adjust and display only the fields that are relevant to the user’s selections.

To create a form with conditional field(s), start by editing your form or creating a new one.

When you want one of the question fields to adjust dynamically, its type has to be Select or Multiselect.

✍️ Example:

The form includes a question about previous work experience.

Goal: if a candidate has previous experience, the form will show an additional question.

Add a new field below it and turn on the Conditional field toggle. Assign the previous field for the 'Show this field when', and select under 'Has one of the values' which input(s) will trigger the conditional field to be displayed.

Do not forget to assign the Candidate profile target field, and if necessary, set the Rules as well.

✍️ This is how candidates see the form, when 'Yes' is selected for the "Do you have any previous work experience?" question:

Screen Recording 2025-11-14 at 12.52.12.mov [video-to-gif output image]

If "Please describe your previous experience" were a Select or Multiselect type field, you could add another conditional field below it, which would then also be displayed based on the setup of the field. This allows us to create a chain of conditional fields.

Add and Arrange new Fields

You can always customize and add more fields to your application form.

Click the +Add Field button below your existing fields to create a new label.
Name and customize the new Field.
Click, hold, and drag to re-arrange the order of the fields.

Styling

After the field blocks, you can see design options for your application form in the Builder column. You can change the button text, and set colors by adding the color HEX code you wish to use.

When you create a form for your landing pages, we recommend to switch on "Use landing page theme". This guarantees that the form design and colors will adopt to your landing page settings.

After creating a Form to match your organization, you can save it as a template as well.

Forms and GDPR

It's easy to be GDPR compliant while using Teamdash application forms.

Static Text field
- The form must include a reference to your privacy notice for recruitment processes. The privacy notice must be informative.
- Add a notice to the label text and add a the public link via the Link icon into your label text.
Checkbox Numeric - Months of GDPR consent
- With Teamdash Forms, you can ask the applicants for a longer data processing consent with the application.
  - by default, the data processing consent is valid until the project end after submission.
  - if a candidate consents to a longer data processing agreement, the profile remains a valid GDPR consent until specific date.
  - the Forms settings must comply with your organizations privacy notice.

Creating Forms