Skip to content

Guest access for public forms

This page is only for public forms on Experience Cloud. A form on your Sliick Edge address does not need any of this: it reaches your org through the integration user you chose when you connected Sliick Edge.

On Experience Cloud, a visitor who is not logged in uses your site’s guest user. That guest user needs some access before a form will load. Salesforce does not let a managed package set up a site’s guest user, so you do this part yourself.

Work through the steps in order. Each missing step causes a different problem, which is why a public form that “does not work” is rarely just one thing.

Assign the packaged Sliick Forms Submitter permission set to the site’s guest user. It gives the guest what a public form needs: read access to your forms, permission to send in a submission and to save answers for later, and access to the form component.

Use this permission set rather than setting things up by hand. It comes with the package and is updated when you upgrade. To see exactly what it grants, open it in Setup.

If it is missing, the page shows Unable to load form where the form should be.

Do not give the guest user access to the package’s integration endpoints. A public form does not use them. Only Sliick Edge uses them, signed in as your integration user, and they are deliberately left out of the Submitter permission set. Granting them to the guest user would let anyone on the internet submit, upload and resume, with no way for you to tell who it was, limit them, or shut them off.

The Submitter permission set covers all of these. They are listed so you can recognise what goes wrong if one is missing, for example on a guest profile you set up by hand.

The guest needsWhat goes wrong without it
Read on Form Definition and Form Element, and read access to their fields the form usesThe form does not load, or loads with pieces missing and no error
Create on the Form Submission eventSubmitting fails with a server error
Create on the Form Partial eventSave and continue later fails for visitors. The form still loads and submits, so it does not look like a setup problem
Read on the form’s Language and Translations fieldsA closed form shows in English instead of the form’s language

If Save and continue later fails on a site where everything else works, check this grant first.

Give the guest no access at all to responses or saved partial answers, not even read. See Why visitors never get access to responses, below.

This is also a common problem after an upgrade. If you set field access on the guest profile yourself, the package cannot update it. When a release adds a field the public form reads, you need to make that field visible yourself. See Upgrading the package.

The site’s guest user must not have the API Enabled permission, from any source. This protects every respondent’s answers, and nothing in the package can enforce it for you.

Why it matters: because the guest can send in submissions, Salesforce also lets it read the stream of incoming submissions. Without API Enabled, there is no way for a visitor to open that stream. With API Enabled, anyone who can reach your site could read every respondent’s full answers, including saved answers from people who never finished, going back about three days.

This usually happens by accident: an admin turns on API Enabled for the guest while fixing something unrelated, because nothing on that screen warns them.

Check two things, when you install and after any change to the guest user:

  1. The guest profile does not have API Enabled.
  2. No permission set or permission set group assigned to the guest user grants API Enabled.

Check both. Adding the guest user to a permission set meant for an integration can grant API Enabled without anyone touching the profile. No permission set that comes with Sliick Forms grants it.

Do not try to fix this by removing the guest’s read access to submissions. Salesforce does not allow it. If your org truly cannot keep API Enabled off the guest user, talk to us first: public forms depend on it.

The permission set cannot do this part. Salesforce requires secure guest access, so a visitor cannot see any form until a sharing rule shares it with them.

  1. In Setup, go to Sharing Settings.
  2. Find Form Definition and click New under Guest User Sharing Rules.
  3. Set it up like this:
    • Rule type: Guest user access, based on criteria
    • Criteria, with filter logic 1 OR 2:
      1. Is Active equals True
      2. Was Published equals True
    • Share with: the site’s guest user
    • Access level: Read Only
  4. Save.

You need both criteria. The second one is easy to miss. A form that was published and then closed must stay shared. Otherwise visitors are told the form does not exist instead of that it is closed.

A form that has never been published and is not active matches neither rule, so it stays hidden. That is on purpose: nobody should be able to find such a form by guessing its address.

Was Published is ticked the first time a form is published and never cleared, so it means “this form has been live at some point”.

Form Element does not need its own rule. It follows the form it belongs to.

If a form shows as missing, fix the sharing rule. Do not give the guest more field access: it does not help, and it opens up more than you need to.

The site must be published, Live, and have Public Access turned on before anyone who is not logged in can see it. The exact settings are on Public forms on Experience Cloud.

If your Experience site uses a custom domain, or you have tightened security settings such as CSP or trusted sites, check that the form page still loads for a visitor who is not logged in. If you show the form on a website outside Salesforce, add that website’s address in Setup, CORS.

Why visitors never get access to response records

Section titled “Why visitors never get access to response records”

No packaged permission set gives the guest access to responses, and you should not add it.

Every visitor to your site who is not logged in shares the same guest user. If that user could read responses, any visitor could read every other visitor’s answers.

Instead, a visitor only sends the submission in, and Sliick Forms creates the response record itself. The visitor never sees the response record, or even its ID. Saved partial answers work the same way: visitors can never read them, and a respondent can only get back to their own saved answers through their resume link.

  • The Experience site exists, is published, is Live, and has Public Access on
  • Sliick Forms Submitter is assigned to the site’s guest user
  • The guest can create Form Partial events, if you use save and continue (Submitter includes this)
  • The guest has no access of any kind to responses or saved partial answers
  • The guest user has no API Enabled permission from any source: not its profile, not a permission set, not a permission set group
  • The guest has no access to the package’s integration endpoints
  • A guest sharing rule on Form Definition: Read Only, filter logic 1 OR 2 on Is Active and Was Published
  • Test: open the form page in a private browser window, not logged in to Salesforce, and submit it
  • The submission appears in Sliick Responses. This can take a few seconds