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 and operators | Full access to form definitions, elements, and versions, full access to submissions, the Sliick Forms Admin app and all four of its tabs |
| 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 |
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 only. 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.