Publishing a form
Publishing makes your work live. Until you publish, respondents see none of your changes.
Each publish saves a fixed copy of your draft as a new version, and that version is what respondents see. You can keep editing the draft afterwards without changing the live form, until you publish again.
The first time you publish a form
Section titled “The first time you publish a form”A form’s first publish opens one screen. At the top it shows the version number, the number of fields, and what publishing will do: make this the version respondents answer, and turn the form on. Below that is a checklist of anything worth sorting out first. Then come the form’s settings as rows you can expand, each showing its current value on the right:
| Row | What it covers | Example value |
|---|---|---|
| Object model | Record types, the main 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 tick, and the two allowlists | Not served publicly |
| Notifications & integrations | The notification addresses and the webhook | 1 recipient |
Object model only appears if the form maps at least one object. Otherwise you see the other four rows.

You can read what publishing will do without opening anything. Open a row only if you want to change it. The buttons are Keep editing and Publish. Clicking straight through changes nothing you did not touch. You can change any of these later in Form settings, without publishing again.
Publish
Section titled “Publish”-
Click Publish in the top bar.
-
If there is something worth knowing first, a Before you publish dialog lists it, under the heading Nothing here blocks publishing: these are things respondents or your team will notice. Typical warnings: a required choice field with no options, a mapped File Upload field, and fields that are not mapped. Choose:
- Keep editing: go back. Nothing is saved or published.
- Publish anyway (shown when there are warnings) or Publish: go ahead.
The dialog does not remember your answer. It asks again next time. To see the setting rows on a later publish, click Review setup first. On an org without Sliick Edge, a form with no warnings publishes with no dialog at all.
-
When it works, you see Published, This version is live, and a Done button. If the form has a link, it is shown with Copy link. If it has no link yet, none is shown: go to the Share tab to see where the form can be reached.
If your org is connected to Sliick Edge, the Before you publish dialog opens on every publish. It carries the Allow on your public Sliick Edge address tick. This is a choice, not a warning: it never blocks publishing. If you change the tick there, it is saved before the publish runs, so your public address gets the version you just published.
Check that tick on a form’s first publish. Connecting Sliick Edge says how your org serves forms, so on a form’s first publish the box is already ticked, under Who can reach it. Untick it if the form should only be on an internal or Experience Cloud page. On every later publish, the box shows what you last chose, so unticking a form is never undone for you.
A locked setting does not stop you changing the tick. If your permission set stops you editing another setting in that dialog, you can still see and change the Sliick Edge tick, and publish. Only the locked setting stays locked.
What stops a publish
Section titled “What stops a publish”These have to be fixed before you can publish:
| What stops it | How to fix it |
|---|---|
| An A/B experiment is running | End it first. See Versions and A/B experiments |
| Show/hide logic that can never settle | Find it in the Logic Map |
| A required record type has not been chosen | Choose it in Record types |
| A record link question has not been answered | Answer it in The form’s object model |
| Two fields have the same API name | Rename one. The message names the duplicate and every field using it |
| Two fields take their value from the same link parameter, or a field uses a parameter name the form already uses | Change one of them. See Sharing a form |
| A person account form maps person fields to a business account record type | Choose Person Account in Settings, or map those questions somewhere else. See Person accounts |
Publishing and accepting responses
Section titled “Publishing and accepting responses”A form’s first publish turns it on. If a form has never been published and is not accepting responses, publishing it also starts accepting responses. The confirmation says so.
Publishing again never re-opens a form you closed on purpose. Restoring an old version never re-opens it either.
How the change reaches respondents
Section titled “How the change reaches respondents”On Experience Cloud, respondents see the new version straight away.
On your Sliick Edge address, publishing tells Sliick Edge to fetch the new version, so respondents see it on their next visit.
If a change does not show up on a public link, publish again rather than waiting. If the update fails, your public address keeps showing the previous version until your next successful publish. The Edge cache refresh row on the Delivery panel shows whether the update arrived.