Build, publish, and share a form

A form belongs to the selected Personal or team context. On Forms, choose Create form, then choose a blank, contact, feedback or registration starting point. Forms offer built-in starting points. Choosing one copies its questions into the new form; it does not change how the finished form works.

In the native app, Form editors can publish a draft or close a published Form from the Form action menu. They can also open Settings to change Require sign-in, One response per person, and Email me for new responses; these settings save immediately. Edit questions lets native Form editors change the title, page titles, supported question types, labels, descriptions, required state and choice options, and add or remove questions. It supports every question type and content block the website editor offers. These saves keep the existing draft version check. Payment lets native Form editors require payment, set the amount and choose the currency. Payment saves also use the draft version check. Appearance can also be changed from the native Form action menu; the available public themes and descriptions are the same catalog used by the website. Collaborators can be added, updated or removed from the native Form action menu; team members already have access through the workspace. Native Form editors can delete a Form from the Form action menu after confirming; the Form and responses are removed while payment records are retained.

Native Edit questions also supports adding, removing and reordering pages, moving questions and content, and adding or editing headings, supporting text and dividers. It also supports conditional visibility with equals, not equals, contains, answered and not answered rules.

The native editor also accepts an introduction, completion heading and completion message. Each is bounded and saved with the same draft version check. The completion copy is shown after a response is accepted.

The editor saves the working draft as you type. Edit the title and introduction from the page bar. Use the page rail to choose, reorder or add pages. Add questions to the selected page; Add content adds headings and supporting text. Move questions with the Move up and Move down buttons. A new page gives the respondent a Next and Back sequence instead of showing the whole form at once. Add at least one question before publishing.

Question types cover short and long text, email, phone, URL, number, single and multiple choice, yes or no, date, time, rating, and file upload. Mark a question required when an empty answer should block submission. For radio buttons, checkboxes, and selects, enter one choice per line.

Conditional visibility shows a question only when another question equals the value you enter. A hidden question is not required and its answer is not stored. If you remove a question used by a condition, update that condition before publishing; publication stops rather than leaving a rule that points to a missing question.

Publish and close

Publish copies the current draft into a fixed Form version and opens its public address. Later edits remain a draft until you choose Publish changes. Existing responses stay attached to the version each respondent saw, so a question edit does not rewrite an earlier response.

The public address is generated when the Form is created. Anyone with that link can open a published Form unless Require sign-in is on. Treat a public link as public access, not as a password. Close stops new responses without deleting the Form, its versions, or responses.

The Forms list shows views of each published Form. Visits by the person who created the Form are not included; visits by other people, including anonymous visitors, are counted.

A Magpie link sits under the Form on its public page: the Magpie name and a line offering the reader their own Form. It is shown on every Form on the free plan. On a paid plan, turn Magpie link off in Form settings to remove it from that Form; the preview shows the result before you publish. Removing it is per Form, so other Forms keep the link until you turn each one off. If a paid plan ends, the link comes back on Forms it was removed from.

Access and collaborators

Form settings contains access, payment, collaborators and publication controls. Require sign-in limits submission to Magpie users. One response per user uses that signed-in identity to reject a second response; it cannot reliably limit anonymous visitors, so require sign-in before using it. Email me for new responses is on by default and sends the Form's creator an email with a link to each new response as it arrives; turn it off from Form settings if you'd rather check the Responses page yourself.

Team access still follows the selected team's permissions. A direct collaborator receives access to this Form without joining the team. Can view allows the Form and its responses to be read. Can edit also allows changes, publication, closing, collaborator management, and response actions. Send a direct collaborator the editor address because the Form does not appear in a team they have not joined.

If a saved edit is missing after reloading, or publication reports a condition you cannot identify, Contact support.