Building forms

Form settings

Who can respond, how many times, until when, and where the form lives. All of it is enforced when a response is submitted, not merely hidden in the interface.

Access

SettingEffect
Require sign-inOnly signed-in users may submit. The form says so up front rather than letting someone fill twenty questions and then bounce off a refusal.
Password protectionA password is required before the form can be submitted. The flag only takes effect once a password has actually been set — otherwise the form would demand one nothing could satisfy.
Allow multiple responsesOff means one response per respondent, checked against sign-in where available and a device fingerprint otherwise.

Limits

SettingEffect
Response capAfter this many responses the form closes itself and says so. Useful for limited places on a course or a workshop.
Expiry dateAfter this moment the form stops accepting responses and tells visitors it has closed, rather than 404-ing as though the link were wrong.

Both produce a “no longer accepting responses” message rather than a missing page. Someone who arrives late had the right link; telling them otherwise sends them off to ask for it again.

Notifications

Add email addresses to be notified when a response arrives. Each is sent a summary, not the full response — an inbox is the wrong place for collected data, and forwarding one email should not forward someone's answers.

Status

A form is always in exactly one of four states:

StatusMeaning
DraftNever published. The public link shows nothing.
PublishedLive and accepting responses.
ClosedWas live; reached its cap or expiry, or was closed by hand. Visitors are told it has closed.
ArchivedRetired. Responses are kept and remain exportable.

Deleting a form is a soft delete: it moves to Trash, where it can be restored. Responses survive the whole time.