Skip to content

Publish, submit, and recover

Releasing a form is three decisions in sequence: who should be able to reach it, what happens after someone submits, and which saved version goes out. Take them in that order and publishing itself is straightforward. The last section covers the step authors skip most often, which is proving that a failed submission leaves the respondent’s answers intact.

Open Internal & external publishing.

Annotated publishing settings with internal, external, access, and release controls

  • Enable Internal Publishing (for Pages) for the authenticated Lunar Paper copy.
  • Select an approved external publisher only when anonymous delivery is required.
  • Use Manage Internal access to confirm the signed-in audience.

Open Submission actions. Actions run in order only after the response is stored successfully.

Ordered completion-page and submit-another-response actions

Use a Show completion page action when you need custom confirmation content. Add Show submit-another-response button for shared devices or repeated intake. The submission-complete page is read-only after submission and is excluded from stored answers.

Choose Publish, select the destination, and add an optional version-history note.

Publishing locations and release note

Confirm the publish. The toolbar displays View Published Form when the Internal Publisher succeeds.

Builder toolbar after the form is published

Publishing releases the saved version. If the draft shows unsaved changes, save and re-open Preview before publishing.

Open View Published Form and complete the response as a respondent would.

Published form with three steps and contact fields

Test error recovery:

  1. submit or move next with required answers missing;
  2. confirm each message identifies the field and corrective action;
  3. enter an invalid format and correct it;
  4. cancel a file picker;
  5. clear and re-enter a signature;
  6. confirm previous-page answers remain intact.

On the final page, review consent and signature controls before submitting.

Published consent page with rich text, consent checkboxes, and typed signature

After successful storage, the renderer replaces the form with the configured completion page and then exposes later actions.

Completion page and submit-another-response button

If storage fails, the respondent must stay on the form with their answers intact and an error they can recover from. A completion page must never suggest success before the response is stored.

Choose Submit another response and confirm the first response remains stored while the new form starts with cleared respondent answers.

The responses themselves are covered in Review submissions and analytics. For why anonymous delivery is a separate publisher rather than a setting, see Publishing, access, and security.