The Field Builder

The field builder is where you tell Docshark what each recipient fills and signs. It opens on step 3 of the envelope wizard. And on templates, where the layout saves for reuse.

The canvas

• The document renders page by page. Scroll, zoom, and click any spot to drop a field.
• A recipient picker at top decides whose field you are placing. Each recipient gets a color, and every field on the page shows its owner's color.
• The field palette lists all 21 field types. Drag one onto the page, or click to drop at the cursor.
• Fields move by dragging, resize from their corners, duplicate and delete from their menus. Snap guides align fields to each other.

The properties panel

Select a field and the panel shows everything configurable on it:

• Recipient. Reassign whose field this is.
• Required / optional. Required fields block the signer from finishing.
• Label and placeholder. The text the signer sees.
• Validation. Formats and ranges for text and number fields.
• Options. The choices for radio, dropdown, and checkbox-group fields.
• Read-only value. For fields that display a fixed value.
• Formula. On formula fields, the expression that computes the value from other fields.

Mako field placement

Suggest fields asks Mako to read the document and propose placements, it finds signature blocks, date lines, and fill-in blanks, then places suggested fields with a confidence chip on each (high/medium/low). Accept the good ones, drag the rest, it is a starting grid, not a verdict.

Anchor tags

For documents you control, embed invisible anchor text. A token like {{sig:1}} in the source document. On upload the builder places the right field at each anchor automatically. Templates built this way stay correct even when the document's wording shifts the layout.

Bulk tools

• Copy to other pages, replicate a field (same type, same recipient) across pages, initials on every page in one action.
• Tab order. The order signers tab through fields; the builder shows and lets you fix it.

Checking your work

• The per-recipient field count in the header warns when a recipient has no signature-type field. An envelope can send without one (a form to fill, an approval), but the warning makes sure it is intentional.
• Preview as recipient walks the signing flow exactly as that person will see it. Tab order, required blocks, and all.