Combining & reflowing documents

The document bar and its layouts

The document bar sits in a dedicated row directly above the preview canvas, not in the top nav. The editor toolbar (undo/redo, page navigation, field types, zoom, split Run button, +More menu) sits just above it; the global nav keeps only Save/Discard.

The bar picks one of three layouts automatically from the template's contents (no manual toggle):

• Multi-source (default): full tab strip, one tab per source; drag to reorder. For multiple sources, or one source plus a Form tab.
• Single-source: a compact row with source name, ⋯ menu, and × remove. For exactly one source and no Form tab (common for batch templates and simple "fill out one PDF" templates). The ⋯ opens the same row settings as the multi-source chevron.
• Form-only: a minimal Form label with × button, when the template has only form questions and no PDF source.

A brand-new (empty) template shows only + Add. Adding a source to a single-source template promotes it to multi-source the moment the new tab lands.

What a tab points at

Every page in the output comes from a tab, and each tab occupies a range of pages in the final PDF. A tab references one of:

• A workspace document source asset (preferred): a PDF blueprint (cover sheet, letterhead, terms page, blank form) uploaded once at workspace level and reused across templates. Sources are workspace-owned, shared by every template and automation; manage them under the Documents tab. The asset's file category becomes one of this template's input categories, telling the autofill picker which incoming files it consumes. Changing a source's category instantly updates every template using it (no per-template re-tagging).
• Another template's output: for aggregating templates that stitch other templates' outputs into one packet; points at the upstream template by ID.
• A blank-page placeholder: shown as ⬜ Blank; a separator or reserved space for stapling/signature.
• A Form tab: appears whenever the template has form-question inputs; always leftmost, hosting the questionnaire surface. (Template-level AI Instructions are edited in the details dropdown, not here.)

Per-tab vs source-level settings

Each source tab's chevron (multi-source) or ⋯ (single-source) opens a popover with row-only settings: AI instructions for this row (augments extraction for fields sourced here) and Include pages from source (an "All pages" tri-state plus per-page checkboxes with thumbnails, to slice a multi-page PDF down to the pages this template needs). Template-reference tabs show both; blank tabs show only a page-count stepper and orientation toggle.

Source-level settings (rename, file category, automation) live on the workspace source itself: change them from the Documents tab, since they affect every template referencing that source. The details dropdown (click the template name in the toolbar) shows a read-only Routed from chip per derived input category.

Page navigation lives in the toolbar's page navigator (between undo/redo and zoom), walking pages within the current document ("1 / 5" through "5 / 5", regardless of where that document sits in the combined output); click a tab to switch documents. It hides on the Form tab and single-page documents.

The + Add popover (right end of the bar) lists Sources from this workspace (name, category chip, lightning-bolt automation chips; a source can appear more than once; search appears above 8 sources) and Other: Upload new file (pick a PDF, name it, assign an existing or new file category), Blank page (1 portrait page), and Add form (grayed out if a Form tab exists; otherwise creates a starter form-question field and snaps the preview to the new Form tab).

Document reflows

Placement is normally exact and fixed, perfect when the document never changes. Turn on Document reflows (details dropdown, bottom, beside output-category and file-name; only on file-generating templates) when content can grow, shrink, or shift: an extra paragraph or longer scope pushing a signature block down or onto the next page. At fill time the AI reads the document, locates each field's anchor (its printed label and the line it sits on) and stamps the value where that anchor sits now. With it off, fields render at saved positions and fills stay instant, so enable it per template, not by habit. The repositioning pass only runs when the toggle is on.

Each write zone gains an optional Anchor hint naming what the field attaches to. Hints are optional (the AI usually works out the anchor from context) but sharpen placement on busy pages with several similar lines. Fields that fill named PDF form fields are placed by name, never coordinates, so reflows never moves them.

FieldBid Price

HintTo the right of the BID PRICE: $ label, resting on the underline

Troubleshooting

• Anchor can't be found: the field stays exactly where you placed it (never a random guess). In Test & Preview, a notice above the preview lists how many fields couldn't be auto-placed and were left at the template position; verify there before relying on output. If one field keeps landing slightly off, give it an anchor hint that names the label and edge relationship ("to the right of TOTAL:, on the underline").
• Removing the Form tab: a destructive action; clicking × opens a confirmation listing fields to be deleted (question-only) or mutated (mixed-input); template-level AI Instructions are also cleared.
• Deleting a source is orphan-tolerant: a tab pointing at a deleted source stays as "Missing source" and renders blank pages where its pages would have been. Repair by removing the dangling tab (×), re-adding the replacement from + Add, then dragging it into position.

Related

• Field placement
• Managing document sources
• Running autofill
• Assemble the transmittal: see it in action