Skip to content

Headers, footers and page setup

Everything on this page is about the document as a whole rather than a single block: what repeats on every page, where pages break, and what is stamped across them.

Documents can carry running headers and footers that repeat on every page, with page numbers and dynamic merge content: an account name in the header, a page count in the footer, or both.

Use the Body / Header / Footer switcher above the canvas to edit each surface directly. A different-first-page toggle omits the header and footer from a cover page, which is the usual layout for proposals and statements.

Barcodes render in running headers and footers as well as in the body, and header and footer content is checked for unprintable characters exactly like body text. See Proof, publish and versions.

A Page break block forces a new page at runtime. A Section block can also be set to start on a new page, which is usually the tidier choice when the break belongs to a whole group of content.

Dashed guides on the canvas show approximately where the document will break across pages as you author.

In the right rail’s Page settings, the Watermark controls stamp every page of the generated PDF.

  • A text watermark takes text, colour, opacity and font size, for DRAFT, CONFIDENTIAL, copyright lines, or document-classification labels.
  • An image watermark is sourced from a file already in Salesforce, with adjustable opacity.
  • The two can combine, for example a brand logo paired with a “DRAFT” stamp.

The editor preview matches what the document will contain. Theme references and merge-field chips are not supported inside the watermark text, which is a plain string.

Note: the image watermark is honoured by both PDF and Word output, but the text watermark is PDF-only, so a template with a text watermark cannot enable Word output. The validator surfaces this at save time. Admins typically split a template when both an editable-Word workflow and a stamped-PDF version are needed.