Install and permission sets
This page is for the Salesforce admin setting Sliick Docs up for the first time. It covers installing the package, giving each person the right access, and finding your way around the app.
Install the package
Section titled “Install the package”- Open the Sliick Docs AppExchange listing and start the install.
- When asked who to install for, pick All Users. Pick Admins Only instead if you want a gradual rollout and plan to give access person by person with permission sets.
The listing always installs the latest release.
Upgrading: install the listing again over your existing Sliick Docs. Your templates, releases and settings are kept. Read the release notes first, because some releases change behaviour you may rely on.
Before you upgrade to 3.4
Section titled “Before you upgrade to 3.4”3.4 replaces the platform event Doc Signature Completed with a general one, Sliick Docs Background Task. It does the same job for completed signature requests, and also restarts stalled premium batches.
- If your org is at its platform-event limit, free one slot before you upgrade. The upgrade adds the new event before it stops using the old one.
- If you built your own automation on Doc Signature Completed (a Flow or trigger that listens for it), move it to Sliick Docs Background Task. The old event is no longer sent after the upgrade, so automation left on it stops running.
- After the upgrade, the old event stays in your org, unused, and still counts toward the limit until an admin deletes it. Delete it only after any automation of your own has moved off it.
Sliick Charts is a separate, open-source package. You can install it in the same org if you want chart components to place on your own pages. It has nothing to do with the charts inside Sliick Docs, which live on the Analytics dashboard and are not available in Lightning App Builder or Flow.
Permission sets
Section titled “Permission sets”The package includes five permission sets to assign to people. Give each person the one (or two) that match their role, from Setup > Users > Permission Sets.
| Permission set (label and API name) | Who it is for |
|---|---|
Sliick Docs Admin (Sliick_Docs_Admin) | The few people who own document policy. Everything: building, proofing and publishing templates, plus the Doc Batches and Doc Bundles tabs. |
Sliick Docs Template Author (Sliick_Docs_Template_Author) | Day-to-day template builders. Design, proof, publish, bundles and batches, and turning e-signature on or off for a template. They can see the audit and retention settings but not change them. |
Sliick Docs User (Sliick_Docs_User) | Everyone who generates documents from a record page. No template building and no admin tabs. |
Sliick Docs Automation (Sliick_Docs_Automation) | The running user of any Flow that uses Sliick Docs, or a dedicated integration user. Just enough access to generate documents from automation, without broad “View All” or “Modify All” rights. |
Sliick Docs Integration (Sliick_Docs_Integration) | A dedicated integration user, where you need one. Assign it to that user, not to an admin. |
There is a sixth set, Sliick Docs Signer Guest (Sliick_Docs_Signer_Guest). Do not assign it to people. It goes on your signing site during e-signature setup.
Tip: in production, keep Sliick Docs Admin for the small group who own document policy, and give template builders Sliick Docs Template Author. People who only generate documents need Sliick Docs User. The running user of every Sliick Docs Flow needs Sliick Docs Automation.
Experience Cloud (site) users
Section titled “Experience Cloud (site) users”Generating documents as an Experience Cloud (site) user is not supported. To get documents to site users, generate them as an internal user, for example with a scheduled Flow that runs Generate Sliick Docs (Bulk), and share the files with the site users who need them. Do not rely on a record-triggered Flow for this: it runs as the user who changed the record, which can be a site user.
Never assign Sliick Docs Admin, Template Author, User or Automation to site users. These permission sets are for people inside your company.
If you already have, do both of these:
- Remove those permission set assignments from the site users.
- In Setup > Sharing Settings, click Edit, set Template Release’s Default External Access to Private, and save. Until you do, those site users can read the published content of every template.
New installs from 3.3 start with Template Release set to Private. An upgrade may leave your current setting in place, so check it. Internal users are not affected either way.
What changed in 3.2
Section titled “What changed in 3.2”Upgrading updates the permission sets that come with the package. If your org uses its own or cloned permission sets or profiles, add these field permissions by hand:
- Every set that generates documents: Read on the Output Formats field of Template Release. Without it, generation fails for that person.
- Every set that builds templates: Read and Edit on the Output Formats field of Template Version.
- Every set or profile that sends for e-signature: Read on the Seal Failure Code field of Signature Request. Without it, the Sliick Signatures card does not load for that person.
What changed in 3.0
Section titled “What changed in 3.0”Upgrading updates the packaged permission sets for you. There is nothing to set up.
- Template Authors can turn e-signature on and off for a template, and accept the sender warning, just as Admins can. If Sliick Docs Template Author is assigned more widely than you want, review who holds it. Anyone without it (or Admin) sees the switch greyed out, with this message: “Turning e-signature on or off for a template needs the Sliick Docs Admin or Sliick Docs Template Author permission set. Ask your Salesforce admin.”
- Every user who can generate can now make a combined Word bundle. In 2.11 and 2.12, people with only Sliick Docs User or Sliick Docs Automation could not.
Open the app
Section titled “Open the app”- Open the App Launcher and select Sliick Docs.
- The app opens on the Template Library tab.
The other tabs are Template Editor, Doc Bundles, Doc Batches, Doc Analytics, Diagnostics, Learning Center and Sliick Docs Settings.
To create a template, click New Template in the Library. You can start from one of six ready-made starters or from a blank page. See The template editor and Starting from the gallery.

Before your template builders start, set the colours and branding every template uses: see Themes and branding.