Public forms on Experience Cloud
Sliick Forms includes a component, Sliick Experience Form, that shows a form on a page of your Salesforce Experience Cloud site. The form is hosted on your own Experience site, not on Sliick Edge. Use this option for a form behind a portal login. It is also one of the options for a public form.

Place the component
Section titled “Place the component”- Open Experience Builder for your site.
- Go to the page where the form should appear.
- Drag Sliick Experience Form from the components list onto the page.
- Set Form ID to the form’s Form ID, from Form settings, Details.
- If you like, set Submit Button Label and Success Message. From 1.2, Source Channel is no longer used: a rule that tests the channel always reads
experienceon an Experience Cloud page. - Publish the site.
One page can serve every form
Section titled “One page can serve every form”Leave Form ID blank, and the component reads the form from the page address instead, using ?form=. Then, on the Admin Dashboard’s Delivery panel, set the Experience Cloud address to that page with {form} in place of the form’s ID. For example:
https://<your site>/s/<your page>?form={form}
Every form in the org then gets a working share link, with no extra pages to build. See Choosing how to host a form.
Fill in Form ID when a page should only ever show one form. Leave it blank for the shared page.
Follow the site’s language
Section titled “Follow the site’s language”On a site with more than one language, turn on Follow the site’s language on the component. The form then shows in the visitor’s site language, when the form has that language. A link with ?lang= still wins. With it off, the form follows the visitor’s browser language.
With it on, Submit Button Label and Success Message also show translated text, as long as you left them at their default wording. Text you typed yourself is always shown as typed. See Form settings.
What respondents see (Sliick Forms 0.9.0 and later)
Section titled “What respondents see (Sliick Forms 0.9.0 and later)”- Date and time questions use the respondent’s own time zone, and date limits are checked against the respondent’s own day.
- A number too big for the Salesforce field it maps to is flagged next to the question, before the respondent submits. Publish again any form that maps number, currency or rating questions to number fields to turn this on.
- A multi-select can be filled from a repeated link value, such as
?topics=a&topics=b. - One-tap answers from an email wait for the respondent to press Submit, and a failed save-for-later says so.
- Answers that fail a check are fixed on the page. The respondent sees what is wrong and corrects it. These responses are not kept for review.
The site itself must be public
Section titled “The site itself must be public”An Experience site only shows pages to people who are not logged in once it is both published and open to them. Publishing alone is not enough:
- In Experience Builder, go to Settings, General, and turn on Public Access. With it off, visitors are sent to the login screen or see Page Not Found.
- The site must be Live, not Under Construction. Set this in Administration, Settings, Activate.
- Custom pages are under
/s/, so the address looks likehttps://<domain>/<prefix>/s/<page>.
A public form here needs more than a live site. It also needs a permission set assignment and a sharing rule. Work through Guest access for public forms before you test one.
The hidden field on public forms
Section titled “The hidden field on public forms”Public forms include a hidden field that people never see. Automated programs that fill in every box on a page fill this one in too. A submission with it filled in is quietly dropped: the sender sees a normal confirmation, and nothing is saved. There is nothing to set up.
This stops simple spam bots without getting in the way of real people. It is not a full spam filter, and it will not stop a program written to target your form. Sliick Forms does not limit how often someone can submit, so a form that attracts a lot of automated traffic needs protection in front of it, such as Sliick Edge.
A form on your Sliick Edge address has this same hidden field, plus a Cloudflare Turnstile check on every submission. See Bot protection is automatic.