Layout blocks: tables, columns, images and callouts

Blocks are the pieces a template is built from. Drag them from the Blocks tab on the left rail, or click + Add block inside any container. Every block is selectable, and the right rail switches to its Properties and Block style panels on select.

Block reference

Block	Use
Heading	H1, H2, or H3 heading line. Supports merge field chips inline.
Text	Paragraph text. Supports inline formatting per run and merge field chips.
Divider	Horizontal rule.
Spacer	Configurable vertical space.
Image	Embedded image. A Source toggle picks Static file (the same image on every document), Merge field (per-record letterheads, signatory logos, hero images), or Files on this record (an evidence-pack photo grid, see Evidence packs).
Table	Static table with manually authored rows and cells, with horizontal cell merging and a Ruling control for how row and column lines print.
Columns	Two or three columns with custom widths. The older two-column block is a special case and keeps working.
Page break	Forces a new page at runtime.
Signature	A signer block with top-bordered lines and merge-field signer labels.
Section	Group of blocks with optional padding and “start on new page” behaviour.
Callout	Section variant with a tinted background and a coloured left bar.
Show if (cond)	Conditionally renders its children based on parent-record data, with an optional else branch. See Repeats and conditional content.
Repeat for each	Loops over a child relationship of the base object; children render once per row, as stacked blocks or as table rows. Repeats can be nested to arbitrary depth.
List	Bulleted or numbered list, with merge field chips inside list items. Each list item is a text run that supports inline formatting.
Barcode	Code 128 barcode bound to any merge field. See Barcodes and QR codes.
QR Code	ISO 18004 QR code bound to any merge field. See Barcodes and QR codes.

Block-level styling

Every styleable block exposes a Block style section in the right rail. The controls render live in the canvas, so what you see matches what the finished document will contain.

Control	What it does
Spacing	Combobox per side (above, below, inner top, inner bottom). Pick Tight (4 pt), Normal (8 pt) or Spacious (16 pt) from the theme, or Custom for 0 to 48 pt.
Background	A brand or theme swatch (Brand Primary, Secondary, Accent, Heading or Body colour), or a hex code such as #F4F6F9.
Border	Width 1 to 8 pt; style solid, dashed or dotted; colour with a swatch-plus-hex picker. Per-side checkboxes pick which edges the border applies to.
Line height	Default / 1.0 (tight) / 1.15 / 1.5 / 2.0 (loose).
Indent	Stepper 0 to 4. Each level adds 24 pt of left padding. Text, heading and callout blocks only.

Blocks are square-cornered on the canvas because they are square-cornered in the finished PDF: the editor and the generated document take their defaults from the same place, so what you lay out is what prints. The native PDF engine does not support rounded corners.

Theme references such as brand.primary and theme.headingColor resolve when the template is published, so an org-wide theme change repaints every block using those references the next time the template is published. Hex codes are literal one-offs that do not track theme changes. See Themes and branding.

Tables

Merged cells

Table cells can be merged horizontally to build colspan title bands and total rows. Select a cell and use Merge right and Split in the cell properties panel; each option enables only when the merge maths allows it. The canvas renders merged cells at their true width, and adding or removing columns stays in lockstep with the merged geometry so a table never corrupts silently.

Vertical merge (rowspan) is not supported. Horizontal merging covers the title-row and total-row patterns most templates need.

Ruling

Selecting a table exposes a Ruling control alongside its other properties:

Ruling	What prints
Horizontal lines (default)	Rules between rows only: the convention for statements, proposals and line items.
Grid	Every cell edge ruled.
None	No rules at all, useful over a tinted background or when spacing alone should separate rows.

Striped rows and header-row shading work with all three. Already-published templates keep the ruling they were published with until you republish.

Columns

The Columns block lays content out in two or three columns with custom widths. Native stepper arrows adjust the width and gap, widths auto-redistribute to total 100% as you change any one (with a 10% minimum per column), and the gap renders live on the canvas. Templates built with the older fixed two-column block keep working unchanged.

Images

An Image block’s Source toggle decides where the picture comes from:

• Static file (the default): the same image on every document, picked from a Salesforce File.
• Merge field: the image varies per record. Bind any field that points to a Salesforce image file. This makes per-record letterheads work against any image field; pair it with auto-email and a letterhead field on Account to send branded statements without a separate template per account.
• Files on this record: a photo grid built from the record’s own files. See Evidence packs.

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

Signature blocks

A signature block renders a two-or-more signer area with top-bordered lines and merge-field signer labels, for example Account.Name for the customer line and Account.Owner.Name for the rep line. Add or remove signers in the right rail; the minimum is two.

Note: a signature block is printed layout, not an electronic signature. To collect a real signature, see E-signature.