If you have a user or users who cannot see a Experience Cloud Form (Previously known as a Community Form), below are some troubleshooting tips you can review to ensure proper access has been granted and the correct settings are in place.
Formstack Permission Set
Please ensure your user has been assigned the permission set Formstack Experience Cloud Permissions. To assign a Permission Set, please review the following article from Salesforce here.
When you first install the Salesforce Application, we automatically assign this Permission Set both post-installation and whenever we conduct a new release. However, between these release periods, simply creating a new Experience Cloud user does not automatically grant them this Permission Set. You can either manually assign it or ask your Salesforce Developer to create an Apex Trigger that automatically assigns the Permission Set.
You may not need all of the following permissions in every community, but Formstack forms will function properly when they are all applied. Below are the key permission sets and system permissions required for different user types:
-
Community Site Guest User
-
Permission Sets: Formstack Community Forms
-
System Permissions (grant through the profile or a custom permission set):
-
Apex REST
-
API Enabled
-
-
-
Public Site Guest User
-
Permission Sets: Formstack NativeCloud Permissions
-
System Permissions (grant through the profile or a custom permission set):
-
Apex REST
-
API Enabled
-
-
-
Primary Formstack User
-
System Permissions (grant through the profile or a custom permission set):
-
Apex REST
-
API Enabled
-
-
-
Logged-In Community User
-
Permission Sets: Formstack Community Forms
-
Field Access:
-
Needs Read/Write access to all fields on the form.
-
If there are lookup fields, needs Read access to the fields in the lookup list view and any fields used for the list view filter.
-
-
System Permissions (grant through the profile or a custom permission set):
-
Apex REST
-
API Enabled
-
-
Ensure Object Permissions
Please ensure that your Experience Users have access to all of the Objects and Fields on your Experience Cloud Form. If you are unsure, you can try creating a custom Permission Set that gives create, edit and read access. If you are unsure how to do this, please reach out to your Salesforce Administrator or Salesforce Application Support.
Ensure The Users Are Assigned Supported Experience Cloud Profiles
We have two Standard Profiles for Community which we do not support, because the setting API Enable is not checked, which are:
- Experience User (Formerly known as Customer Community User)
- Experience Login user (Formerly known as Customer Community Login User)
If you are using these two profiles, you cannot use the Logged-In user context to assign records to users. Only the Admin User Context can be used which assigns Records to the Formstack Admin. If you do still want to use these profiles, please make sure you created a Permission Set to grant access to API Enabled.
Profile Must Have Apex REST Services and Salesforce API enabled
The Experience User Profile or Permission Set must have Apex REST Services and API Enabled as enabled features. You can see a screenshot of these settings below.
Formstack Object Sharing Settings Must Have Public Access
The Formstack Objects will need to have Public Read Only access set in Salesforce sharing settings. This can be done by navigating to Setup > Security > Sharing Settings.
In order to make our forms available for the experience users, we will need to set the Default External Access for some of the Formstack objects to be Public Read Only.
Here are the objects:
Template - Public Read Only
- This is for Classic/Native Community and NativeCloud
Form Page - Public Read Only
- This is for NativeCloud and Community in order to have the Prefill working as well.
Form Style - Public Read Only
- This for Community and NativeCloud.
Submission Draft - Public Read Only
- This is for NativeCloud save for later to load the data after I hit save and open the link.
CSP Issues in Experience Cloud Forms
Your Experience Cloud form may not load if you have images embedded or a Stripe payment field. This is because Salesforce prevents access to endpoints outside. You will need to Add CSP trusted sites for both your org URL and for the Stripe endpoint being blocked. These endpoints are listed in the error or the Experience Cloud Builder (Formerly known as Community Builder). To make things easier, we have provided a single button in Admin Settings under Settings and Permissions that will automatically add required Trusted Sites.
Please note the image below shows Community Forms, but the button may also say Experience Cloud Forms and would function the same.