Upgrading the package

Upgrading is installing the new version over the old one, in the same org and the same way you installed it. Upgrades preserve your forms, your responses and your permission-set assignments. This page is the short list of what to confirm afterwards.

After upgrading, re-check

1. Permission-set assignments survived and the admin app still opens. Open the App Launcher, open Sliick Forms Admin, and confirm all four tabs load.
2. Any new fields the release added are visible to the site’s guest user, if you serve public forms on Experience Cloud. Field visibility lives on your own guest profile, so the package cannot manage it: a release that adds a field the public form reads needs that field made visible by hand. This is the classic post-upgrade failure, and it shows up as a form that renders with pieces missing rather than as an obvious error. See Guest access for public forms.
3. A public form still loads and submits. Open it in a private browser window, with no Salesforce session, submit it, and confirm the response appears in Sliick Responses.
4. Existing forms still serve their published version.

Assign packaged permission sets rather than copies of them. An upgrade updates a packaged permission set in place and can never add a new grant to a copy you own, so a clone falls behind quietly and fails later on something that used to work.

The release notes for each version call out anything upgrade-sensitive, including new fields a public form reads. See Sliick Forms releases.