Install and permission sets
The one-time setup for a new org: install the package, check the requirements, and give your team access. You need a Salesforce admin to do this.
Install the package
Section titled “Install the package”Install Sliick Forms free from the AppExchange listing and choose Install for Admins Only. You will grant access explicitly with permission sets in the next step, so installing for all users grants nothing extra and only widens the tab surface.
Confirm the install under Setup, Installed Packages: Sliick Forms should appear with the expected version and the sliick namespace.
What the package needs
Section titled “What the package needs”| Requirement | Needed for | Notes |
|---|---|---|
| Lightning Experience | Everything | The admin surface is built entirely from Lightning components |
| My Domain deployed | Everything | Standard Lightning requirement |
| Experience Cloud | Portal forms behind login only | A public form can run on your Sliick Edge address instead. See Hosting on Sliick Edge |
| A published Experience site available to guests | Public or guest forms placed on Experience Cloud | The site is yours: the package never creates one. Not needed if a public form is hosted on Sliick Edge instead |
Assign the permission sets
Section titled “Assign the permission sets”No packaged permission set is assigned automatically. Assign them yourself, from Setup, Permission Sets, select the set, then Manage Assignments. From the Salesforce CLI the same assignment is:
sf org assign permset --name Sliick_Forms_Admin --target-org <alias>| Permission set | Assign to | Grants |
|---|---|---|
| Sliick Forms Admin | Form authors | Full access to form definitions, elements, and versions, full access to submissions, read, create and edit on form partials (which is what a record link writes), the Sliick Forms Admin app and all four of its tabs |
| Sliick Forms Operator | Staff who send people a form link from a record and work the responses that come back, but do not author forms | Read-only definitions, elements and versions, read, create and edit on form partials, the Generate link component, and full working access to submissions through the Sliick Responses tab. No Admin Dashboard and no Form Builder |
| Sliick Forms User | Internal reviewers who read submissions but do not author | Read-only access to definitions, elements, versions, and submissions, plus the app and the plain Form Submission tab |
| Sliick Forms Submitter | Authenticated Experience Cloud or portal users who submit forms, and the site’s guest user for a public form on Experience Cloud | Read access for retrieving a form, permission to send in a submission, and access to the component behind a served form |
| Sliick Forms Integration | One dedicated integration user, never a person. Needed only if you connect Sliick Edge or build your own integration | The access that connection needs, including read on form definitions and elements. It grants no access to responses |
Sliick Forms Operator: read this before you assign it
Section titled “Sliick Forms Operator: read this before you assign it”Assign it to staff whose job includes sending someone a personalised form link, such as a case worker, a scheduler, or a front desk, but who should not be able to change the forms themselves.
sf org assign permset --name Sliick_Forms_Operator --target-org <alias>It is self-contained: an Operator does not also need Sliick Forms User or Sliick Forms Admin. Sliick Forms Admin already includes everything an Operator can do, so a person who authors forms needs only the Admin set.
An Operator gets the Sliick Responses console in full: searching responses, the dry-run panel, correcting answers, processing and retrying, the CSV export, and the results and funnel panels. That is the one tab they get.
What an Operator can reach. Working responses needs broad access to them. Staged responses are created by the site’s guest user or by an integration user, never by the operator, so the console needs View All to show anything; correcting or processing one edits a record the operator does not own, which Salesforce permits only under Modify All; and Modify All cannot be granted without Delete. So the set carries read, edit and delete over every staged response in the org, not only the ones that person works with.
Assign it to people you would trust with the responses themselves. If that is more than you want, Sliick Forms User is the read-only alternative: it sees responses and has no console.
Record links mean both working sets can read in-progress answers. A record link stores the values it will prefill in a form partial rather than in the URL, so minting one is a write to that object, and the object cannot be granted narrowly: creating a row requires reading the object, and every form is shared org-wide. Anyone holding Sliick Forms Admin or Sliick Forms Operator can therefore read and edit every respondent’s in-progress answers, on every form in the org. Both sets are meant to hold it, and neither can delete a partial: retention is the purge job.
Assign the packaged Integration set directly and never clone it. An upgrade updates a packaged permission set in place and can never add a new grant to a copy you own, so a clone quietly falls behind and the failure arrives months later as an access error on something that worked before.
Check the admin surface
Section titled “Check the admin surface”- Open the App Launcher and open Sliick Forms Admin.
- Confirm all four tabs load: Admin Dashboard, Form Builder, Sliick Responses, Form Submission.
- Open the Form Builder and create a throwaway form.
If the tabs load but actions fail, the cause is almost always a partial permission-set assignment rather than a data problem.
At this point internal authoring works. If you only need forms on internal Lightning pages, you are done.
Three things worth knowing about access
Section titled “Three things worth knowing about access”- Sliick Forms User does not include the responses console. The richer surface with filtering, CSV export, reprocessing, corrections, and analytics is part of Sliick Forms Admin and Sliick Forms Operator. A Sliick Forms User reviewer sees the plain list and detail view of submission records.
- Never assign Sliick Forms User to an external or guest persona. It grants view-all on submissions, which is an internal-staff grant.
- No packaged permission set grants create access on the submission object. That is intentional and explained under 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 site that is live and open to visitors. Work through Guest access for public forms before testing one.