Client form block

Who can use it. Staff add and configure a form in the portal template or a project's portal (where this feature is turned on for your account). Any customer with portal access can fill it in, submit it, and come back later to update their answers.

What it's for

Sometimes a quick decision, checklist, or single question block isn't enough — you want to ask a client a short set of questions all at once and get one clean set of answers back, like a "tell us about your kitchen" intake form before a design meeting, or a short pre-start questionnaire. The form block lets you build exactly that: a small, ordered list of fields the client fills out and sends in one go.

How to use it

1. Open a portal template (or a project's own portal) in the editor and add a Form block, wherever you'd add a Question or Checklist.
2. Give it a title, an optional description, and add fields one at a time. Each field has:

- A label — the question or prompt the client sees. - A type — short text, long text (a bigger box for a longer answer), single choice (the client picks one option from a list you set), date, or yes/no. - A required toggle — turn this on for anything the client must answer before they can submit. - For single choice fields, the list of options they can pick from.

1. Reorder fields with the up/down arrows next to each one, and remove any you don't need.
2. Set the submit button label if you want something other than "Submit" (e.g. "Send my answers").
3. Turn on "Notify staff by email when a customer submits this" if you want your team emailed the moment a client sends the form in — the same notify toggle every other client-answerable block has, where this is enabled for your account.
4. Publish (or save the project's own portal) — the client now sees the form on their portal page.

What it affects

• The client sees the form on their portal page, fills in the fields, and taps the submit button. Required fields must be filled in (and a single-choice field must be one of your listed options) before the submit goes through — a client sees an inline note next to anything still missing.
• Once submitted, the client's answers stay visible in the same fields, the button changes to "Update response," and a small "Submitted [date]" note appears — so they can come back any time and change their answers; the latest submission is what's kept.
• Staff see the submitted answers on the project's portal page, listed as "field label: answer" for every field you configured (an unanswered field shows a dash), right alongside every other block's answers.
• If you turned on the notify toggle, your team gets an email when the client submits (or updates) their answers, same as a notify button tap or any other block with that toggle on.

Good to know

• A form you've just added with no fields yet doesn't show up on the client's live portal at all — it only appears once you've added at least one field, so an unfinished form is never accidentally shown half-built.
• There's no file-upload field yet — stick to a document slot block if you need the client to upload something.
• A form doesn't support branching logic or multiple pages — it's one flat list of fields, submitted together.
• This is a newer addition and may not be turned on for every account yet — if you don't see Form in your block list, it isn't available for your business yet.