Form fields reference
Review the supported participation form field types, authoring constraints, and answer visibility.
This reference lists the field types currently supported in participation form schemas, along with the main rules and limits to keep in mind when you build them.
Use stable field labels
Participation form CSV exports use field labels as column headers. Choose labels that will still make sense when you review answers later.
Supported field types
| Field type | What the participant sees | Notes for schema authors |
|---|---|---|
| Text | A one-line free-text input | Good for short answers such as city, code, or short comments |
| An email input | OmniLab validates the email format | |
| Number | A numeric input | Accepts numeric values only |
| Telephone | A phone number input | Use when you want a phone number instead of a generic text field |
| Dropdown | A select list | Add at least 2 options so participants have a meaningful choice |
| Checkbox | A yes/no checkbox | Good for acknowledgements or simple confirmations |
| Date | A date picker | The submitted value must be a valid date |
| File | An image upload field | Best for photo collection; keep uploads under 2 MB after processing |
What you can configure on each field
Every participation form field should have a clear label. Depending on the field type, you can also configure:
- an optional description to help the participant understand the question
- a
Required fieldsetting - a placeholder for input-based fields
- a list of options for dropdown fields
A form schema must contain at least one field before it can be saved.
Editing rules that affect existing answers
Participation form schemas are reusable. If you update a schema, the change can affect every campaign that uses it.
| Change | Practical effect |
|---|---|
| Correcting label text or fixing typos | Safe for readability and does not change the meaning of past answers |
| Deleting a field | Past answers for that field can be lost |
| Changing dropdown choices | Older answers may become harder to compare with new ones |
| Swapping the schema on an active campaign | Existing response history may no longer line up with the new schema |
Export answers before major edits
Before you delete fields, swap schemas, or redesign an active questionnaire, export the existing participation form answers first.
Where answers appear
Participation form answers are available in the participant detail view and in the campaign's participation form exports. Clear, human-readable labels make those views much easier to work with.