What Sliick Forms is
Start here if Sliick Forms is new to you. This page explains what the product does and names the four pieces you will meet on every other page.
Sliick Forms lets admins build forms inside Salesforce. You drag fields onto a form, choose the Salesforce object and field each answer goes to, and publish it.
People can fill in a form in these places:
- Inside Salesforce, on a Lightning page, for your own staff.
- Behind a login, on your Experience Cloud site.
- In public, on an Experience Cloud page. The form is served by Salesforce.
- In public, on your own Sliick Edge address. The form is served by Sliick Edge, hosting that Sliick runs outside Salesforce. Answers pass through it on the way to your org.
You never export answers and import them again. Every response waits in your org first, so you can check what it will write. When you process it, the answers land on the right Salesforce records.
The four pieces
Section titled “The four pieces”| Piece | What it is |
|---|---|
| Form Definition | The form itself. It has a fixed Form ID (its External ID), which integrations and links rely on |
| Form Builder | Where you edit one form: fields, logic, pages, mapping, settings and publishing |
| Published version | A snapshot of the form, taken when you publish. It never changes, and it is what people actually fill in |
| Submission | One person’s answers, held in your org until you process them onto your Salesforce records |
Two ideas worth knowing
Section titled “Two ideas worth knowing”Editing is not publishing. Changing a form never changes what people are filling in right now. You publish to make your changes live. Every version you have published is kept, so you can compare against it or go back to it.
A response is not a record yet. Answers arrive as a submission and show in the responses console. Nothing is written to your Contacts, Cases or Leads until you process the submission, and you can preview exactly what processing will do first.
Note: answers never go straight onto your records. Because they wait first, you can review, correct and retry a response before it touches your data. See Processing responses onto records.