Getting started
Documentation
Which part do I need?
Most of the platform is one of three things, and knowing which one your problem is saves a lot of reading.
A form is a single questionnaire with a public link. Someone opens it, fills it in, and their answers become a response. That is the right tool for a survey, an intake form, a registration, a feedback request.
A data appis several forms bound to the same subject and filled as one session — a monitoring visit that records the school, the training given and the observations made, all against that school's record. Reach for it when the same thing is measured repeatedly over time and you need the history in one place.
An option list is reference data that dropdowns draw from — states, districts, schools, cost centres. Upload it once and every question bound to it stays in step, instead of the same list being retyped into thirty forms.
Getting started
What the platform is, and how to get a working form in front of people.
Building forms
Everything in the form builder, from a single field to a rule engine.
The builder
The canvas, the outline, the panels, and how autosave works.
Field types
Every question type, what it stores, and when to reach for it.
Pages and layout
Multi-page forms, and the stacked, conversational and grid layouts.
Conditional logic
Show and hide questions based on what someone has already answered.
Rules and calculations
Calculated fields, conditional requiredness, and validation that spans questions.
Form settings
The public link, access control, response caps, expiry and notifications.
Theme and branding
Colours, typography, logo and cover image.
Option lists
Reference data your dropdowns draw from, managed in one place.
Publishing and responses
Getting a form in front of people, and working with what comes back.
Data apps
A guided, multi-form surface for collecting data about the same subject over time.
What a data app is
When to build an app instead of a form, and what it gives you.
Record types
Defining the subject an app collects data about, and its identity.
Steps
Ordering forms, repeating them, and making them conditional.
Records and timeline
Reading everything collected about one subject in one place.
App appearance
Paging steps, page width, headers, spacing, and why field widths need the right layout.
Administration
People, permissions, and the platform itself.