Install and permission sets

This page is for the Salesforce admin doing the first-time setup. It covers installing the package, giving each role the access it needs, and finding your way around the app.

Install the package

Install from the Sliick Docs AppExchange listing.

When prompted, install for All Users, or for Admins Only if you want a controlled rollout and would rather assign the relevant permission set per user.

The listing always installs the current release. To upgrade an org that already has Sliick Docs, install the listing again over it; your templates, releases and settings are kept. Read the release notes first, because some releases change behaviour you rely on.

The open-source Sliick Charts package can be installed in the same org alongside Sliick Docs if you want placeable charting components of your own. It is entirely separate from the charts inside Sliick Docs, which belong to the Analytics dashboard and are not offered in Lightning App Builder or Flow.

Permission sets

Five assignable permission sets ship with the package. Assign each user the one (or two) that match their role, from Setup > Users > Permission Sets.

Permission set	Grants
Sliick_Docs_Admin	Template authoring, proof, publish, the Doc Batches console, and the Doc Bundles console.
Sliick_Docs_User	Record-page generation only, with no authoring and no consoles.
Sliick_Docs_Template_Author	Design, proof, publish, bundles, and batches: the authoring subset of Admin, including turning e-signature on or off for a template. Audit and retention settings are read-only for this role, so policy stays with whoever owns DevOps.
Sliick_Docs_Automation	For the running user of any Flow that calls Sliick Docs, or for a dedicated integration user. Just enough access to run document generation from automation. No broad “View All / Modify All” rights.
Sliick_Docs_Integration	For a dedicated integration user where one is needed. Least privilege, assigned to that user rather than to an admin.

A sixth set, Sliick_Docs_Signer_Guest, is not assigned to people at all. It is assigned to your signing site during e-signature setup.

What changed in 3.0

The upgrade updates the shipped permission sets for you; there is nothing to configure.

• Template Authors can turn e-signature on and off for a template and acknowledge the sender warning, exactly as Admins can. If Sliick_Docs_Template_Author is assigned more widely than you want e-signature switched on, review who holds it. Anyone without it or Admin sees the switch greyed, with the sentence “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.”
• Combined Word bundles work for every user who can generate. In 2.11 and 2.12, users holding only Sliick_Docs_User or Sliick_Docs_Automation could not generate a combined Word bundle. 3.0 adds the access they were missing.

Tip: in production, treat Sliick_Docs_Admin as a privileged role for the small group who own document policy, and give day-to-day template builders Sliick_Docs_Template_Author instead. End users only ever need Sliick_Docs_User. The running user of every Sliick Docs Flow needs Sliick_Docs_Automation.

Open the Template Library

Open the App Launcher and select Sliick Docs. The default landing tab is the Template Library. The other top-level tabs you will use are Doc Bundles, Doc Batches, Generations, Analytics, Diagnostics, and Settings.

Clicking New template from the Library opens straight into a gallery of six ready-made starters alongside the option to start blank. See The template editor and Starting from the gallery.

Next

Set the palette every template inherits before your authors start work: see Themes and branding.