Choosing how to host a form
Before you share a form, decide where people will open it. There are three options. You can use all three in one org, and one form can be reachable in more than one way.
Compare the three
Section titled “Compare the three”| Sliick Edge (Edge tab) | Experience Cloud | Custom (own Share URL) | |
|---|---|---|---|
| What it is | Sliick hosts your public forms at an address of your own, such as https://acme.sliick.net | The Sliick Experience Form component on a page of your own Experience site | A form you placed somewhere else, at an address only you know |
| Where the form is hosted | On Sliick Edge, outside Salesforce. Answers pass through Sliick Edge on their way to your org | On your Salesforce Experience site | Wherever you put it |
| Needs an Experience site | No | Yes | Depends where you put it |
| Forms behind a login | No. Sliick Edge does not sign anyone in | Yes | Depends where you put it |
| Setup | Connect the org once, then turn on each form | Publish a site, place the component, and set up guest access for public forms | Nothing org-wide. Paste the form’s own Share URL |
| Bot protection | A hidden trap field, plus an automatic Cloudflare Turnstile check | A hidden trap field | A hidden trap field |
| Protection against floods of traffic | Yes. Heavy or automated traffic is filtered before it reaches Salesforce | No. Salesforce serves the page directly | Depends where you put it |
| Embed on your own website | Yes, with a ready-made <iframe> snippet | Not offered | Not offered |
| Counts views and starts for your results | Yes | Not generally available | Not generally available |
Where you host matters for a form that attracts spam. Salesforce’s own limits apply to your whole org, not to one form. A flood of traffic against a form on Experience Cloud uses up your org’s capacity. A form on Sliick Edge is filtered before traffic reaches Salesforce. Sliick Forms itself does not limit how often someone can submit. A response cap is not a spam control either: a spammer who hits the cap closes the form to real respondents.
Rules of thumb:
- A public form, and you would rather not build an Experience site: use Sliick Edge.
- A form behind a portal login: use Experience Cloud. Sliick Edge does not sign anyone in.
- A public form on a page you have already built, or somewhere unusual: give the form its own Share URL (the Custom option).
Set the org-wide addresses
Section titled “Set the org-wide addresses”Open the Delivery panel on the Admin Dashboard. It has three tabs: Edge, Experience Cloud and Custom. Each tab has a status dot, so you can see what is set up without opening it.
Edge (Sliick Edge). Optional. Click Connect, choose an integration user, and keep the suggested address, which is based on your Salesforce My Domain name. Connecting does not publish anything. Each form still needs Allow on your public Sliick Edge address ticked before it is served there. This tab also shows Edge cache refresh, which tells you whether your last publish reached your public forms. Full steps: Hosting on Sliick Edge.
Experience Cloud. The address of the site page that shows your forms, written as a pattern. Click Set address and put {form} where the form’s Form ID goes. One setting then covers every form. For example:
https://acme.my.site.com/s/forms?form={form}
As you type, the panel shows the link one of your own forms would get. If the preview is empty, your forms would get no link either. If you leave out {form}, the form’s Form ID is added to the end after a /. A single trailing slash is removed when you save.

This is the same setting as Setup, Custom Settings, Forms Settings, where the field is labelled Public Site Address.
Custom. For a form on its own page, or anywhere the address does not follow a pattern. There is nothing to set org-wide. Open the form and fill in its own Share URL under Form settings, Availability. The tab shows how many forms have their own link.
When more than one option applies to the same form
Section titled “When more than one option applies to the same form”Sliick Forms picks the share link in this order and stops at the first one it finds:
- The form’s own Share URL.
- Your Sliick Edge address, if the form is allowed on it. From 1.2 the link ends in the form’s own Sliick Edge address when it has one.
- The Experience Cloud address pattern.
See Sharing a form.