What is Sliick Docs
Sliick Docs brings native, versioned document generation to your Salesforce org. Admins design templates in a visual editor and publish them as frozen releases; business users generate the resulting PDF or Microsoft Word file in one click from a record page, a list view, a Flow, or a bulk batch. Read this page first if the product is new to you: it explains the words the rest of the documentation uses.
Where your documents are produced
Section titled “Where your documents are produced”Sliick Docs is a native Salesforce document-generation app by default. Both PDF and Microsoft Word files are generated on-platform, and no document content leaves your org or passes through a third-party service on the standard path.
Two capabilities are opt-in exceptions, and both are called out wherever they appear: the premium high-volume rendering path (see Generation at scale and your own storage) and the premium cryptographic signature seal (see E-signature settings).
The words this documentation uses
Section titled “The words this documentation uses”| Term | What it means |
|---|---|
| Template | One per logical document type (Account Summary, Quote Cover Letter, Work Order). Admins edit a template; end users generate from it. Each template can be configured to allow PDF output, Word output, or both. |
| Draft and Release | While a template is being edited it lives as a draft. Publishing creates an immutable Release: a frozen snapshot the runtime renders from. Drafts can change freely; releases never do. |
| Active Release | The release currently serving end users. Switching versions or rolling back is a single, fully audited change. |
| Bundle | A named, ordered collection of templates rendered together against a single record as one combined PDF. Bundles publish to immutable releases too. |
| Batch | A bulk run that produces many files from one template (or one bundle) against many records. |
| Generation | The audit record for one rendered file, surfaced on the Generations tab. It tracks who generated what, in which format, from which template release, against which record, and the email outcome if auto-email is enabled. A record’s full generation history is paged, so long histories stay reachable rather than stopping at the most recent page. |
| Base object | Every template (and bundle) is anchored to a single Salesforce object. Merge fields and runtime data come from records of that object. |
| Evidence pack | A document whose image block embeds every file attached to a record, or to each child record, collated into one PDF. See Evidence packs. |
| Storage | Generated documents are saved to Salesforce Files by default. With Sliick Files installed, evidence-pack photos can be read from, and generated documents written to, your organisation’s own connected cloud storage. |
The four ways to generate a document
Section titled “The four ways to generate a document”- From a record page, in one click. See From a record.
- From a list view: tick records and click a mass-action button. See List-view mass action.
- From the Doc Batches console, for admin bulk runs. See Doc Batches.
- From a Flow: record-triggered, scheduled, or screen. See Flow actions.
All four share the same rendering engine, so what your admin sees in proof is what every recipient gets. Documents can also be sent for electronic signature.
Sliick Docs is a document platform rather than only a document generator: it also collates a record’s files into evidence packs, generates large image-heavy documents at scale, keeps output in your own storage, and sends documents for signature.