Forms: views of your data
A profile form decides what an audience sees of their own record — which fields appear, in what order, and which they can edit. The form is a lens on the data, not the data itself: record values live against your dictionary fields, and the form just chooses how they’re presented.
That has a reassuring consequence: editing a form never loses data. Remove a field from the participant form and its values are still on every record — you’ve only changed what participants can see. There’s nothing to publish and no versions to manage; save a change and it applies immediately.
One form per audience
Each audience slot gets one form:
- Participant — how participants view and maintain their own details for the life of the study. The one that matters most in a study that enrols people.
- Admin, Data entry and Billing — one per member role, for how a member sees their own record.
- Free-standing records — the data-entry view of a record that belongs to nobody. This is the form your team works through when the record is a sample or a site rather than a person, so in a database-shaped study it’s the one that matters most.
Free-standing records get a form but never an onboarding flow — there’s no one joining.
Building a form
The editor works in sections. Add a section, then place dictionary fields into it; drag to reorder either. For each placed field you can set:
- Required — must be filled in.
- Access — editable, or read-only (visible but locked).
- Label override and help text — friendlier wording than the dictionary default.
- Visibility condition — show the field only when another field’s value matches a rule, so forms stay short and relevant.
The live preview beside the editor shows exactly what that audience will see.
Where forms appear
- Participants see their form on their study page and during onboarding (form steps in a flow use profile forms).
- Your team sees records through the same lenses: a record’s Data tab offers the form view alongside the full-record editor.