Skip to content

Hosting on Sliick Edge

Sliick Edge is Sliick’s hosting for public forms. Connect your org once and you get a public address of your own, such as https://acme.sliick.net. You do not need an Experience Cloud site.

Sliick Edge sits alongside Experience Cloud rather than replacing it. A form behind a portal login still needs Experience Cloud, because Sliick Edge does not sign anyone in.

Sliick Edge runs outside Salesforce, on Cloudflare. In plain terms:

  • Your published form is copied to Sliick Edge, so it loads quickly for respondents. That copy is the form itself (questions, design, settings), not anyone’s answers.
  • Answers pass through Sliick Edge on their way to your org. That includes uploaded files and save-and-continue saves. Sliick Edge checks each submission, then passes it on. If your org cannot accept it straight away, Sliick Edge holds it for a short time and tries again.
  • Responses are stored in your org. Once a submission arrives, it is handled exactly like one from any other placement: it is held for review first, and you work it from the responses console.
  • Sliick Edge counts form views and starts, so your results can show how many people opened a form and how many began it.

Connecting is a one-time job for a Salesforce admin. There are four steps. The first three happen in Setup. Each one is a common place for a connection to fail, so do them in order.

1. Create a dedicated integration user. In Setup, go to Users, New User, and use the Minimum Access - Salesforce profile. Give it a mailbox nobody reads and a name that says what it is, such as forms-integration@yourcompany.com.

Sliick Edge signs in as this user. If you use a real person’s login instead, the connection breaks when that person leaves, changes their password, or is deactivated. It would also be able to reach everything that person can see.

2. Assign the Sliick Forms Integration permission set to that user. In Setup, go to Permission Sets, Sliick Forms Integration, Manage Assignments. Assign the packaged set itself. Do not clone it. Upgrades update the packaged set, but cannot update your copy, so a clone falls behind and the connection fails later. This permission set does not give access to responses. It also does not give the user API Enabled, which a packaged permission set cannot deliver. Grant that yourself, through a permission set you created or the user’s profile. The Minimum Access - API Only Integrations profile already has it. Without it, the connection is refused.

3. Pre-authorise that user on the packaged integration app. In Setup, open the packaged app named Sliick Forms Integration, open its Policies, and click Edit:

There is no sign-in flow to turn on. The flow Sliick Edge uses comes with the package and cannot be changed in your org. Sliick Edge signs in as the integration username you enter in step 4.

This step cannot come with the package, because it names a user that only exists in your org. Until you change it, the app does not let the integration user sign in, so connecting fails. If the connection is refused, the message names this screen.

4. Connect. On the Admin Dashboard, open the Delivery panel, open the Edge tab, and click Connect.

  • Integration username: the user from step 1. If you have not created one yet, the panel offers your own login as a shortcut so you can finish now. Swap in a dedicated user afterwards: the shortcut stops working the day your own account is deactivated.
  • Preferred address (optional): already filled in with your Salesforce My Domain name, which is always available. Keep it unless you want a different one. If a name you type is taken, you see a short message and two or three alternatives. Nothing is created on a refused request, so you can pick another and connect again.

Your address appears in the panel once it is ready. This can take a moment. Click Check again to look again.

Sliick Edge is updated regularly and works best with the latest version of Sliick Forms. On an older version, some hosted-form features may not work as expected. Please upgrade to the latest release from AppExchange. See Upgrading the package.

Disconnecting releases your address and removes the stored sign-in details. Your address is never given to another company afterwards, so old links and printed QR codes can never open someone else’s forms.

A refreshed sandbox has to connect again. A refreshed sandbox is a new org, and it may carry production’s connection details with it. Sliick Forms notices, refuses to use them, clears them, and offers Connect again. A sandbox can never serve forms as if it were production. You do not need to remember this: you will simply be asked to connect.

Connecting the org does not make any form public. Each form needs Allow on your public Sliick Edge address ticked. You can tick it in two places:

  • Form settings, Availability.
  • The Before you publish dialog, which shows it on every publish once your org is connected.

The line under the tick shows the exact address the form will get, so you know what you are agreeing to. See Each form’s Sliick Edge address.

  • New forms start with it off. But on a form’s first publish, the Before you publish dialog shows the box already ticked, because connecting Sliick Edge says how your org serves forms. Untick it there if the form should not be public. After the first publish, the box always shows what you last chose.
  • Copies and imports start off. A duplicated form is off, even if the original was on. A form imported from a blueprint is off, and re-importing over an existing form never changes this setting.
  • Turning it off works straight away. The public address stops serving that form, and any link or printed QR code for it stops working. The address then answers as if the form does not exist, rather than saying it is closed.
  • You can check that a publish arrived. The Edge cache refresh row on the Delivery panel’s Edge tab shows whether your public forms picked up your last publish. It only reports refreshes made since your current connection was set up.

From version 1.2, each form can have its own Sliick Edge address: the last part of its link, such as contact-form in https://acme.sliick.net/contact-form.

  • New forms get one suggested from their name, in the Name your form step of New Form. A duplicated form gets one suggested from its new name. See Create a form.
  • Change it in Form settings, in the Sliick Edge address box under the form’s name. It is checked as you type, and saved when you click Save Settings.
  • The rules: 3 to 63 lowercase letters, numbers and single hyphens, starting and ending with a letter or number. Each address belongs to one form. A few words are reserved for Sliick Edge itself, such as api, admin and embed.
  • Changing an address people can already open asks first. The dialog shows the new and old address and lists what stops working, including links and QR codes you shared with the old address. Another form may then take the old address. The form’s permanent link, built from its Form ID, keeps working, and so do save-and-continue links, Experience Cloud links, record links and embeds.
  • The share link uses it. For a form allowed on your Sliick Edge address, the link on the dashboard and in the builder’s Share tab and QR code uses the Sliick Edge address. A form with no address uses its Form ID, as before.
  • Forms created before 1.2 have no address until you set one, so their links do not change.

The box only appears once your org is connected to Sliick Edge. If it says your permission set has no edit access, ask your admin for Read and Edit on the Form Definition field Sliick Edge Address. The packaged Sliick Forms Admin set already has it.

Every submission through your Sliick Edge address goes through a Cloudflare Turnstile check before it is accepted. This is on top of the hidden trap field that protects public forms everywhere.

There is nothing to set up. If the check itself cannot be completed, the submission is refused rather than let through.

Once a form is ready to embed, its Share tab offers a ready-made <iframe> snippet. If it is not ready yet, the tab tells you exactly what is missing: the form is not on your Sliick Edge address, nobody is on its Embed allowlist, or it has a Stripe payment field, which does not work embedded. See Embedding a form on your own site.

Starting or stopping an A/B experiment reaches a form on Sliick Edge without a new publish. It can take a few minutes to reach every visitor. See Versions and A/B experiments.

The builder’s Share tab can check, on demand, whether your public address is ready to serve a form. It also tells you when a form is not being served because Allow on your public Sliick Edge address is unticked.