Install and permission sets
The one-time setup for a new org: install the package, check you have what it needs, and give your team access. A Salesforce admin needs to do this.
Install the package
Section titled “Install the package”- Open the Sliick Forms AppExchange listing and click to install it.
- Choose Install for Admins Only. You give everyone else access with permission sets in the next step, so installing for all users adds nothing useful.
- Check the install: in Setup, open Installed Packages. Sliick Forms should be listed with the version you expect and the
sliicknamespace.
What your org needs
Section titled “What your org needs”| You need | For | Notes |
|---|---|---|
| Lightning Experience | Everything | The admin app runs in Lightning only |
| My Domain deployed | Everything | A standard Salesforce requirement |
| Experience Cloud | Forms behind a portal login only | A public form can run on your Sliick Edge address instead. See Hosting on Sliick Edge |
| A published Experience site open to guests | Public forms placed on Experience Cloud | You create and own the site. Sliick Forms never creates one. Not needed for a public form on Sliick Edge |
Assign the permission sets
Section titled “Assign the permission sets”No permission set is assigned for you. Assign them yourself:
- In Setup, open Permission Sets.
- Click the permission set.
- Click Manage Assignments, then add the users.
If you use the Salesforce CLI, this does the same thing:
sf org assign permset --name Sliick_Forms_Admin --target-org <alias>
| Permission set | Give it to | What they can do |
|---|---|---|
| Sliick Forms Admin | People who build forms | Everything: create and edit forms, publish, work all responses, create record links, use all four tabs of the Sliick Forms Admin app, and run Finish upgrade steps on the dashboard |
| Sliick Forms Operator | Staff who send people a form link from a record and work the responses that come back, but do not build forms | Use the Generate link button on record pages and the full Sliick Responses console. They can see forms but not change them. No Admin Dashboard and no Form Builder |
| Sliick Forms User | Internal reviewers who only read responses | Read forms and responses, and see the plain Form Submissions tab |
| Sliick Forms Submitter | Logged-in Experience Cloud or portal users who fill in forms, and your site’s guest user for a public form on Experience Cloud | Open a form and send in a response |
| Sliick Forms Integration | One dedicated integration user, never a person. Only needed if you connect Sliick Edge | What the connection needs to read forms. It cannot see responses |
Before you assign Sliick Forms Operator
Section titled “Before you assign Sliick Forms Operator”Give it to staff who send people personalised form links, such as a case worker, a scheduler or a front desk, but who should not change the forms.
sf org assign permset --name Sliick_Forms_Operator --target-org <alias>
- It works on its own. An Operator does not also need Sliick Forms User or Sliick Forms Admin.
- Admins already have it all. Sliick Forms Admin includes everything an Operator can do, so a form builder needs only the Admin set.
- Operators get the full Sliick Responses console: searching, previewing what processing will do, correcting answers, processing and retrying, CSV export, and the results and funnel panels. It is the only Sliick Forms tab they get.
Operators can see, edit and delete every response in the org. To work the console, they need access to every response, not just the ones they handle, and Salesforce does not allow editing other people’s records without also allowing delete. Give this set only to people you would trust with all of your responses. If that is too much, Sliick Forms User is the read-only alternative: it shows responses, without the console.
Admins and Operators can read answers people have saved but not yet submitted. A record link stores the answers it fills in ahead of time inside your org. Anyone with Sliick Forms Admin or Sliick Forms Operator can read and edit those in-progress answers on every form in the org. Neither set can delete them: they are removed by the scheduled clean-up.
Assign the packaged Sliick Forms Integration set as it is. Never clone it. Upgrades update the packaged set for you, but never update a copy you made. A copy slowly falls behind, and months later something that used to work fails with an access error.
Check the admin app works
Section titled “Check the admin app works”- Open the App Launcher and open Sliick Forms Admin.
- Check all four tabs open: Sliick Admin Dashboard, Sliick Form Builder, Sliick Responses and Form Submissions.
- Create a test form, then delete it.
If the tabs open but actions fail, the cause is almost always a permission set that is missing or only partly assigned, not a problem with your data.
You can now build forms. If you only need forms inside Salesforce, on Lightning pages, you are done.
Three things to know about access
Section titled “Three things to know about access”- Sliick Forms User does not include the responses console. Filtering, CSV export, reprocessing, corrections and results come with Sliick Forms Admin and Sliick Forms Operator. A Sliick Forms User sees the plain list and record view of responses.
- Never give Sliick Forms User to an external user or a site’s guest user. It lets them see every response, which is only for your own staff.
- No packaged permission set lets anyone create responses directly. That is on purpose, and explained in Guest access for public forms.
Note: a public form on Experience Cloud needs more than the permission set. It also needs a sharing rule and a live site open to visitors. Work through Guest access for public forms before you test one.