Portal Forms
Field types in the form builder
Quick answer: Every form is built from a stack of fields — text inputs, date pickers, dropdowns, signatures, file uploads, and display-only blocks. This article lists every type and when to use each.
Display-only blocks
These don't collect data — they structure the form so parents can navigate it.
| Block | What it does | Use it when |
|---|---|---|
Header | A large title that breaks the form into sections. | Long forms with multiple parts. |
Paragraph | Plain explanatory text. Can be styled as a note or warning. | Anywhere you need to explain a policy, give instructions, or call attention to something. |
Section | A smaller divider with an optional sub-description. | To group two or three related fields under a heading like "Person 1". |
Text-style inputs
| Field | What it accepts | Common use |
|---|---|---|
text | A single line of plain text. | Name, relationship, free-form short answer. |
email | Validates as an email address. | Emergency contact email, alternate parent email. |
tel | Validates as a phone number. | Phone numbers (any format). |
url | Validates as a web URL. | Rare — link to an external document. |
textarea | Multi-line text, up to several paragraphs. | Allergies, special instructions, notes to the school. |
Numeric and date inputs
| Field | What it accepts | Common use |
|---|---|---|
number | Numeric only, with optional min/max. | Age in years, grade level, weight, dosage. |
date | A calendar date picker. | Date of birth, signature date, trip date. |
Choice inputs
| Field | What it accepts | Common use |
|---|---|---|
select | One choice from a dropdown. | Grade level, relationship type, T-shirt size. |
radio | One choice, shown as a list of buttons. | Yes/No, opt in/out, short choice lists. |
checkbox | A single yes/no acknowledgement. | "I have read and agree to the handbook." |
multi_checkbox | Multiple selections from a list. | Languages spoken at home, list of allergies to choose from. |
Signatures
| Field | What it accepts | Common use |
|---|---|---|
signature_drawn | A signature drawn with mouse or finger. | Forms where a signature visual is required (most permission slips). |
signature_typed | The parent's full legal name, typed, with an acknowledgement statement above it. | Acknowledgements, low-risk forms, situations where a typed legal name is sufficient. |
File uploads
| Field | What it accepts | Common use |
|---|---|---|
file_upload | PDF, JPG, PNG, HEIC. Max ~10MB per file. Can be configured for single or multiple files. | Immunization records, custody papers, insurance card images. |
Field-level options
Every input field has these common settings:
- Label. What the parent sees as the question.
- Required. Whether the parent must fill it in. Required fields show a red asterisk.
- Help text. A short sub-line under the question to explain what you want.
- Pre-fill. An optional source (parent name, student name, today's date) that auto-fills the field.
- Width. Whether the field takes the full row, half, or a third — used for compact two-column layouts.
What you get back
Every submission stores its data as a single record on the parent's family. Each field becomes a key/value pair you can see in:
- The Portal Forms Inbox widget on your admin dashboard
- The submission's printable PDF view
- The parent's record in Growth Suite (if the form has writeback configured)
Related articles
- Pre-filling parent and student data
- Signatures: typed vs drawn
- Connecting form data back to Growth Suite
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article