Forms overview
Understand how Forms separates form authoring, sharing, and response administration from the public responder journey.
Forms is the organization workspace for building questionnaires and reviewing submitted answers. A form contains ordered sections, questions, response settings, and a live preview that uses the same renderer as the respondent page.
The signed-in Forms workspace covers administration. Filling a public or recipient-specific form is a separate customer journey with its own access rules.
What you can manage
| Area | What it does |
|---|---|
| Forms | Search, filter, and sort the organization’s live forms. The list shows Title, Status, Responses, Belongs to, and Last edited. |
| Builder | Edit Basics, Settings, sections, questions, choices, conditional visibility, and supported question-specific options. |
| Preview | Open the real response renderer without creating or recording a response. |
| Share | Copy the open-response URL or QR code for a published, standalone form. |
| Responses | Compare a per-question Summary, inspect Individual submissions, download uploaded answers, or export CSV. |
Forms can include short or long text, single or multiple choice, dropdown, rating, yes/no, number, date, and file-upload questions.
Administrative lifecycle
- Draft is editable and can be previewed, but it has no working share link.
- Published accepts responses and exposes Share.
- Closed no longer accepts responses, while collected responses remain available to authorized administrators.
- Archived remains a recorded catalog state and does not represent an active collection surface.
An event-owned form appears in Forms for administration, but its entry point belongs to Events. It therefore does not receive the generic Forms share link.
Access boundary
An authenticated organization member can reach the Forms list. Creating, editing, previewing, publishing, revealing a share link, reading responses, downloading answer files, and exporting CSV require the organization’s form-management permission, which is assigned to organization admins.
Responder URLs must be treated as access-bearing links. Do not paste them into documentation, tickets, or screenshots.