Form settings

Everything about a form that is not a field. Click the gear icon in the top bar of the builder to open it.

The modal shows the form’s public ID (fixed, because links depend on it), the Form name and its Folder, and groups the rest into the sections below.

Availability

• Share URL (optional): where you actually placed this form. See Sharing a form.
• Allow on your public Sliick Edge address: off by default. Ticking it is what puts this form on your connected Sliick Edge address; the line underneath names the exact address it would produce. See Hosting on Sliick Edge.
• Open from and Close at: an optional scheduled window.
• Close after this many responses: an optional response cap.
• Embed allowlist and CORS allowlist: which sites may put this form in a frame, and which may fetch its data from a script. See Embedding a form on your own site.

Whether the form is accepting responses right now is not here: that is the state pill in the top bar. See Accepting responses.

A scheduled window and a response cap both produce their own notice for respondents. See Accepting responses.

After submit

• Success message: what respondents see when they are done.
• Show a review step before submit: respondents get a summary of their answers with edit links before the final submit.
• Redirect after submit: an optional URL to send them to instead.

Notifications and integrations

• Notify these emails on every submission, comma separated.
• Send the respondent a confirmation email, chosen from the form’s Email-type fields, or Off.
• Webhook URL: receives a POST for each response. Its host must also be allowed in Salesforce’s Remote Site Settings, and a Slack or Teams webhook URL will not work on its own. See Webhooks.

Notification and webhook sends both swallow their own failures by design, so a bad address or a down endpoint can never block a submission from being staged.

Emails are sent in the background, so they arrive shortly after the response rather than instantly. A failed email send is recorded in Form Log as counts and codes only, and never blocks a response.

Note: this modal is the only place that validates these settings, so a malformed email address or a webhook URL that is not https:// is rejected here rather than failing silently later.

Form language

The language the form is written in, chosen from the 18 languages Salesforce fully supports. New blank forms start in your org’s language, and a form that has never declared one behaves as it always did.

Sliick Forms’ own respondent text appears in that language: buttons, the thank-you page, notices, validation, upload and save-for-later messages, screen-reader labels, and the confirmation email. When the form has translations, a respondent gets the best match for their browser language instead. A Canadian French browser is served French, and European Portuguese is served Brazilian Portuguese. The language switcher lists each language by its own name.

The Translations panel offers the same 18 languages, so a translation can no longer be filed under a misspelt code.

On a multilingual Experience Cloud site, turn on Follow the site’s language on the form component to show the visitor’s site language instead. See Public forms on Experience Cloud.

A guest profile you set up yourself needs two extra grants. A closed form shows in English unless the guest can read the form’s Language and Translations fields. See Guest access for public forms.

Record types

Listed only where a mapped object has more than one active record type, and publishing is blocked until each one is chosen. See Record types.

Object model

Which object the form is mostly about, and which lookup joins two of them. Absent for a form that maps to a single object, since there is nothing to ask. See The form’s object model.

Theme

Each form has its own theme panel. See Themes and branding.

If a control here is greyed out, your permission set has read access to the field behind it but not edit access, and the hint under the control names the exact field to ask your Salesforce administrator for. Everything else still saves normally, and the locked control is withheld rather than silently discarded.