For new intake experiences, open Apps and start with Form. A form is a one-page app; add pages when the questions need more room. Public participants can submit without joining your workspace. Their final submission creates records through the fields and actions you explicitly publish.
Make the questions easy to answer#
- Choose the sheet, then select the exact fields the app may write. Give each question a clear label and useful help text.
- Arrange sections and inputs, set required answers, and use conditional visibility when later questions depend on earlier answers.
- Add progress and a validation summary for longer forms. Hidden answers are cleared and server validation checks the conditions again.
- If a relationship is needed, choose an explicit public choice list. Public record pickers do not expose general sheet search.
- Use file inputs when people need to provide an attachment. Check file, count, and size restrictions in the input setup.
- Preview with fictional answers, including missing information and the expected success state. Preview does not submit records or run a real Flow.
Publish and share#
- A workspace manager reviews the data bindings, access policy, and any connected published Flow, then publishes a release.
- Copy the hosted app link. Test the participant experience with a clearly marked example and verify the resulting record.
- For embedding, approve the exact HTTPS site origin and use the app’s embed setup.
- Pause the app to stop entry and further actions. Existing records and completed history remain saved.
Public apps create records only at final submission. Back and Next retain draft answers; all pages and bindings validate and commit together. Anonymous participants cannot update existing records or open anonymous business-process tasks. Use an invited app participant for continuing access, updates, or reviews.
Let someone return later#
A public participant can explicitly save progress and copy a private return link. Draft answers remain on the server for seven days; answers and credentials are not stored in browser storage. The return link rotates when opened. Keep it private, and use the interface to clear this device or delete the saved draft when finished.
Fifteen minutes of inactivity clears the local session. A failed final validation keeps the draft for correction. An accepted response deletes the saved copy; a cleanup problem is reported rather than silently claimed as complete.
Keep submitted files scoped#
Uploads use private storage and are bound to the app release, participant, input, and field. Checks and quotas run before a file becomes usable. Download access is rechecked against current record and field scope. A different participant cannot claim a pending upload. Content inspection is not an antivirus guarantee.
Continue work after the response#
A public submission may start a configured background Flow. The records, receipt, and exact Flow run commit together. The receipt confirms intake and shows follow-up as pending; it does not promise that a later approval, integration, or notification has finished. Inspect the run for its actual outcome.
Existing sheet rules also apply. If a rule requires a value the form does not collect, adjust the form or rule before publishing. Retry the same submission through its existing attempt instead of starting multiple new attempts; accepted submissions have duplicate protection.
Keep an existing sheet Form working#
Existing Form views retain their original submission route and sharing controls. Their input limitations remain those of the legacy form, including no file inputs or general relationship pickers. Apps provides a compatibility report and explicit migration to a draft, preserving supported field IDs, original URLs, capability tokens, and submission identities.
Review and explicitly publish a compatible release before activating the migrated form. Migration does not publish an unpublished form. Unsupported definitions stay on their original path with a report; rollback returns to the retained legacy definition. Keep the full legacy link, including its token fragment, when sharing it.