Skip to content

Form settings

Form settings cover everything about a form that is not a field. To open them, click Settings (the gear icon) in the builder’s top bar. Click Save Settings when you are done.

The Form settings dialog for the Spring Promotion form, with the Availability section open showing the Sliick Edge option, an open and close date and a limit of 500 responses

At the top you see:

  • The form’s External ID. It never changes, because the form’s public links depend on it.
  • Form name and Folder.

The rest is grouped into the sections below.

  • Share URL (optional): the address where you have actually placed this form. See Sharing a form.
  • Allow on your public Sliick Edge address: off by default. Tick it to make this form available on your connected Sliick Edge address, which is Sliick’s hosting outside Salesforce. Once Sliick Edge is connected, the line underneath shows the exact address. See Hosting on Sliick Edge.
  • Embed allowlist and CORS allowlist: which websites may show this form inside their pages, and which may load its data from their own code. See Embedding a form on your own site.
  • Open from (optional) and Close at (optional): a time window when the form is open.
  • Close after this many responses (optional): a limit on the number of responses.

A time window and a response limit each show respondents their own notice when the form is closed. Whether the form is accepting responses right now is set with the Accepting responses switch in the top bar, not here. See Accepting responses.

The After submit and Notifications sections of Form settings, with a success message, the review step ticked, a notify email and a confirmation email sent to the Email field

  • Success message: what respondents see when they finish.
  • Show a review step before submit: respondents see a summary of their answers, with links to change them, before they submit.
  • Redirect after submit (optional URL): a web page to send respondents to instead of the success message.
  • Notify these emails on every submission (comma-separated): who gets an email for each response.
  • Send the respondent a confirmation email: pick one of the form’s Email fields to send it to, or leave it off.
  • Webhook URL (optional, POST on every submission): another system to notify of each response. Its address must also be added to Salesforce’s Remote Site Settings. A Slack or Teams webhook address will not work on its own. See Webhooks.

These checks happen when you save. An email address that is not valid, or a webhook URL that does not start with https://, is rejected here with a message, so you find out now rather than later.

A problem sending never stops a response. If an email address bounces or a webhook is down, the response is still received. Emails are sent in the background, so they arrive shortly after the response rather than instantly. A failed email is noted in Form Log.

Form language is the language your questions are written in. You can pick any of the 18 languages Salesforce fully supports. New blank forms start in your org’s language. A form with no language set shows Not set (English).

Sliick Forms shows its own text for respondents in this language: buttons, the thank-you page, notices, error messages, upload and save-for-later messages, screen-reader labels and the confirmation email. The builder notes that a few system messages may still appear in English.

If the form has translations, each respondent gets the closest match to their browser’s language instead. For example, a Canadian French browser gets French, and a European Portuguese browser gets Brazilian Portuguese. The language switcher on the form lists each language in its own name.

The Translations panel (open it with Manage translations on the Design tab of the right panel) offers the same 18 languages.

On an Experience Cloud site with several languages, turn on Follow the site’s language on the form component to show the form in the visitor’s site language. See Public forms on Experience Cloud.

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

This section only appears when an object the form saves to has more than one active record type. You must choose one for each before you can publish. See Record types.

Which object the form is mainly about, and which lookup links two objects together. This section does not appear for a form that saves to only one object. See The form’s object model.

The form’s colours, font and logo are not in this dialog. They are on the Design tab of the right panel. See Themes and branding.

If a setting is greyed out, your permission set lets you read the field behind it but not edit it. The hint under the setting names the exact field, so you can ask your Salesforce administrator to give you edit access to it. Everything else still saves normally, and the locked setting is left as it was.