Forms, publish, and versions

What is Forms, publish, and versions?

Every Formit form lives in a workspace. You build and iterate in the editor, then publish to create a versioned live form. Respondents always answer against a specific published version, so historical submissions stay aligned with the questions they actually saw.

How it works

1. Open a workspace and create a new form (blank, template, or AI-generated draft).
2. Add and configure blocks in the form builder until the flow is ready.
3. Preview the form to confirm layout, logic, and endings.
4. Publish to create a new version and make the form available via public link or embed.
5. Share the link or embed code; submissions attach to that published version.
6. Edit again when needed, then republish so new respondents get the updated version while past answers stay on their original version.

Key capabilities

• Workspace-scoped forms

  Forms belong to a workspace, so access, branding, and results stay within that team context.

• Versioned publish

  Each publish creates a version snapshot. Live respondents use the current published version.

• Version-bound submissions

  Answers are stored against the version the respondent filled, which preserves historical accuracy when the form changes.

• Iterate without data loss

  You can keep editing drafts and republishing without overwriting past submission structure.

Benefits

• Safe iteration: change questions without corrupting older response sets.
• Clear ownership: forms sit in the workspace your team already uses.
• Reliable sharing: publish once, then distribute the same public URL or embed across channels.
• Audit-friendly history: each live release is a distinct version respondents actually used.

Use cases

• Shipping a lead form that will evolve as marketing copy and fields change.
• Running applications or intake forms where past submissions must remain comparable to their original questions.
• Maintaining production surveys while a new draft is still being reviewed.

Example workflow

A product team builds an onboarding survey in their Growth workspace, previews the flow, and publishes. After a week they add a new satisfaction scale and republish. New respondents see the updated form; earlier submissions remain tied to the first published version, so results still make sense when filtered by version.

Tips and best practices

• Publish only when the form is ready for respondents - draft edits do not change the live version until you publish again.
• Name forms clearly inside the workspace so teammates can find the right production form.
• After structural changes (new required fields, logic, endings), preview and publish before promoting the link again.

Limitations and plan notes

• Respondents only see published versions; unpublished draft changes are not live.
• Submission structure follows the version filled - comparing across heavily redesigned versions may require care.
• Form access and collaboration still respect workspace roles and plan seat limits.

Frequently asked questions

Does editing a form immediately change what respondents see?

No. Respondents see the last published version. You must publish again for live changes to take effect.

Are submissions tied to a specific version?

Yes. Each submission is bound to the published version the respondent used when they filled the form.

Where do forms live?

Forms are workspace-scoped. Create and manage them inside the workspace that owns the project.