Publishing a form

Publishing is the step that makes your work live. Until you publish, respondents see nothing you have changed.

Publishing snapshots the current draft into an immutable version that respondents see. Your draft keeps evolving independently until you publish again.

The first time you publish a form

A form’s first publish is one screen. It leads with the version number, the field count, and what publishing will do: make this the version respondents answer, and turn the form on. Below that, a checklist of anything worth settling first, then the form’s settings as collapsible rows, each stating its current value on the right:

Row	What it covers	Reads, for example
Object model	Record types, the primary object, and the record link choices	Contact primary
After someone submits	The message or redirect a respondent gets	Generic message, Custom message
When responses are accepted	The schedule and any response cap	Always open
Who can reach it	The Share URL, the Sliick Edge consent tick, and the two allowlists	Not served publicly
Notifications and integrations	The notification addresses and the webhook	1 recipient

Object model appears only on a form that maps at least one object, so a form with nothing mapped shows the other four.

The point of the current values is that an author who opens nothing has still read what publishing will do. Open a row to change it. The buttons are Keep editing and Publish, and clicking straight through writes nothing you did not touch. A closing line says you can change any of it later in Form settings, with no republish needed.

Republishing is unchanged: the compact dialog below, with Review setup first to reveal those same rows inline.

Publish

1. Click Publish in the top bar.
2. On a republish, if there are things worth knowing first, a Before you publish dialog lists them, under the heading Nothing here blocks publishing: these are things respondents or your team will notice. Typical warnings: a required choice field with no option source, a mapped File Upload, and fields left unmapped. The buttons are Keep editing, which writes nothing and publishes nothing, and the confirm button, which reads Publish anyway when warnings are listed and Publish when the dialog is only the Sliick Edge question. Declining is not remembered: the next publish asks again, showing whatever is stored at that point. On an org with no Sliick Edge connection, a clean form publishes with no dialog at all.
3. On success you get a short confirmation: Published, This version is live, with a single Done button. It shows the link that resolved for this form, if one did, with Copy link. It never composes a link where none resolved, because where a form can be reached has more than one answer. That lives in the Share tab.

On an org connected to Sliick Edge, the Before you publish dialog opens on every publish, because it also carries the Allow on your public Sliick Edge address tick. It is an offer, not a warning: it never blocks publishing and never appears in the warnings list. Ticking or unticking it there saves before the publish runs, so the public address is refreshed against the version you just published.

Check that tick on a form’s first publish. Connecting Sliick Edge is your org saying how it serves forms, so a form that has never been published arrives with the box already on, under Who can reach it. Every later publish shows it as you last left it, so unticking a form is never undone for you. Untick it on a form that should exist only on an internal or Experience Cloud page.

A permission set that stops you editing one setting no longer decides this for you. The consent tick stays readable and editable even where a neighbouring setting is locked, so you can untick it and publish. Only the locked setting itself is withheld.

What hard-blocks a publish

These cannot be overridden:

Block	How to clear it
A running experiment	End it first. See Versions and A/B experiments
Visibility logic that cannot settle	Find it in the Logic Map
An unresolved required record type	Choose it in Record types
An unanswered record link choice	Choose it in The form’s object model
Two fields sharing an API name	Rename one. The message names the duplicated name and every field carrying it
Two fields answering the same link parameter, or a parameter name the renderers already use	Change one of them. See Sharing a form
A person-account form mapping person fields to a business account record type	Choose Person Account in Settings, or map those questions elsewhere. See Person accounts

Publishing and intake

Publishing a form that is paused turns intake on. If a form has never been published and is not currently accepting responses, its first publish also starts it accepting, and the confirmation says so.

Republishing never re-opens a form you deliberately closed, and restoring an old version never re-opens one either.

How the change reaches respondents

On an Experience Cloud placement, respondents see the change immediately, because that reads the org directly.

On a public Sliick Edge address, publishing tells that address to re-fetch the form, so the new version reaches respondents on their next visit.

If a change is not showing up on a public link, publish again rather than waiting. If a refresh fails, the public address keeps serving the version it already has until your next successful publish. The Delivery panel’s Edge cache refresh row reports whether the refresh landed.