Documentation

Learn Docable

Start with the quickstart, then go deeper on the concepts. And if you'd rather run the first thirty minutes together, guided onboarding is one email away.

Getting started

Install the package, build your first data model, upload a Word template and generate your first document — in about 30 minutes.

Core concepts

How Docable thinks

Data Models

The governed heart of Docable. A data model defines the base object, relationships, fields, filtered collections, aggregates, conditions, images and Flow data sources a document process can use. Built by admins, reused by every template that needs the same data.

Merge tags

Each data model publishes a catalogue of approved tags — fields, parent paths, child collections, totals, conditions, images and runtime values. Tags are copied into Word documents; Docable resolves them at generation time.

Templates

A template is a Salesforce record plus a Word document. Templates are validated against their data model before they can be activated — document versions are tracked through Salesforce Files history.

Generation

Users generate from records and list views; Flows generate automatically as part of a process. Output is Word or PDF, chosen at runtime, rendered on platform and saved to Salesforce Files.

Template packs

Move templates between orgs with versioned export/import packs — config, documents and data model references included, with per-template review on import.

Permissions

Packaged permission sets split responsibilities: admins manage data models and templates; users generate documents. Generation respects the running user's access by default.

Stuck on something specific? Ask support — include the template name and what you expected, and we'll dig in.