Skip to content

WPsigner Document Builder adds a rich-text editor for creating a document without uploading an existing PDF. Add signers first, write the content, insert assigned signing fields, preview the PDF, and continue directly to WPsigner’s Review step.

ComponentMinimum
WPsigner3.0.2
WordPress5.8
PHP7.4
Document BuilderThis guide covers 1.5.17

The addon uses WPsigner’s bundled PDF engine and secure storage. It does not require a separate PDF service.

  1. Install and activate WPsigner 3.0.2 or newer.
  2. Go to Plugins → Add New → Upload Plugin.
  3. Upload the official Document Builder ZIP.
  4. Activate WPsigner Document Builder.
  5. Open WPsigner → Document Builder, or choose Document Builder from WPsigner → New Document.

If the addon does not load, confirm the main WPsigner plugin is active and meets the minimum version.

Add at least one signer with a valid email address, then choose a signing workflow:

  • Parallel Signing — all signers receive the request at once.
  • Sequential Signing — signers receive it one at a time in the listed order.

Click Continue to Document.

Enter a Document Title, then create the body with the TipTap editor. Available tools include headings, font size, emphasis, alignment, lists, links, images, tables, page breaks, find/replace, and shared headers and footers.

Headers and footers can use:

VariableOutput
{{page}}Current page number
{{pages}}Total page count

Choose the active signer in Assign fields to, then drag or click fields from Signing fields. The builder supports Signature, Initials, Text, Number, Date, Name, Email, Phone, Company, VAT, Title, Checkbox, Checkbox Group, Radio, Dropdown, Text Area, and Attachment.

Open Field settings to configure:

  • Display label
  • Mapping name for Zapier, API, and form feeds
  • Required or Optional
  • Choice options and validation
  • PDF layout for grouped choices

Signature fields are always required.

Use stable mapping names made from letters, numbers, and underscores. Changing a mapping name can break an existing integration.

  1. Click Preview PDF and review all pages, headers, footers, fields, and page breaks.
  2. Click Continue to review.
  3. WPsigner generates and stores the PDF as a draft.
  4. Complete security, expiration, reminders, and delivery settings in WPsigner’s Review step.

To revise a Document Builder draft, open it and click Edit content. Only drafts originally created by Document Builder can be reopened in the editor.

Click Save as template in the builder to preserve:

  • Body, header, and footer content
  • Signers and signing order
  • Field assignments and mapping names

Saved items also appear in the WPsigner template catalog. Choose a template to create another document, or delete it from the builder’s template panel.

You must save at least one Document Builder template before creating a Document Builder feed for a form integration.

Document Builder 1.5+ can create a document from:

  • Fluent Forms
  • WPForms
  • Gravity Forms

Open WPsigner → More → Integrations, configure the form plugin, then choose Manage Doc Builder feeds.

Each feed selects:

  1. A form and a Document Builder template.
  2. The form fields containing the signer’s name and email.
  3. Optional form-to-document field mappings.
  4. One delivery mode:
    • Open signing page immediately — redirect the submitter; no invitation email.
    • Send signing request by email — send the link; no browser redirect.

Signature and initials fields are never prefilled. Other mapped fields use the stable mapping name configured in the template.

Document Builder sanitizes the editor HTML, creates an A4 PDF with WPsigner’s TCPDF/FPDI engine, and writes it through WPsigner secure storage.

Current generation limits include:

  • 500,000 bytes of document HTML
  • 15 embedded data images
  • 350,000 characters per embedded image
  • Server-level post_max_size and upload limits

Preview links are temporary, bound to the current administrator, and expire after approximately 10 minutes.

  • Creating documents requires the WPsigner create-document capability.
  • Editing checks access to the specific draft.
  • Builder and feed requests use dedicated WordPress nonces.
  • Editor HTML is filtered through an allowlist before PDF generation.
  • Generated PDFs are hashed and stored with WPsigner’s secure-storage controls.
  • Uploaded images use the WordPress Media Library and its upload limits.

See Team Roles & Permissions and System Status, Storage & Retention.

Reload with Ctrl+Shift+R, disable script optimization for the WPsigner admin, and check the browser console for a blocked builder asset.

The body is empty. Add document content before creating the PDF.

Add at least one signer with a valid email

Section titled “Add at least one signer with a valid email”

Return to Signers and correct missing or invalid addresses.

Remove or compress pasted images, use Media Library uploads, simplify the header/footer, and check the server’s post_max_size.

Click Preview PDF again. Preview tokens are intentionally short-lived.

Disable the enabled PDF-template feed or Document Builder feed for that form. Keep only one feed type.

Only a draft created with Document Builder and still linked to its builder source can open in the editor. Sent or completed documents are immutable through this workflow.