The form builder

Forms decide what people see when they create, edit or view a record. The form builder in Admin → Forms is a generic layout designer: one form can span sections, tabs and columns, mix editable and read-only fields, show related records, compute values live, and hide parts of itself until they’re relevant. The same forms also power your portals — design once, use everywhere.

Building a form

1. Open Admin → Forms and click + New form, then pick the record type it’s about.
2. Add layout containers — sections (with 1–2 columns) and tabs — and drag items into them.
3. Add items: fields, text blocks, related-record lists, calculated values, action buttons.
4. Save, then assign the form to a screen (below).

What you can place on a form

• Fields — any field of the type. Per item, choose:
  • Read or edit — the same form can show some fields read-only.
  • Required — required-ness lives on the form, so Create can demand fields that Edit doesn’t.
  • Validation — an extra rule the value must pass before saving.
• Text blocks — headings, instructions, explanations between fields.
• Related-record lists — a table of connected records (a person’s payments, an event’s registrations), resolved through your reference fields and relationships.
• Related fields — a single field from a 1-to-1 related record, shown inline.
• Calculated values — an expression over the form’s fields, recomputed live as the user types.
• Workflow items — the state pill and transition buttons, placed exactly where you want them.
• Action buttons — save, cancel, delete, or a specific workflow transition.

Conditional visibility

Any item or section can carry a visibility condition — an expression over the form’s values. The membership section appears only when type = member; the rejection reason only when status = rejected. Visibility updates live while editing, keeping forms short and relevant.

Assigning forms to screens

Forms are assigned on the record type, not the other way round:

1. Open Admin → Entity types, pick the type, and open its Forms section.
2. Choose a form for each screen — Create, Edit and View.

Use a minimal form for Create (fast entry), a full one for Edit, and a read-oriented one — with related lists and calculated summaries — for View. A screen with no assigned form falls back to a simple all-fields layout, so nothing ever breaks while you design.

One form, many places

Because forms are just configuration, the same form can serve:

• The app’s Create / Edit / View screens.
• A transition screen — the fields collected before a workflow step completes.
• A portal page — the exact layout an external person sees and fills in, with the same required fields and validation.

Change the form once and every surface follows.