Sliick Docs.

Sliick Docs turns your Salesforce records into polished PDF or Microsoft Word documents without leaving Salesforce. Admins design reusable templates in a visual editor with brand-driven styling, merge fields that reach across related records, repeating sections for child data, and barcodes or QR codes, then preview the output against a real record. Business users generate the finished file in one click from any record page; list-view mass actions and Flows generate them in bulk; and auto-email routes the finished document to the right recipients automatically.

No external services. No data leaves your Salesforce instance. PDF and Word are both rendered natively on the platform. Just secure, version-controlled document generation built for Salesforce.

Read the Sliick Docs: Complete User Guide

What’s new in v1.6

Codenamed Quire, the latest release lands editor craft and cross-org portability together:

• Running headers and footers: page numbers, dynamic merge content, and a different-first-page toggle for cover pages, rendered natively by the Salesforce PDF engine.
• Drag-and-drop reorder + undo / redo: blocks reorder by dragging on the canvas, and every change tracks in a document-level command stack with Cmd/Ctrl+Z and Cmd/Ctrl+Shift+Z.
• Table-row repeats with merged cells: a repeating section can render as table rows for line-item layouts such as invoices and statements, with horizontal cell merging for title bands and total rows. The canvas honours the merged-cell maths, so what you see is what the PDF emits.
• Flexible columns block: the column block supports two or three columns with custom widths, auto-redistribution to 100%, native stepper arrows on the width and gap inputs, and live gap rendering on the canvas.
• Cross-org template portability: export and import templates and bundles between orgs as portable .sdt files. Each template carries a stable cross-org identity, so re-promoting updates in place rather than duplicating. Imports offer four conflict policies (skip, update, duplicate, fail), a dry-run mode that previews the outcome before committing, optional auto-publish, and graceful handling of watermark images, attached files, folders, and org-specific references such as email templates and org-wide addresses.
• Refreshed starter templates: the six in-repo starters (Sales Proposal, Order Confirmation, Account Statement, Welcome Letter, Case Summary, Lead Follow-up) are rebuilt with native table blocks, colspan-merged title and total rows, three-column status strips, and an asymmetric letterhead layout. Customers downloading the gallery now get enterprise-shaped output out of the box.
• Bundle display-name uniqueness: Doc Bundle display names now enforce uniqueness, with auto-rename on insert and rename-collision protection on update - parity with how template names already work.
• Editor polish: native colour pickers (swatch plus hex input) across border, background, cell and toolbar controls; PDF / DOCX format badges and full-filename tooltips in the proofs drawer; merge / split buttons on table cells; range-aware validation messages that name the specific limit; and a fix so the page-bottom “Add block” button now lands in the undo history.
• 10-language end-user UI: the surfaces non-admin users actually see (record-page generator, help pane, Flow error messages) are localised across ten languages, signalling enterprise-readiness without touching template content.

Read the full Sliick Docs v1.6 release notes

Why teams choose Sliick Docs

• Stay native and secure: PDF and Word are rendered on-platform. No third-party services, no data egress, no Remote Site Settings.
• Two formats, one source of truth: Generate a PDF or a Microsoft Word .docx from the same template. Admins enable the formats per template; end users pick at runtime where both are allowed.
• Reduce admin friction: Admins design templates visually, with no Word documents to maintain or external tools to learn.
• Theme once, restyle everywhere: Brand colours and spacing live in a single theme that every template inherits. Change the theme, republish, and every document picks up the new look.
• Versioned by default: Every template change creates a new draft. Publishing snapshots an immutable release, so runtime output is always reproducible.
• Trust the merge fields: Field discovery respects each user’s security. Inaccessible fields fail explicitly, never silently.
• Compliance-ready: An opt-in audit log with SHA-256-fingerprinted merge-value snapshots for integrity verification, per-template retention policies, and template-level controls over who can generate what.
• Generate at any scale: One click from a record page, a list-view mass action across up to 200 records, async batches from the console, or fully automated from a Flow. The same engine drives every path.

Built for record-driven document workflows

Sliick Docs is at its best when documents are operational, not decorative. If your team produces the same kinds of documents repeatedly from CRM data, the standard Salesforce reporting and email tools rarely cover the gap.

Team or use case	What Sliick Docs improves
Sales operations and revenue ops	Generate quotes, statements of work, and order summaries directly from Opportunity or Order records.
Service and field operations	Produce work orders, service reports, and inspection summaries from any custom object.
Not-for-profit and member services	Create donation receipts, member letters, and grant acknowledgements without exporting data.
Education and accreditation programs	Issue enrolment confirmations, completion letters, and program documents from student records.
Property and asset management	Render lease summaries, asset reports, and condition reports straight from the relevant Salesforce data.

Feature highlights

A visual editor designed for Salesforce admins

Build pages with sections, callouts, headings, text blocks, dividers, spacers, tables, images, two-column layouts, signatures, repeating blocks, and conditional regions. The editor runs inside Salesforce as a Lightning Web Component, so you stay on-platform from authoring through to publishing. The merge-field browser sits in its own panel beside the canvas and stays in place as you work, with block settings in a separate panel and the design area in the middle; the browser collapses to a slim strip when you want more room.

Theme-driven styling and an inline formatting toolbar

A single brand theme defines your colours, heading sizes, body text, and spacing scale. Block-level controls handle background, borders, corner radius, line height, indent, and spacing, and an inline toolbar covers the usual text formatting: bold, italic, underline, font, size, colour, highlight, and alignment. Colours reference the theme, so a theme change repaints every template the next time it is published.

Merge fields are first-class objects, not text replacements

Insert merge fields from the base object, related records several lookups deep, child collections via Repeat blocks, or aggregates such as sum, count, and average over child records. Each field is a structured chip rather than a fragile placeholder string, with a format option for how it renders - currency, number, percent, date, and more - all locale-aware to the running user.

Fields are grouped into collapsible, searchable sections - record fields, parent lookups, related lists, running user, and built-ins - each showing how many fields it contains, so the right field is quick to find even on objects with dozens of fields. Related lists such as Contacts, Opportunities, or Cases can be browsed and inserted directly from the panel, which sets up the repeating section for you rather than requiring it first.

Running-user fields, date and time built-ins, and approval history

Reference the person generating the document - name, title, contact details, and manager - through the Running User fields, so a “Prepared by” line works cleanly across record-page, Flow, and batch generation without hard-coding anyone’s name. Built-in Today and Now tokens insert the current date and time in the user’s time zone, with optional formatting, so “as of” lines never have to be edited by hand. And any repeating section can render a record’s Salesforce approval history - who approved it, their comments, and when - which suits contract cover sheets, audit packs, and sign-off summaries.

Conditional content with an else branch

Conditional blocks support an else branch, so a single block renders one outcome when its condition is met and another when it is not, instead of two blocks kept in sync with inverted expressions. Existing templates are unchanged.

Find and replace

Search the text in a template and replace it in place, stepping through each match with an option to match case. It is a quick way to update a product name, a legal phrase, or boilerplate across a longer template.

Image merge fields, hyperlinks, lists, and watermarks

Bring any Salesforce image field in as a dynamic image, or set an image block to resolve per record for letterheads, signatory logos, and hero images. Wrap text or merge fields in hyperlinks, including merge values inside the URL itself. Author bulleted and numbered lists. Add a per-template watermark that renders on every page: a text watermark (colour, opacity, size) and an optional image watermark sourced from a file already in Salesforce, with adjustable opacity. The two can combine - for example a brand logo paired with a “DRAFT” stamp - and both PDF and Word output honour the image watermark.

Inline image sizing and on-canvas previews

Inline images offer five sizing modes that render identically in both PDF and Word output, and static images now preview directly on the design canvas while authoring, so authors see the real image without switching to preview mode.

Barcodes and QR codes as first-class blocks

Insert dedicated Barcode (Code 128) and QR Code (ISO 18004) blocks, bind them to any merge field, and configure width, height, and alignment. Encoding is fully native, with no external services and no static images, and renders reliably in the generated document.

Proof against a real test record before publishing

Pick a real Salesforce record as the test record for a template. Sliick Docs merges the live data, runs validation, and generates a proof using the same path as runtime. What you see in proof is what your end users will get.

Versioning and publishing built in

Every template has a draft that admins edit freely. When you are ready, publishing creates an immutable release and points the template at it, so runtime output is always reproducible and switching versions is instant. Bundles work the same way, freezing each member’s active release so a bundle published today renders identically a year from now.

graph LR
    Draft[Draft Version] -->|Edit and Validate| Proof[Proof Generation]
    Proof -->|Test Record| PDF[Proof PDF]
    Draft -->|Publish| Release[Immutable Release]
    Release -->|Active Release| Runtime[Record Page Generation]
    Release -->|Bulk| Batches[Doc Batches Console]
    Release -->|Flow| Invocables[Flow Actions]
    Runtime --> Files[Saved to Salesforce Files]

One-click generation from any record page (PDF or Word)

Drop the Sliick Docs Generator component on any record page. End users see the templates available for that object and click generate. Where a template allows both formats they pick PDF or Word at runtime; otherwise they get a single button. The finished file is created and saved to Salesforce Files against the record - no exports, no clicks-through-screens, no manual file naming.

Bulk generation with the Doc Batches console

The Doc Batches console submits and monitors bulk runs against a filter, a Salesforce report, or an explicit set of records. A pre-flight check confirms readiness and counts the records, and a spot-check previews the merged output against a handful of records before you commit. Generate individual files or a single combined PDF, with ZIP downloads on demand. Retry-failed is version-aware: if the template has been republished since the original run, the confirmation calls that out before re-running.

List-view mass action

Add a one-click list button to any object’s list views, standard or custom. End users select up to 200 records, click the button, pick a template and output format, and the batch submits in one click. The same button works across every object.

Multi-template Doc Bundles

A bundle renders several templates together against a single source record to produce one combined PDF. Order the members, mark each Required or Optional, and use a per-item condition to decide whether a member is included for a given record. Publishing freezes each member’s active release, so the bundle renders identically every time even if member templates change later, and a drift indicator flags the moment any member has been republished since the bundle was last published.

Auto-email after generation

Configure email-on-success per template: choose an email template, the recipient and optional CC, and the sending address. When generation succeeds, Sliick Docs sends the document and records the outcome on the generation history. Generation and email outcomes are tracked separately, so a delivered document whose email failed is still visible.

Flow integration

Three Flow actions make Sliick Docs callable from record-triggered, scheduled, or screen Flows, for single, bulk, and bundle generation. They never halt the calling Flow on failure, and each can generate PDF or Word.

Organise templates into folders

The template library supports folders, so a library that has grown across several teams stays easy to navigate. Create, rename, and delete folders, and move templates between them. Unfiled templates appear under an “Uncategorised” view, with an “All templates” view that still shows everything at once.

Cross-org template portability

Templates and bundles export to portable .sdt files for sandbox-to-UAT-to-production promotion. Each template carries a stable cross-org identity, so re-promoting the same template updates it in place rather than duplicating. Imports offer four conflict policies - skip, update, duplicate, or fail - with a dry-run mode that previews the outcome before committing. An optional auto-publish toggle activates templates on import if they pass validation, suiting repeatable promotion pipelines. Watermark images and attached files travel with the export, folder structures are created automatically in the target, and org-specific references such as email templates and org-wide addresses are resolved on import. Files exported from earlier versions still import.

Validation that catches problems before users do

Validation checks fonts, merge fields, theme references, and block styling so authoring problems surface in the editor, not in a finished document. Unresolved merge fields produce clear author-facing messages instead of silent blanks.

Files saved against the record, with a full generation history

Every generated document is saved to Salesforce Files and linked to its source record. A generation history records who generated what, in which format, from which template version, against which record, and the email outcome - an auditable trail with no extra setup.

Compliance and access controls

Three template-level controls let compliance teams set rules that apply across every generation path - record page, batch, Flow, and list view:

• Audience visibility: restrict a template to users who hold the right permission sets, so sensitive templates such as board packs, HR letters, or executive variants stay out of everyone else’s picker. Admins still see every template in the editor.
• Per-record targeting: scope a template to a specific set of records so it only appears, and only generates, for those records. Batch runs filter to the records in scope automatically rather than failing outright.
• Output-format lock: lock a template to a single output format so, for example, a signed contract cannot be generated as an editable Word document.

Compliance audit log

Opt in per template. Every successful generation captures a SHA-256-fingerprinted snapshot of the resolved merge values, so the contents are verifiable against the original generation. Entries are written through a protected path that Sliick users cannot suppress or forge.

Retention policies

Set a per-template auto-delete window. A nightly job removes generated files older than the window while keeping the generation record as an audit trail, and a hold option exempts specific documents for legal holds or audit windows. Admins schedule the sweep with one click in Settings.

Admin analytics dashboard

An admin-only Analytics tab draws on your existing generation history - no new tracking. It shows documents generated this month, last month, and lifetime, success rate, a daily volume chart, the top templates and users, and a breakdown of failures. It refreshes automatically, with manual refresh available.

Admin setup checklist

A Setup tab gives admins a single readiness view when onboarding the package, covering prerequisites such as permission sets, the org-wide email address, and deliverability. Each item shows its status and links directly to the relevant Setup page, so the most common install issues surface before the first template is built.

Security and architecture

Sliick Docs is built with a Salesforce-first security model:

• 100% native rendering: PDF and Word are generated on-platform. No external rendering services, no Remote Site Settings, no Trusted Sites.
• Security enforced everywhere: Field-level security and sharing apply to the running user throughout authoring, proof, and runtime. Audit writes are the only deliberately protected path, so users cannot suppress their own audit history.
• No data egress: No data ever leaves your Salesforce org during authoring, proof, runtime, batch, or auto-email.
• Least-privilege permission sets: Separate permission sets for admins, end users, and automation or integration users.
• Immutable releases: Published template and bundle releases are treated as read-only snapshots and held that way by permission-set field-level security plus a write-guard trigger. Switching the active version is a fully audited, single step.
• Fingerprinted audit log: When enabled, each generation captures a SHA-256 fingerprint of the resolved values for integrity verification - accidental corruption and changes by non-administrator users are detectable by recomputing the digest.

Technical specifications

Feature	Specification
Namespace	sliick
API Version	66.0
Component Type	Lightning Web Component (LWC) plus packaged custom objects
Supported Targets	Record Pages (end-user generation), App Pages (admin authoring and consoles)
Output formats	PDF (Salesforce native engine) + Microsoft Word .docx
Storage	Salesforce Files
Automation	Flow actions, list-view mass action, and the Doc Batches console for bulk runs
Compliance	Opt-in audit log, nightly retention, analytics, audience and output-format controls
Dependencies	None. No external libraries, services, or static resources

Quick installation

Get Sliick Docs into your Salesforce org in minutes:

1. Install Sliick Docs from the AppExchange listing.
2. Assign the Sliick_Docs_Admin permission set to admins, Sliick_Docs_User to end users, and Sliick_Docs_Automation to any Flow runner or integration user from Setup > Users > Permission Sets.
3. Open the Sliick Docs app from the App Launcher and create your first template.
4. Follow our Complete User Guide for step-by-step authoring, proof, publish, batch, bundle, and Flow instructions.

Sliick Docs is free on the AppExchange. Use is governed by the Salesforce AppExchange Program Agreement for Free Apps (the standard end-user licence for free AppExchange apps).

What implementation looks like

1. Install Sliick Docs into your Salesforce org.
2. Assign permission sets according to role.
3. Set the org-wide theme in Settings (brand colours, heading sizes, spacing scale).
4. Create a template against the base object you want to generate documents for, design the layout, drop in merge fields, pick a test record, proof, fix any validation issues, then publish.
5. Add the Sliick Docs Generator component to the relevant record page so end users can generate documents in one click.
6. (Optional) Configure auto-email on the template, or call Sliick Docs from a Flow for fully automated generation.

Teams can have a real, production-quality template live in their org on day one and a fully automated, bulk pipeline live by the end of the week.

Ready to bring native, secure, versioned, fully-automatable document generation into your Salesforce org?

Install Sliick Docs from the AppExchange

What shipped in v1.5.0

v1.5.0 turns to what the documents themselves can do, layered on top of v1.4:

• Multi-level nested data so a single template can repeat over related records and the detail beneath them - each opportunity and its line items, or each case and its comments.
• Live document previews that fill the canvas with real record data as you build, so you catch issues before generating.
• Rich-text fields that carry their formatting straight into PDF and Word output.
• A scope-aware field picker that follows your cursor and only offers fields that will resolve at the current level.
• Fewer layout restrictions - sections, callouts, and conditional blocks can now sit inside repeating sections and columns.

What shipped in v1.4.0

v1.4.0 focuses on the editing experience and library organisation, layered on top of v1.3:

• A redesigned editor layout that gives the merge-field browser its own panel beside the canvas, with more room for the design area and block settings.
• Faster merge-field navigation with collapsible, searchable, counted sections and paging for objects with many fields.
• Related-list insertion so child data such as Contacts, Opportunities, or Cases can be browsed and inserted directly, without setting up a repeating section first.
• Find and replace across a template’s text, with match-case and match-by-match navigation.
• Template folders to organise the library: create, rename, delete, and move templates between folders.
• Editor refinements, including a cleaner way to set signer labels in signature blocks.

What shipped in v1.3.0

v1.3.0 focuses on authoring efficiency and compliance controls, layered on top of v1.2:

• Running-user merge fields so a document can reference whoever generates it, across record-page, Flow, and batch generation.
• Today and Now date-time built-ins, with optional formatting.
• Approval history as a repeating section, with no custom code.
• Conditional else branches so a single block handles both outcomes.
• Audience visibility, per-record targeting, and output-format lock - template-level control over who can generate what, against which records, and in which format, enforced across every generation path.
• Image watermarks alongside the existing text watermark, honoured by both PDF and Word.
• Inline image sizing that renders identically in PDF and Word, plus on-canvas previews of static images.
• Admin setup checklist with readiness checks and one-click links to Setup.
• A new .sdt template format that handles larger, image-heavy templates more reliably; files exported from v1.2 still import.

What shipped in v1.2.0

Layered on top of the v1.0 Captivating release:

• Microsoft Word (.docx) output from the same template - one source of truth, two formats. Available on the record-page button, all three Flow actions, the Doc Batches console, and single-record bundles.
• Compliance audit log with SHA-256-fingerprinted merge-value snapshots for integrity verification, opt-in per template.
• Retention policies with a nightly sweep that removes aged files, with a per-document legal-hold option.
• List-view mass action for bulk generation across up to 200 records in one click, on any standard or custom object.
• Barcodes and QR codes as standalone blocks, native, with no external services.
• Per-record image blocks so the same image block can resolve per record for letterheads, signatory logos, and hero images.
• Admin analytics dashboard with generation volume, success rates, top templates and users, and failure breakdowns.
• Six starter templates on standard objects so they import cleanly anywhere.
• Generations tab for non-developer admins.
• A range of editor refinements.

What’s next

Sliick Docs continues on a native-tier roadmap, with further authoring and compliance enhancements in active development.

Building for a specific document workflow? Contact us to discuss your use case and roadmap fit.