# WPsigner Lite Pack
> Only Lite-safe pages: edition both plus Lite hubs (Lite vs Pro, first document). Use this so models do not invent Pro-only features.
Generated for AI assistants from the official WPsigner docs.
HTML guide: https://docs.wpsigner.com/support/use-with-ai/
Pages in this pack: 31
## Suggested prompt
```text
You are helping me configure WPsigner Lite (free WordPress.org edition).
Use ONLY the documentation below as your source of truth.
Each page header includes edition: lite, pro, or both. Never invent Pro-only features for Lite.
If something is not covered, say so clearly and ask for the missing detail.
Prefer exact admin menu paths, shortcodes, endpoints, and settings names from the docs.
```
## Contents
1. [Changelog](https://docs.wpsigner.com/md/changelog.md) — https://docs.wpsigner.com/changelog/
2. [Legal Compliance](https://docs.wpsigner.com/md/compliance.md) — https://docs.wpsigner.com/compliance/
3. [Core Features](https://docs.wpsigner.com/md/core-features.md) — https://docs.wpsigner.com/core-features/
4. [Creating Documents](https://docs.wpsigner.com/md/core-features/creating-documents.md) — https://docs.wpsigner.com/core-features/creating-documents/
5. [Form Fields](https://docs.wpsigner.com/md/core-features/form-fields.md) — https://docs.wpsigner.com/core-features/form-fields/
6. [Security & Compliance](https://docs.wpsigner.com/md/core-features/security-compliance.md) — https://docs.wpsigner.com/core-features/security-compliance/
7. [Signer Workflows](https://docs.wpsigner.com/md/core-features/signer-workflows.md) — https://docs.wpsigner.com/core-features/signer-workflows/
8. [Customization](https://docs.wpsigner.com/md/customization.md) — https://docs.wpsigner.com/customization/
9. [Email Templates](https://docs.wpsigner.com/md/customization/email-templates.md) — https://docs.wpsigner.com/customization/email-templates/
10. [Languages & Translations](https://docs.wpsigner.com/md/customization/languages.md) — https://docs.wpsigner.com/customization/languages/
11. [Digital Identity & Security](https://docs.wpsigner.com/md/digital-identity.md) — https://docs.wpsigner.com/digital-identity/
12. [Audit Trails](https://docs.wpsigner.com/md/digital-identity/audit-trails.md) — https://docs.wpsigner.com/digital-identity/audit-trails/
13. [Digital ID (PKI Certificates)](https://docs.wpsigner.com/md/digital-identity/digital-id.md) — https://docs.wpsigner.com/digital-identity/digital-id/
14. [Document Encryption](https://docs.wpsigner.com/md/digital-identity/encryption.md) — https://docs.wpsigner.com/digital-identity/encryption/
15. [Timestamping (TSA)](https://docs.wpsigner.com/md/digital-identity/timestamping.md) — https://docs.wpsigner.com/digital-identity/timestamping/
16. [Getting Started](https://docs.wpsigner.com/md/getting-started.md) — https://docs.wpsigner.com/getting-started/
17. [First Document on WPsigner Lite](https://docs.wpsigner.com/md/getting-started/first-document-lite.md) — https://docs.wpsigner.com/getting-started/first-document-lite/
18. [Hosting Compatibility](https://docs.wpsigner.com/md/getting-started/hosting-compatibility.md) — https://docs.wpsigner.com/getting-started/hosting-compatibility/
19. [Installing WPsigner](https://docs.wpsigner.com/md/getting-started/installation.md) — https://docs.wpsigner.com/getting-started/installation/
20. [Introduction to WPsigner](https://docs.wpsigner.com/md/getting-started/introduction.md) — https://docs.wpsigner.com/getting-started/introduction/
21. [WPsigner Lite vs Pro](https://docs.wpsigner.com/md/getting-started/lite-vs-pro.md) — https://docs.wpsigner.com/getting-started/lite-vs-pro/
22. [Quick Start Guide](https://docs.wpsigner.com/md/getting-started/quick-start.md) — https://docs.wpsigner.com/getting-started/quick-start/
23. [System Requirements](https://docs.wpsigner.com/md/getting-started/requirements.md) — https://docs.wpsigner.com/getting-started/requirements/
24. [System Status, Storage & Retention](https://docs.wpsigner.com/md/getting-started/system-status-and-storage.md) — https://docs.wpsigner.com/getting-started/system-status-and-storage/
25. [WPsigner Glossary](https://docs.wpsigner.com/md/glossary.md) — https://docs.wpsigner.com/glossary/
26. [WPsigner Documentation](https://docs.wpsigner.com/md/index.md) — https://docs.wpsigner.com/
27. [Support](https://docs.wpsigner.com/md/support.md) — https://docs.wpsigner.com/support/
28. [Frequently Asked Questions](https://docs.wpsigner.com/md/support/faq.md) — https://docs.wpsigner.com/support/faq/
29. [Report a Security Issue](https://docs.wpsigner.com/md/support/security.md) — https://docs.wpsigner.com/support/security/
30. [Troubleshooting](https://docs.wpsigner.com/md/support/troubleshooting.md) — https://docs.wpsigner.com/support/troubleshooting/
31. [Use Documentation with AI](https://docs.wpsigner.com/md/support/use-with-ai.md) — https://docs.wpsigner.com/support/use-with-ai/
---
# Changelog
> Full version history and release notes for WPsigner, with links to the docs guides affected by each release.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/changelog/
Markdown: https://docs.wpsigner.com/md/changelog.md
All notable changes to WPsigner are documented here. Each release lists **Edition** impact (**Lite**, **Pro**, or **Both**) and **Docs** links to the guides you should re-read after updating.
## How to read this changelog
| Label | Meaning |
|-------|---------|
| **Edition: Both** | Behavior exists in Lite and Pro (or shared core) |
| **Edition: Pro** | Requires WPsigner Pro (or a Pro addon / integration) |
| **Edition: Lite** | Affects the free WordPress.org edition |
| **Docs** | Official guides to open after you update |
Compare editions anytime: [Lite vs Pro](/getting-started/lite-vs-pro/). New to WordPress.org? Start with [First Document on Lite](/getting-started/first-document-lite/).
## v3.2.0
**August 22, 2026** · **Edition: Pro**
Unicode signed PDFs, WordPress user picker on Add Signers, and an optional per-signer WordPress login gate. This is the release that includes the work built on top of 3.1.3 (Appearance and Bulk Send stay in that version).
**Docs**
- [Creating Documents](/core-features/creating-documents/)
- [Security & Compliance](/core-features/security-compliance/)
- [Signer Workflows](/core-features/signer-workflows/)
- [Languages](/customization/languages/)
- [Campaigns](/core-features/campaigns/)
**Signed PDF fonts**
- **Languages → Signed PDF fonts** — Optional Noto packs so flattened signed PDFs keep accents and non-Latin scripts. Does not translate the WPsigner screens
- **Packs** — Accented Latin (Vietnamese, Turkish, Polish, and other Latin languages with accents), Japanese, Chinese Simplified, Chinese Traditional, Korean, Arabic, Hebrew, Thai
- **One active pack** — Install only what you need. **Use for signed PDFs** sets the active pack. Files download to `uploads/wps-pdf-fonts/` after install and are not inside the plugin ZIP
**WordPress signers**
- **User search** — Type at least two characters in a signer name or email to pick an existing WordPress user
- **Add me as signer #1** — Fills the first row with the current account. Does not turn on the login gate by itself
- **Signer order** — The first person you add is Signer #1 (their signature fields). Drag rows to change the order
- **Use Template** — Same search and checkbox per slot (for example signer #1 must log in, signer #2 can be a guest)
**WordPress login for a signer**
- **Per signer, off by default** — Check **Require WordPress login with this email**. The email must already belong to a WordPress user (the checkbox is turned off if it does not). The signing token is not enough; the WordPress account email must match that signer
- **Same message on the signing page** — Log in (or log out and switch accounts) and return to the document
- **Does not replace OTP, KYC, or access codes**
- **No campaign hybrid** — An active public campaign cannot share a document with a gated signer, and you cannot turn the checkbox on while a campaign is active. Individual links for those signers are not redirected to the campaign URL. Public reuse of that email still requires the matching WordPress login
- **Bulk Send and public guests** — CSV rows and new public-campaign signers do not get this gate
Download from your [Account Portal](https://app.wpsigner.com/).
## v3.1.3
**August 20, 2026** · **Edition: Both** (Pro 3.1.3, Lite 1.0.2)
Official compatibility with WordPress 7.1 and WooCommerce 11.0.1. WPsigner’s document editor and signing pages are not Gutenberg blocks, so the always-iframed post editor in 7.1 does not affect sending or signing. The WooCommerce integration uses the order API (HPOS) and does not customize the checkout form.
Pro also adds **Appearance** (brand, signing-page buttons, and client portal on one page) and **Bulk Send** (CSV invitations from a template, with a tag you name for each send).
**Docs**
- [Appearance](/customization/appearance/)
- [Bulk Send](/core-features/bulk-send/)
- [Installation](/getting-started/installation/)
- [Whitelabeling](/customization/whitelabeling/)
**Signing page buttons (Pro)**
- **Signing Page tab** — Under **More → Appearance**. Pixel controls for font, padding, corner radius, and border width, plus color, hover, style (solid / outline / soft), weight, and width. S / M / L remain as shortcuts that fill the pixel fields
- **Live preview** — Sidebar mockup updates as you edit, with a light/dark toggle and a contrast warning when text is hard to read
- **Applied everywhere signers tap a primary action** — Finish, Apply, OTP, KYC, the public “start signing” button, and campaign embeds. Decline stays red
- **Brand color finally reaches the signing page** — A custom **Primary Color** from **Appearance → Brand** now styles signing buttons. Stock plugin blue/indigo is unchanged until you save a custom button color
- **Button labels stay in Custom Texts** — Finish, Complete, and Decline copy is still edited there
- **No flash of default styles** — Brand colors, theme, and fonts apply on the first paint so signers do not see a generic look first
- **Appearance hub** — Brand, Signing Page, and Client Portal are tabs on one Appearance page. Previous Signing Appearance and Client Personalization URLs redirect there
**Bulk Send (Pro)**
- **Documents menu** — New **Bulk Send** item next to Documents, plus a button on the Documents list
- **CSV** — Download a sample file (`name`, `email`, optional `title`). Up to 200 rows
- **Batch name = tag** — You name the send; every document in that send gets that tag so you can filter the batch in Documents
- **Emails in batches** — Default 4 per step (1–20). Pause, cancel, or leave the page; leftover batches continue via cron
Download from your [Account Portal](https://app.wpsigner.com/). Lite updates via WordPress.org.
## WPsigner for Uncanny Automator 1.2.0
**August 20, 2026** · **Edition: Pro** (official addon)
Native Uncanny Automator integration: field tokens and prefill, cloud/payment/delete triggers, messaging actions, signer loops, and a settings page for signing-URL privacy.
**Docs**
- [Overview](/addons/uncanny-automator/)
- [Installation](/addons/uncanny-automator-installation/)
- [Triggers](/addons/uncanny-automator-triggers/)
- [Actions](/addons/uncanny-automator-actions/)
- [Tokens](/addons/uncanny-automator-tokens/)
- [Recipe examples](/addons/uncanny-automator-recipes/)
- [Settings](/addons/uncanny-automator-settings/)
- [Security](/addons/uncanny-automator-security/)
- [Troubleshooting](/addons/uncanny-automator-troubleshooting/)
**1.2.0**
- Dynamic template signer-slot hint (AJAX) and up to five signers on create
- Template `FIELD_*` tokens and variable prefill (`key=value` or JSON)
- Triggers for cloud backups, document update/trash/delete, Stripe fail/refund
- Channel reminders (WhatsApp, SMS, Slack, Telegram, Teams) and Slack custom message
- Automator Pro condition “signer is a WordPress user” and loopable signer tokens
- Settings to hide signing URLs and field values; hourly create cap
Previously **1.1.0** added certificate/owner/tag tokens, PDF and Stripe succeeded triggers, tag/signer/expiration actions, and the “document has tag” condition. **1.0.0** was the initial integration.
## v3.1.1
**August 3, 2026** · **Edition: Pro** (forms integrations)
Fluent Forms and WPForms reliability for larger forms with inline signing and OTP, safer signer name detection, and a clearer PDF field editor (name / mapping popup and delete control).
**Docs**
- [Fluent Forms](/integrations/fluent-forms/)
- [WPForms](/integrations/wpforms/)
- [Form Fields](/core-features/form-fields/#field-name-mapping-name-and-placeholder)
- [Creating Documents](/core-features/creating-documents/)
**Forms & OTP**
- **Fluent Forms OTP submit** — Large forms with signature + OTP no longer fail with “Please verify your identity…” after a successful verification. The token is kept through Fluent Forms’ AJAX submit (with a browser-session fallback)
- **Fluent Forms email field** — OTP uses the feed’s mapped signer email instead of guessing the wrong field on complex forms
- **WPForms OTP + feeds** — Same reliability: session OTP fallback, smarter name/email detection (avoids “Username”), OTP only when a signature is present, and content-signing feeds save without forcing a template
- **Signer name field** — Name detection no longer mistakes “Username” for the person name; Fluent Forms `names` (first/last) is preferred
- **Content-signing feed save** — Saving a feed for inline signing no longer asks for a template when Feed Name and Form are already set
**PDF field editor**
- **Field Properties (double-click)** — Set **Field name**, optional **Mapping name** (Zapier / forms / API), and **Placeholder**. Empty mapping uses the field name (slugified). Docs: [Form fields](/core-features/form-fields/#field-name-mapping-name-and-placeholder)
- **Floating popup** — The editor opens outside the field box (not clipped inside it)
- **Delete (X)** — The remove control sits outside the field corner again
**Content signing**
- **Multiple signatures (Fluent Forms / WPForms)** — Forms with several WPsigner Signing fields include every filled signature on the generated PDF, each with its field label
- **Form tags in Documents** — Documents created from form integrations get a tag like “Form: [form name]” (same idea as Campaign tags)
- **Certificate of Completion (forms)** — Signature thumbnails load correctly for content-signing documents; multiple Signing fields appear as separate cards labeled with the form field name (e.g. Client / Witness)
Download from your [Account Portal](https://app.wpsigner.com/).
## v3.1.0
**August 1, 2026** · **Edition: Pro** (portals, campaigns, team roles) · shared admin/diagnostics for Pro installs
A clearer admin experience, better portals, smarter team access, more reliable campaigns, and safer storage tools. Your existing documents and signer data are kept when you update.
**Docs**
- [System Status & Storage](/getting-started/system-status-and-storage/)
- [Client Portal](/core-features/client-portal/)
- [Team Roles & Permissions](/core-features/team-roles/)
- [Campaigns](/core-features/campaigns/)
- [Form Fields](/core-features/form-fields/) (VAT field)
- [Security & Compliance](/core-features/security-compliance/)
- [Languages](/customization/languages/)
**Easier admin screens**
- **System Status** is a practical diagnostics hub (compatibility, storage, cron repair, and cleanup tools when you need them)
- **Storage & Retention** uses the same clear layout as the rest of WPsigner
- **License** page matches the standard WPsigner admin design (activate, verify, renew, and remove license with less confusion)
- **Signer Protection** cards (OTP, KYC, Access Code) line up evenly on Security & Compliance
- Security settings save button stays aligned correctly
**Client Portal and Admin Portal**
- Cleaner Client Portal login and document list (items that need attention appear first)
- Option to hide your theme header and/or footer on portal pages
- “Enable Client Portal” now saves correctly
- Front-end Admin Portal: clearer stats, activity, and “needs attention” view
**Team access that matches each role**
- Dashboard shows all documents for Managers, Viewers, and Admins; Senders still see only their own
- Viewers no longer see a New Document button they cannot use
- Users page works for inSigner Admins (not only WordPress Administrators)
- Clearer “No Access” option when assigning roles
**Campaigns — one completed document per signature**
- Each campaign signature is saved as its own completed document in Documents, with the campaign tag
- Audit trail opened from a submission focuses on that independent signed document (not the shared template)
- Campaign signed PDFs and certificates no longer show the internal “Campaign template” as a signer
- Empty “Pending” boxes from that template no longer appear on campaign PDFs
- Campaign links stay open for many people to sign; the shared template is not closed after the first submission
- Legacy shared-template submissions are promoted to independent documents when you open Submissions, Audit, or Download
**Fields and languages**
- New **VAT** field type available in the PDF editor, campaigns, Document Builder, and the signing page
- Language pack updates correctly overwrite short-locale `.mo` copies and refresh WordPress translation file cache
- Locale fallback prefers regional packs (for example `es_ES`) over stale short codes (`es`)
**Storage — Delete Everything**
- Storage → Delete Everything permanently removes all documents and PDFs (including signed), plus templates, campaigns, submissions, tags, payments, and audit logs
- Runs in safe batches so large libraries do not time out the server; keep the page open until it finishes
- Plugin settings and license are kept
**Signing experience and small fixes**
- Legal Notice from settings is included on the certificate page of the signed PDF
- Telegram Chat ID in the document wizard only appears when Telegram is connected
- Signing page “Page X of N” controls stay readable with common themes (including Astra and WooCommerce)
- Creating and sending signature requests is done in WordPress admin under **New Document**; the front-end Admin Portal is for reviewing status
- Production ZIPs are Linux/WordPress-compatible (forward-slash paths) with UTF-8 encoding verification before packaging
Download from your [Account Portal](https://app.wpsigner.com/).
## v3.0.1 – v3.0.x
**July 2026 (maintenance builds after 3.0.0)** · **Edition: Pro**
Incremental fixes and integration improvements shipped between 3.0.0 and 3.1.0, including Fluent Forms feed UI and OTP, Contact Form 7 parity, WhatsApp Complete Setup, language packs foundation, Storage & Retention tools, and related hardening. These builds are superseded by 3.1.0.
**Docs**
- [Fluent Forms](/integrations/fluent-forms/)
- [Contact Form 7](/integrations/contact-form-7/)
- [WhatsApp](/integrations/whatsapp/)
- [System Status & Storage](/getting-started/system-status-and-storage/)
- [Languages](/customization/languages/)
## v3.0.0
**July 2026** · **Edition: Pro**
Major release with official addons, Fluent Forms content signing, and Stripe improvements.
**Docs**
- [Addons Overview](/addons/overview/)
- [Account Portal](/addons/account-portal/)
- [Smart Signing Forms](/addons/smart-signing-forms/)
- [Fluent Forms](/integrations/fluent-forms/)
- [Stripe](/integrations/stripe/)
- **Addons marketplace** — **WPsigner → Addons** to install and activate official extensions
- **Account Portal integration** — Download addons from [app.wpsigner.com](https://app.wpsigner.com/account/?portal_tab=addons)
- **Smart Signing Forms** (addon v1.6.0) — Drag-and-drop signing forms with design presets, OTP, Stripe payments, and signed PDF output
- **Fluent Forms content signing** — Sign inline with the WPsigner Signing field; PDF generated from form content without a template feed
- **Fluent Forms OTP** — Email, SMS, and WhatsApp verification on the Signing field before submit
- **Fluent Forms merge tags** — `{inSigner:signed_pdf_url}` and `{inSigner:download_button}` in notification emails
- **Stripe** — Server-side PaymentIntent verification, webhook hardening, restricted API keys (`rk_*`) recommended
- Submission blocked when content-signing PDF generation fails (no orphaned Fluent Forms entries)
- Security and compatibility improvements across signing and integrations
Download from your [Account Portal](https://app.wpsigner.com/).
### Smart Signing Forms v1.6.0 (addon)
**Edition: Pro** · **Docs:** [Smart Signing Forms](/addons/smart-signing-forms/)
- 4-step wizard: configuration, form builder, design presets with live preview, compliance
- Field types: signature, payment (Stripe), OTP, columns, conditionals, file upload, and more
- Stripe Payment Element flow with server-side payment verification before PDF generation
- Entry management with signed PDF download and audit trail links
## v2.5.0
**June 10, 2026** · **Edition: Both** (field editor / signing UX) · **Pro** addons page
A major update to the field editor and the signing experience.
**Docs**
- [Form Fields](/core-features/form-fields/)
- [Creating Documents](/core-features/creating-documents/)
- [First Document on Lite](/getting-started/first-document-lite/)
- [Quick Start](/getting-started/quick-start/)
- [Addons Overview](/addons/overview/)
- **Checkbox groups** — place checkboxes anywhere on the PDF and set optional, “pick at least one”, or “pick exactly one” rules.
- **Conditional fields** — show, hide, or require fields based on what the signer answers.
- **Right-click menu** on fields to clone, delete, or change checkbox options.
- **Checkbox stamp mode** — drop one checkbox, then click to add more. Press Escape when you’re done.
- **Custom labels and placeholders** — double-click any field to edit.
- **Addons page** — Smart Signing Forms available; Flow Builder coming soon.
- Better signing page on mobile, especially for long PDFs.
- Fields stay in place when you zoom in the editor.
- Dates and times now match your WordPress site timezone everywhere.
- Saves no longer lose fields on multi-page documents.
- Public document verification page works reliably.
- Signing links and PDF viewing work better with caching and security plugins.
Download from your [license portal](https://app.wpsigner.com/).
## v2.4.0
**April–May 2026** · **Edition: Pro**
Interim release with webhook reliability, admin tooling, and integration prep ahead of the 2.5.0 field-editor work.
**Docs:** [Webhooks](/api/webhooks/) · [REST API](/api/)
## v2.3.1
**March 4, 2026** · **Edition: Pro** (API / webhooks) · shared signing hardening
Security and reliability improvements:
**Docs:** [REST API](/api/) · [Webhooks](/api/webhooks/) · [Security & Compliance](/core-features/security-compliance/)
- Stronger protection for API access and signing order.
- Webhooks fire correctly again when documents are signed or completed.
- Better IP detection when your site uses Cloudflare or a CDN.
- Safer storage for certificates and integration credentials.
- General hardening across the signing page and admin.
## v2.3.0
**February 24, 2026** · **Edition: Pro**
**Docs:** [Didit](/integrations/didit/) · [Twilio](/integrations/twilio/) · [Security & Compliance](/core-features/security-compliance/)
- **Identity verification with Didit.me.** Signers can now verify their identity with a government ID, selfie, and liveness check before signing. You set it up once and get real-time status updates.
- **SMS verification via Twilio.** Signers can verify by text message, email, or both.
- New option in settings to choose how verification codes are delivered.
- The signing page now adapts based on the verification method you've picked.
## v2.2.3
**February 12, 2026**
- Encryption is now set up automatically when you install the plugin. One less thing to configure.
- Fixed Google Drive disconnecting when the token expired. Reconnection is handled automatically now.
- Admin notices now link directly to the relevant setup guide instead of a generic settings page.
## v2.2.2
**January 30, 2026**
- Redesigned the timestamp verification email. Much clearer now.
- Blockchain verification links open a clean branded page instead of a raw URL.
- Fixed an edge case where some timestamp providers were incorrectly filtered out.
## v2.2.1
**January 20, 2026**
- IP detection now works correctly when your site is behind Cloudflare, load balancers, or reverse proxies.
- All parts of the plugin now use the same IP source, so rate limiting and audit logs stay consistent.
- Added support for custom proxy headers if your hosting setup needs it.
## v2.2.0
**January 8, 2026**
Big encryption upgrade. Your stored credentials are now much more secure.
- Encryption keys come from your site's unique WordPress configuration instead of the database.
- Certificate passwords use stronger encryption with unique keys for each operation.
- Tighter file validation across uploads, downloads, and templates.
- Location lookups are encrypted in transit.
- You'll see a warning if encryption keys change after a site migration.
## v2.1.1
**December 18, 2025**
- Fixed a crash on mobile with large PDFs (100+ pages).
- Pages now load as you scroll, so your device doesn't run out of memory.
- Automatic cleanup for pages you've scrolled past.
- Better performance on lower-end phones and tablets.
## v2.1.0
**December 2, 2025**
- Rate limiting on all API and integration endpoints.
- Security review of every admin form and input field.
- Third-party credentials (API keys, tokens) are now stored encrypted.
- Plugin uses ~12% less memory.
## v2.0.2
**November 15, 2025**
- Reorganized the integrations page by category: Forms, Messaging, Automation, CRM, Cloud Storage.
- Added "coming soon" labels for Make, n8n, Telegram, Gravity Forms, Dropbox, and Teams.
- New card designs with official brand icons for each integration.
## v2.0.1
**October 28, 2025**
- Fixed PDF viewer not loading on some shared hosting setups.
- Fixed WhatsApp templates breaking when document titles have special characters.
- Better loading indicators for documents over 20 pages.
## v2.0.0
**October 6, 2025**
Biggest release since launch.
- **WhatsApp Business.** Send signing requests, reminders, and completion notifications via WhatsApp.
- **Integrations Hub.** New admin page showing all integrations and their connection status.
- **Google Drive.** One-click setup. Signed PDFs are saved to your Drive automatically.
- **License System.** Manage plugin licenses through WooCommerce.
- Smoother mobile signing with larger buttons and better scrolling.
## v1.9.1
**September 8, 2025**
- Signers now see the full document first instead of being auto-scrolled to the first field.
- Better keyboard navigation and accessibility across the signing page.
- Fixed a validation issue with the consent checkbox on Safari and iOS.
## v1.9.0
**August 11, 2025**
- **OTP Verification.** Signers confirm their identity via email before signing.
- **Location capture.** Optionally log where signers are located for richer audit trails.
- Browser, platform, and timezone are now included in the audit trail.
- Consent checkbox gets its own timestamp for compliance records.
## v1.8.0
**June 23, 2025**
- **REST API.** Full API with key management, permissions, and rate limits.
- **Zapier integration.** Connect WPsigner to 6,000+ apps with real-time triggers and actions.
- API documentation with examples in PHP, JavaScript, Python, and cURL.
- Cleaner email templates.
## v1.7.0
**May 5, 2025**
- **Roles.** 4 roles: Sender, Viewer, Manager, Admin. Each with specific permissions.
- Download links for signed documents now expire after 48 hours.
- You can add custom messages to signing request emails.
- More reliable auto-reminders, even on sites with inconsistent WordPress cron.
## v1.6.0
**March 17, 2025**
- **Translations.** English, Spanish, Italian, French, German, and Portuguese (Brazil).
- All fonts and scripts are self-hosted. No external requests, fully GDPR compliant.
- Pages load ~300ms faster.
## v1.5.0
**February 3, 2025**
- **Digital ID.** Generate a self-signed certificate directly from the settings page.
- **Elementor Forms** and **Fluent Forms** integrations. Turn form submissions into signing documents.
- New system status page with a health score, auto-fix tools, and debug export.
- Dashboard widget showing health score and pending reminders.
## v1.4.0
**December 16, 2024**
- **Security Center.** New settings page with a real-time compliance score.
- Upload your own certificates for Adobe-verified digital signatures.
- Timestamp Authority integration for legally provable signing times.
- 6-digit access codes for sensitive documents.
- Compliance badges for ESIGN Act, eIDAS, and UETA.
## v1.3.0
**October 28, 2024**
- **Webhooks.** Get real-time notifications when documents are signed, viewed, or completed.
- Compatibility fixes for WP Rocket, LiteSpeed Cache, and Autoptimize.
- Added Portuguese (Brazil), French, and German translations.
## v1.2.0
**September 2, 2024**
- **Document Wizard.** 4-step guided flow: Upload, Signers, Fields, Review.
- Sequential signing: set a strict order or let everyone sign at the same time.
- One-click copy for signing links after sending a document.
- White-label: use your own logo, colors, and footer text.
## v1.1.0
**August 4, 2024**
- Multi-signer support. Up to 6 signers per document.
- Color-coded fields so each signer's fields are easy to identify.
- Quick-share modal for signing links.
## v1.0.0
**July 15, 2024**
Initial release.
- PDF upload with drag-and-drop.
- Electronic signatures: draw, type, or upload an image.
- Form fields: signature, initials, date, text, checkbox.
- Automatic email notifications for signing requests and completions.
- Audit trail with timestamps, IP addresses, and action logging.
- PDF certificate of completion with QR code verification.
- Works on desktop, tablet, and mobile.
---
# Legal Compliance
> Complete guide to electronic signature laws, regulations, and compliance standards for ESIGN, UETA, eIDAS, HIPAA, and more.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/compliance/
Markdown: https://docs.wpsigner.com/md/compliance.md
WPsigner provides technical controls that can support an electronic-signature compliance program. This page summarizes major frameworks and maps relevant WPsigner features; it is not a certification that every installation or transaction is compliant.
## Electronic Signature Laws
### United States
#### ESIGN Act (2000)
The **Electronic Signatures in Global and National Commerce Act** establishes that:
| Requirement | Meaning |
|-------------|---------|
| Legal equivalence | E-signatures have same legal weight as handwritten |
| Intent | Signer must intend to sign |
| Consent | Parties must agree to use electronic format |
| Record retention | E-records must be accurately retained |
**Relevant WPsigner controls:**
- Signing actions and consent records
- Audit trails and retained document records
- Identity and access gates when configured
#### UETA (1999)
The **Uniform Electronic Transactions Act** is adopted by 49 states (all except New York, which has similar laws):
| Principle | WPsigner Support |
|-----------|------------------|
| E-signature validity | Signature workflow and consent evidence |
| E-record validity | PDF storage with audit trail |
| Attribution | Email, access, optional OTP/KYC, and audit evidence |
| Effect of change | Hashing and optional certificate signature help detect changes |
### European Union
#### eIDAS Regulation (2014/910)
The EU's **electronic IDentification, Authentication and trust Services** regulation defines three signature levels:
| Level | Description | Legal Effect | WPsigner |
|-------|-------------|--------------|----------|
| **SES** (Simple) | Any electronic signature | Valid, may need additional evidence | Basic WPsigner workflows can produce SES evidence |
| **AdES** (Advanced) | Uniquely linked to signer and capable of identifying them, under their control, with change detection | Stronger evidence | WPsigner controls can contribute; all legal criteria must still be met |
| **QES** (Qualified) | AdES + qualified certificate + qualified creation process/provider | Equivalent to handwritten across the EU | Requires a QTSP and qualified process outside a normal plugin configuration |
**Configuration orientation (not certification):**
```
┌─────────────────────────────────────────────────────────┐
│ QES (Qualified) │
│ • Qualified certificate and process from a QTSP │
│ • Cannot be established by an AATL certificate alone │
├─────────────────────────────────────────────────────────┤
│ AdES-oriented controls │
│ • Strong signer identification and control │
│ • Unique linkage plus change detection │
│ • Must satisfy every eIDAS criterion │
├─────────────────────────────────────────────────────────┤
│ SES-oriented workflow │
│ • Basic WPsigner signatures │
│ • Audit trail with IP and device info │
└─────────────────────────────────────────────────────────┘
```
### Other Regions
| Country/Region | Law | Status |
|----------------|-----|--------|
| **United Kingdom** | UK eIDAS / ECA 2000 | ✅ Recognized |
| **Canada** | PIPEDA + Provincial | ✅ Recognized |
| **Australia** | Electronic Transactions Act 1999 | ✅ Recognized |
| **India** | IT Act 2000 | ✅ Recognized |
| **Brazil** | MP 2.200-2/2001 | ✅ Recognized |
---
## Industry Regulations
### Healthcare (HIPAA)
The **Health Insurance Portability and Accountability Act** applies to Protected Health Information (PHI):
| HIPAA Requirement | WPsigner Solution |
|-------------------|-------------------|
| Access controls | Role-based WordPress permissions |
| Audit controls | Complete audit trail logging |
| Integrity controls | Digital signatures detect tampering |
| Transmission security | HTTPS encryption (your server) |
| Business Associate Agreement | Required with hosting provider |
**HIPAA Compliance Checklist:**
- [ ] Host on HIPAA-compliant infrastructure
- [ ] Configure OTP verification
- [ ] Enable Digital ID signing
- [ ] Enable audit trail with geolocation
- [ ] Sign BAA with hosting provider
- [ ] Implement access controls
- [ ] Train staff on procedures
> **important**
WPsigner provides technical controls. You are responsible for administrative and physical safeguards and, where required, appropriate agreements with hosting and service providers.
### Financial Services (SOX, FINRA)
| Requirement | WPsigner Feature |
|-------------|------------------|
| **SOX 802** - Record retention | Permanent document storage |
| **SOX 802** - Integrity | Digital signatures, tampering detection |
| **FINRA 4511** - Books and records | Timestamped audit trails |
| **FINRA 3110** - Supervision | Audit logs show who signed what |
### Legal (ABA Guidelines)
The American Bar Association recognizes e-signatures for:
- Client engagement letters
- Contracts and agreements
- Settlement agreements
- Non-disclosure agreements
**Best practices for legal documents:**
1. Enable Digital ID (PKI certificate)
2. Enable timestamping (TSA)
3. Use sequential signing for approval chains
4. Keep complete audit trails
### Real Estate (RESPA, TRID)
Many real estate documents can be signed electronically:
| ✅ Allowed | ⚠️ May Require Wet Signature |
|-----------|------------------------------|
| Purchase agreements | Deeds (varies by state) |
| Listing agreements | Notarized documents |
| Lease agreements | Some title documents |
| Addendums | |
---
## Key Compliance Features
### 1. Digital Signatures (PKI)
Cryptographic signatures that prove:
- **Authenticity** - Who signed
- **Integrity** - Document not altered
- **Non-repudiation** - Signer cannot deny signing
Configure at: **WPsigner → More → Digital ID**
### 2. Timestamping (TSA)
RFC 3161 timestamps prove:
- **Exact signing time** - From trusted third party
- **Long-term validity** - Valid after certificate expires
Configure at: **WPsigner → Settings → Legal & Privacy**
### 3. Audit Trails
Every document includes:
- All signer actions with timestamps
- IP addresses and device information
- Consent records
- Viewing history
See: [Audit Trails Documentation](/digital-identity/audit-trails/)
### 4. Identity Verification
Multiple verification methods:
- **Email verification** - Link only works for recipient
- **OTP verification** - Code sent to signer's email
- **PIN protection** - Additional access code
### 5. Certificate of Completion
Every completed document includes:
- Summary of all signatures
- Complete audit trail
- Compliance attestation
---
## Signature Validity by Document Type
### Generally Accepted
| Document Type | Notes |
|---------------|-------|
| Contracts | All jurisdictions |
| NDAs | All jurisdictions |
| Employment agreements | All jurisdictions |
| Service agreements | All jurisdictions |
| Purchase orders | All jurisdictions |
| Terms and conditions | All jurisdictions |
| Client proposals | All jurisdictions |
| HR documents | Most jurisdictions |
### May Require Special Handling
| Document Type | Consideration |
|---------------|---------------|
| Real estate deeds | Check state requirements |
| Wills and testaments | Often require witnesses/notarization |
| Court documents | Check local rules |
| Powers of attorney | Varies by jurisdiction |
| Healthcare directives | May require witnesses |
### Typically Require Wet Signature
| Document Type | Reason |
|---------------|--------|
| Notarized documents | Physical notary required |
| Some government forms | Specific requirements |
| Certain immigration forms | Federal requirements |
---
## Compliance Checklist
### Basic Compliance (SES)
- [x] WPsigner installed and configured
- [x] HTTPS enabled on your site
- [x] Audit trail enabled (default)
- [x] Documents stored securely
- [x] Access controls in place
### Enhanced Compliance (AdES)
- [ ] Digital ID configured
- [ ] OTP verification enabled
- [ ] Timestamping enabled
- [ ] Advanced audit trail (geolocation, device)
- [ ] Document retention policy defined
### Maximum Compliance (QES-ready)
- [ ] All AdES requirements
- [ ] Commercial AATL certificate from QTSP
- [ ] Identity verification procedures
- [ ] Staff training documented
- [ ] Compliance policies written
---
## Compliance Score
WPsigner displays a Compliance Score in **More → Security & Compliance**:
| Score | Level | Features Enabled |
|-------|-------|------------------|
| **Basic (SES)** | Simple Electronic Signature | Default configuration |
| **Enhanced (SES+)** | Enhanced Simple | + Identity verification |
| **Advanced (AdES)** | Advanced Electronic Signature | + Digital ID + TSA + OTP |
---
## Legal Disclaimer
> **caution**
This documentation provides general information about electronic signature laws and is not legal advice. Laws vary by jurisdiction and change over time. Consult with a qualified attorney for requirements applicable to your situation.
WPsigner provides technical tools for compliance. You are responsible for:
- Understanding applicable regulations
- Configuring appropriate security settings
- Implementing proper procedures
- Training your staff
- Maintaining documentation
---
## Next Steps
- [Digital ID Configuration](/digital-identity/digital-id/) - Set up PKI certificates
- [Timestamping](/digital-identity/timestamping/) - Enable RFC 3161 timestamps
- [Audit Trails](/digital-identity/audit-trails/) - Understanding the legal record
- [FAQ](/support/faq/) - Common compliance questions
---
# Core Features
> Learn how to create documents, bulk-send from a CSV, manage campaigns, configure signer workflows, and use form fields in WPsigner.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/core-features/
Markdown: https://docs.wpsigner.com/md/core-features.md
WPsigner's core features cover the document signing lifecycle — from uploading a PDF and placing fields to multi-signer workflows. Some items below (campaigns, client portal, team roles) require **Pro**. Shared document tools work in **Lite** within published limits. See [Lite vs Pro](/getting-started/lite-vs-pro/).
---
## Feature Guides
| Guide | Description | Edition |
|-------|-------------|---------|
| [Creating Documents](/core-features/creating-documents/) | Upload PDFs, add signers (including WordPress users), position fields, and send | Lite + Pro |
| [Bulk Send](/core-features/bulk-send/) | Invite many people from a CSV using one template; tag each batch | Pro |
| [Campaigns (Public Links)](/core-features/campaigns/) | Reusable public signing links | Pro |
| [Client Portal](/core-features/client-portal/) | Admin and signer dashboards on your site | Pro |
| [Team Roles & Permissions](/core-features/team-roles/) | Sender, Viewer, Manager, and Admin access matrix | Pro |
| [Security & Compliance](/core-features/security-compliance/) | OTP, access codes, WordPress login, evidence, certificates, timestamps | Lite + Pro (advanced options in Pro) |
| [Signer Workflows](/core-features/signer-workflows/) | Signer order, parallel vs sequential, per-signer WordPress login | Lite + Pro |
| [Form Fields](/core-features/form-fields/) | Signature, text, date, checkbox, and more | Lite + Pro |
---
## How Documents Work
The document lifecycle in WPsigner follows a straightforward flow:
```
Upload PDF → Add Signers → Place Fields → Send → Signers Sign → Document Completed
```
### Document Statuses
| Status | Meaning |
|--------|---------|
| **Draft** | Document created but not yet sent |
| **Sent** | Emails delivered, waiting for signatures |
| **Viewed** | At least one signer has opened the signing page |
| **Completed** | All signers have signed — PDF is sealed |
| **Declined** | A signer declined to sign |
| **Expired** | Signing deadline passed before completion |
---
## Documents, Bulk Send, and Campaigns
WPsigner offers three ways to collect signatures:
| Feature | Standard Documents | Bulk Send | Campaigns |
|---------|-------------------|-----------|-----------|
| **Signers** | Named (email required) | Named list from a CSV | Anyone with the link |
| **Use case** | Contracts, a few specific parties | Same template, many known people | Waivers, consent forms, open enrollment |
| **Tracking** | Per-signer status, individual emails | One document + tag per row | Per-submission, shared URL |
| **Limit** | Lite: max 2 signers; Pro: unlimited | **Pro**, 200 rows per send | Unlimited submissions per campaign (**Pro**) |
---
## Quick Links
- **New to WPsigner?** Start with [Creating Documents](/core-features/creating-documents/) to learn the 4-step wizard. Pick WordPress users, add yourself as signer #1, or require a matching WordPress login on a row.
- **Same template, many emails?** Use [Bulk Send](/core-features/bulk-send/).
- **Need reusable public links?** See [Campaigns](/core-features/campaigns/) for shareable signing URLs.
- **Adding a team?** Use [Team Roles & Permissions](/core-features/team-roles/) before granting access.
- **Need stronger signer verification?** Configure [Security & Compliance](/core-features/security-compliance/).
- **Multiple signers?** Read [Signer Workflows](/core-features/signer-workflows/) to configure parallel or sequential signing.
- **Custom fields?** The [Form Fields](/core-features/form-fields/) reference covers every field type with positioning tips.
---
# Creating Documents
> Upload a document, add signers (including WordPress users), place fields, and send. Covers signer order, Add me as signer #1, and optional WordPress login.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/core-features/creating-documents/
Markdown: https://docs.wpsigner.com/md/core-features/creating-documents.md
The document creation wizard guides you through a 4-step process to prepare any document for electronic signatures. This page covers each step in detail.
> **Lite limits**
On **Lite**: upload **PDF only** and invite at most **two** signers. Image uploads, unlimited signers, and reusable templates require **Pro**. [Compare editions](/getting-started/lite-vs-pro/) · [Upgrade to Pro](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=upgrade&utm_campaign=creating-documents)
## The 4-Step Document Wizard
| Step | Name | Purpose |
|------|------|---------|
| 1 | **Upload** | Add your PDF or image file |
| 2 | **Signers** | Add people who need to sign |
| 3 | **Fields** | Place signature and form fields |
| 4 | **Review** | Preview and send |
---
## Step 1: Upload Document
### Accessing the Wizard
1. Go to **WPsigner** in the WordPress admin sidebar
2. Click **New Document** or the **"+"** button
3. The upload screen appears
### Supported File Formats
| Format | Extension | Best For |
|--------|-----------|----------|
| **PDF** | .pdf | Contracts, agreements, multi-page documents |
| **PNG** | .png | High-quality images, graphics |
| **JPEG** | .jpg, .jpeg | Photos, scanned documents |
> **tip**
PDF is the recommended format. It preserves formatting, supports multiple pages, and is widely used for agreements.
### Upload Methods
**Drag & Drop**
1. Drag your file from your computer
2. Drop it into the upload zone
3. Wait for the upload progress to complete
**Click to Browse**
1. Click anywhere in the upload zone
2. Select your file from the file browser
3. Click **Open** to upload
### File Size Limits
| Setting | Default | Recommended |
|---------|---------|-------------|
| Max file size | Server-dependent | 64MB |
| Max pages | Unlimited | Any |
If your file is too large, you'll see an error. Contact your hosting provider to increase the `upload_max_filesize` PHP setting.
### Document Preview
After upload, you'll see:
- Thumbnail preview of the first page
- File name and size
- Page count (for PDFs)
- Option to remove and re-upload
---
## Step 2: Add Signers
### Signer Information
For each signer, you can provide:
| Field | Required | Description |
|-------|----------|-------------|
| **Name** | ✅ Yes | Display name for the signer |
| **Email** | ✅ Yes | Where signing request is sent |
| **Phone** | No | For SMS notifications (if enabled) |
| **Role** | No | Custom label (e.g., "Buyer", "Witness") |
| **Require WordPress login** | No | Off by default. When checked, that email must already belong to a WordPress user, and that signer must be logged in with that account. If the email has no account, the checkbox is turned off. The signing link alone will not open the document |
### Signer order and signature fields
The **order you add people** is the signer slot used for fields:
- The first row is **Signer #1** (blue) — their signature, initials, and other fields
- The second row is **Signer #2** (green), then Signer #3, and so on
- Drag a row to change who is #1, #2, #3
- **Add me as signer #1** only fills that first row. If someone else should sign first, put them in row 1 (or drag them to the top)
**Sequential** invitations follow this same list. **Parallel** invites everyone at once, but fields still belong to those slots.
### Adding Your First Signer
1. Enter the signer's **Name**, or type two characters and pick a [WordPress user](#wordpress-users)
2. Enter their **Email** address (filled automatically if you pick a user)
3. (Optional) Add their **Phone** number
4. (Optional) Assign a **Role** label
5. (Optional) Check **Require WordPress login with this email** if they must sign in with a matching WordPress account
### Adding Multiple Signers
Click **Add Signer** to add more people:
1. A new signer row appears
2. Fill in their details
3. Each signer gets a unique color for field assignment
4. Drag signers to reorder (for sequential signing and for which slot owns which fields)
### Signer Colors
Each signer is automatically assigned a color:
| Signer | Color |
|--------|-------|
| Signer 1 | 🔵 Blue |
| Signer 2 | 🟢 Green |
| Signer 3 | 🟠 Orange |
| Signer 4 | 🟣 Purple |
| Signer 5+ | Auto-assigned |
These colors help you identify which fields belong to which signer when placing fields.
### Signing Order
Choose how signers receive the document:
**Parallel Signing** (Default)
- All signers receive the email at the same time
- Anyone can sign in any order
- Fastest completion time
**Sequential Signing**
- Signers receive emails in order
- Signer 2 only gets the email after Signer 1 completes
- Use drag handles to reorder signers
- Perfect for approval chains
### WordPress users
These options are in **WPsigner Pro 3.2.0+**, on **Add Signers** and in the **Use Template** modal.
**Pick an existing user**
1. Type at least two characters in the name or email field
2. Choose the WordPress user from the list (up to 20 matches)
3. Name and email fill in. You can still type a guest if they are not a WordPress user
**Add me as signer #1**
Check **Add me as signer #1** to fill the first row with the logged-in account. That does **not** turn on the login gate.
**Require WordPress login with this email**
Check it on each signer who must prove they own that WordPress account:
- The email must already be a WordPress user. WPsigner does not create the account
- If the email has no account, you see an alert and the checkbox stays off
- The signing link alone will not open the document — they must be logged in, and the account email must match
- You can require login for signer #1 and leave signer #2 as a guest
This gate is separate from OTP, KYC, and access codes. It does not apply to [public campaign links](/core-features/campaigns/) or [Bulk Send](/core-features/bulk-send/) CSV invitations. Details: [Security & Compliance](/core-features/security-compliance/#wordpress-login-per-signer).
### Advanced Options
**Access Code (PIN)**
Enable to require signers to enter a PIN before viewing the document:
1. Check "Require Access Code"
2. Enter a PIN (or auto-generate)
3. Share the PIN with the signer separately
**Expiration Date**
Set a deadline for signing:
1. Enable "Set Expiration"
2. Choose a date
3. After this date, the signing link becomes invalid
---
## Step 3: Place Fields
### The Field Editor
The field editor displays:
- **Left sidebar**: Available field types
- **Center**: Document preview with pages — place and move fields here
### Available Field Types
| Field | Purpose | Required Input |
|-------|---------|----------------|
| **Signature** | Full signature capture | Draw or type signature |
| **Initials** | Smaller initial box | Draw or type initials |
| **Date** | Date field | Auto-filled or manual |
| **Text** | Single-line input | Type text |
| **Text Area** | Multi-line input | Type paragraph |
| **Checkbox** | Yes/No selection | Click to toggle |
| **Dropdown** | Select from options | Choose from list |
| **VAT** | Tax / VAT identifier | Type VAT number |
### Placing Fields
**Method 1: Click to Place**
1. Click a field type in the toolbar
2. Click on the document where you want it
3. The field appears at that location
**Method 2: Drag and Drop**
1. Drag a field type from the toolbar
2. Drop it on the desired location
3. Release to place
### Naming and mapping fields (double-click)
**Double-click** any placed field to open **Field Properties**:
| Setting | Purpose |
|---------|---------|
| **Field name** | Label you see on the field in the editor |
| **Mapping name** | Key for Zapier, form integrations, and the API. Leave empty to use the field name |
| **Placeholder** | Hint text for the signer (text-like fields) |
Hover a field to show the red **X** outside the top-right corner to delete it. Dropdown / radio / checkbox-group fields open their options editor instead of Field Properties.
Full details: [Form fields — Field name, mapping name, and placeholder](/core-features/form-fields/#field-name-mapping-name-and-placeholder).
### Configuring Fields
- Drag to move; use the corner handle to resize
- Right-click for actions such as clone, delete, or conditional logic (when available)
- Assign the active signer with the signer buttons before placing fields (each signer has a color)
**Field-specific options**
*Dropdown / radio / checkbox group*
- Double-click to edit the list of options
*Text-like fields*
- Use Field Properties for name, mapping name, and placeholder
### Multi-Page Navigation
For documents with multiple pages:
1. Use the page arrows at the bottom
2. Or click page thumbnails (if visible)
3. Place fields on any page
4. Field counts shown per page
### Field Alignment
For professional-looking documents:
- Fields snap to common positions
- Use rulers for precise placement
- Align multiple fields using guides
---
## Step 4: Review & Send
### Pre-Send Checklist
Before sending, verify:
- ✅ Document uploaded correctly
- ✅ All signers added with valid emails
- ✅ All required fields placed
- ✅ Fields assigned to correct signers
- ✅ Signing order configured (if sequential)
### Document Summary
The review screen shows:
- Document preview
- List of signers with their fields
- Signing workflow type
- Expiration date (if set)
### Personal Message
Add a custom message that appears in the signing request email:
1. Enter your message in the text box
2. This replaces the default email body
3. Keep it professional and clear
**Example messages:**
- "Please review and sign this contract at your earliest convenience."
- "Attached is the service agreement we discussed. Let me know if you have questions."
### Sending Options
**Send Now**
- Click **Send Document**
- Emails are dispatched immediately
- You're redirected to the document dashboard
**Save as Draft**
- Click **Save Draft**
- Document is saved but not sent
- Resume editing later from Documents list
---
## After Sending
### Document Status
Your document moves through these statuses:
| Status | Meaning |
|--------|---------|
| **Draft** | Not yet sent, can be edited |
| **Sent** | Emails delivered, awaiting signatures |
| **Viewed** | At least one signer opened the link |
| **Partially Signed** | Some signers have completed |
| **Completed** | All signers finished |
| **Declined** | A signer refused to sign |
| **Expired** | Past expiration date |
| **Voided** | Cancelled by document owner |
### Tracking Progress
From the Documents list:
1. See status at a glance with color indicators
2. Click to view detailed progress
3. See which signers have viewed/signed
4. Access audit trail
### Available Actions
| Action | When Available | Effect |
|--------|----------------|--------|
| **Resend** | After sending | Re-sends email to pending signers |
| **Remind** | Sent status | Sends reminder email |
| **Void** | Before completion | Cancels the document |
| **Download** | After completion | Gets signed PDF |
| **View Audit** | Any time | Shows detailed history |
---
## Document Templates
Save time by creating reusable templates.
### Creating a Template
1. Create a document with all fields placed
2. Before sending, click **Save as Template**
3. Enter a template name
4. Template is saved for future use
### Using a Template
1. Click **New Document**
2. Select **From Template**
3. Choose your template
4. Only enter signer details — row 1 is always the template’s Signer #1 fields, row 2 is Signer #2, and so on
5. Search WordPress users, use **Add me as signer #1**, or require WordPress login on any row
6. Fields are already placed!
### Template Benefits
- Pre-configured field placement
- Consistent signer roles
- Faster document creation
- Team-wide standardization
To invite many people from a spreadsheet using the same template, use [Bulk Send](/core-features/bulk-send/). Each row becomes its own document and is tagged with the name you give that send.
---
## Best Practices
### Document Preparation
- **Use high-quality PDFs** - Ensure text is readable
- **Leave space for signatures** - Don't crowd signature areas
- **Include clear instructions** - Add signing instructions in the document itself
- **Test first** - Send a test document to yourself
### Signer Experience
- **Use full names** - "John Smith" not "J. Smith"
- **Verify emails** - Double-check email addresses
- **Explain the process** - First-time signers may need guidance
- **Set reasonable deadlines** - Give signers adequate time
### Field Placement
- **Align with printed lines** - Place fields on existing signature lines
- **Size appropriately** - Signatures need room, dates can be smaller
- **Mark required fields** - Ensure critical fields can't be skipped
- **Test on mobile** - Fields should be accessible on small screens
---
## Troubleshooting
### "Upload failed"
- Check file size limits
- Verify file is not corrupted
- Try a different browser
### "Signer not receiving email"
- Verify email address is correct
- Check spam/junk folder
- Use the Resend option
- Verify SMTP is configured
### "Fields not visible"
- Ensure you're on the correct page
- Check if fields are assigned to a signer
- Zoom in on the document view
### "No WordPress account uses this email"
- Create the WordPress user first, or leave **Require WordPress login** off
- Confirm the signer email matches the account email exactly (case does not matter)
### Vietnamese or accented names look wrong on the signed PDF
- Install **Accented Latin** under **WPsigner → Languages → Signed PDF fonts**
- Click **Use for signed PDFs**
- Guide: [Languages & Translations](/customization/languages/#signed-pdf-fonts)
---
## Next Steps
- [Signer Workflows](/core-features/signer-workflows/) - Signer order, sequential vs parallel
- [Form Fields](/core-features/form-fields/) - All field types explained
- [Security & Compliance](/core-features/security-compliance/#wordpress-login-per-signer) - Per-signer WordPress login
- [Languages](/customization/languages/#signed-pdf-fonts) - Vietnamese and other signed-PDF fonts
- [Bulk Send](/core-features/bulk-send/) - Same template, many emails from a CSV
- [Email Templates](/customization/email-templates/) - Customize signing emails
- [Appearance](/customization/appearance/) - Brand the signing page
---
# Form Fields
> Complete reference for all form field types available in WPsigner documents.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/core-features/form-fields/
Markdown: https://docs.wpsigner.com/md/core-features/form-fields.md
WPsigner provides a variety of form fields for capturing signer information. This page covers each field type, its properties, and best practices for placement.
## Field Types Overview
| Field Type | Purpose | Signer Action |
|------------|---------|---------------|
| **Signature** | Legal signature capture | Draw or type |
| **Initials** | Abbreviated signature | Draw or type initials |
| **Text** | Single-line input | Type text |
| **Number** | Numeric value | Enter digits |
| **Date** | Date entry | Auto-fill or select |
| **Name** | Full name | Type a name |
| **Email** | Email address with validation | Type an email |
| **Phone** | Telephone number | Type a phone number |
| **Company** | Organization name | Type a company |
| **VAT** | Tax/VAT identifier | Type an identifier |
| **Title** | Job title or position | Type a title |
| **Text Area** | Multi-line input | Type paragraph |
| **Checkbox** | Boolean selection | Click to toggle |
| **Checkbox Group** | Select one or more options | Check options |
| **Radio** | Select one option | Choose an option |
| **Dropdown** | Choice from list | Select option |
| **Attachment** | Supporting file | Upload a file |
| **Label** | Display-only instructions | No input |
| **Payment** | Collect payment when the payment integration is enabled | Complete payment |
> **note**
Some field types appear only when the related feature is available. For example, **Payment** depends on a configured payment integration.
---
## Signature Field
The most important field type - captures the signer's legal signature.
### Signature Options for Signers
When completing a signature field, signers can choose:
| Method | Description |
|--------|-------------|
| **Draw** | Use mouse, finger, or stylus to draw |
| **Type** | Type name, rendered in signature font |
| **Upload** | Upload an image of their signature |
### Signature Properties
| Property | Description | Default |
|----------|-------------|---------|
| **Required** | Must be completed | Yes |
| **Assigned To** | Which signer completes this | First signer |
| **Width** | Field width | 200px |
| **Height** | Field height | 60px |
### Signature Best Practices
- **Size appropriately** - Minimum 150px wide for readable signatures
- **Leave space** - Don't crowd with other elements
- **Align with lines** - Place on existing signature lines in the document
- **One per signer** - Usually one signature field per signer
### Signature Data Captured
When a signer signs, WPsigner records:
- Signature image (PNG)
- Timestamp (UTC)
- IP address
- User agent (browser/device)
- Drawing velocity (for drawn signatures)
---
## Initials Field
A smaller version of the signature field for initializing pages or clauses.
### When to Use Initials
- **Multi-page documents** - Initial each page
- **Specific clauses** - Acknowledge individual sections
- **Amendments** - Mark changes as reviewed
- **Witness marks** - Smaller confirmation signatures
### Initials Properties
| Property | Description | Default |
|----------|-------------|---------|
| **Required** | Must be completed | Yes |
| **Assigned To** | Which signer | Current signer |
| **Width** | Field width | 80px |
| **Height** | Field height | 40px |
### Initials vs Signature
| Aspect | Signature | Initials |
|--------|-----------|----------|
| Size | Larger | Smaller |
| Purpose | Main agreement | Page/section acknowledgment |
| Typical count | 1 per signer | Multiple per signer |
---
## Date Field
Captures the date when the signer completes the document.
### Date Behavior
| Option | Description |
|--------|-------------|
| **Auto-fill** | Automatically uses signing date (default) |
| **Manual entry** | Signer selects the date |
### Date Format
The date format is configured globally in **WPsigner → Settings → General**:
| Format | Example |
|--------|---------|
| MM/DD/YYYY | 01/15/2026 |
| DD/MM/YYYY | 15/01/2026 |
| YYYY-MM-DD | 2026-01-15 |
| Month DD, YYYY | January 15, 2026 |
### Date Properties
| Property | Description | Default |
|----------|-------------|---------|
| **Required** | Must be completed | Yes |
| **Auto-fill** | Use current date automatically | Yes |
| **Format** | Date display format | Site default |
### Date Placement Tips
- Place next to signature fields
- Use for agreement dates, not backdating
- Consider timezone differences for international signers
---
## Text Field
Single-line text input for short responses.
### Common Uses
- **Name** - Full legal name
- **Title** - Job title or position
- **Company** - Organization name
- **Address** - Single-line address
- **Phone** - Contact number
- **Email** - Email address
- **ID Number** - License, SSN (partial), passport
### Text Field Properties
| Property | Description | Default |
|----------|-------------|---------|
| **Required** | Must be completed | No |
| **Placeholder** | Helper text shown before input | Empty |
| **Default Value** | Pre-filled value | Empty |
| **Max Length** | Character limit | 256 |
| **Validation** | Input format (email, phone, etc.) | None |
### Text Validation Options
| Validation | Accepts |
|------------|---------|
| **None** | Any text |
| **Email** | Valid email format |
| **Phone** | Numeric with formatting |
| **Number** | Digits only |
| **Letters** | Alphabetic only |
---
## Text Area Field
Multi-line text input for longer responses.
### Common Uses
- **Comments** - Additional notes or observations
- **Explanation** - Detailed responses
- **Address** - Full multi-line address
- **Special instructions** - Custom requirements
- **Decline reason** - Why signer is declining
### Text Area Properties
| Property | Description | Default |
|----------|-------------|---------|
| **Required** | Must be completed | No |
| **Placeholder** | Helper text | Empty |
| **Rows** | Visible text lines | 3 |
| **Max Length** | Character limit | 1000 |
### Text Area vs Text Field
| Text Field | Text Area |
|------------|-----------|
| Single line | Multiple lines |
| Short input | Long input |
| Names, emails | Comments, addresses |
---
## Checkbox Field
Boolean yes/no selection for options and acknowledgments.
### Common Uses
- **Terms acceptance** - "I agree to the terms and conditions"
- **Confirmation** - "I confirm this information is accurate"
- **Options** - "Include extended warranty"
- **Acknowledgment** - "I have read and understood"
- **Consent** - "I consent to email communication"
### Checkbox Properties
| Property | Description | Default |
|----------|-------------|---------|
| **Required** | Must be checked | No |
| **Checked by default** | Pre-checked state | No |
| **Label** | Text next to checkbox | Empty |
### Checkbox Groups
Create related checkboxes for multiple options:
Example: Service Add-ons
- ☐ Priority support (+$99/year)
- ☐ Extended warranty (+$49/year)
- ☐ Training session (+$199 one-time)
### Required Checkboxes
When marked as required:
- Signer must check the box to proceed
- Used for mandatory acknowledgments
- Document cannot be completed without checking
---
## Dropdown Field
Selection from a predefined list of options.
### Common Uses
- **State/Province** - Select from list
- **Country** - Select country
- **Department** - Choose department
- **Plan tier** - Select service level
- **Relationship** - Spouse, child, parent, etc.
- **Yes/No** - Simple binary choice
### Dropdown Properties
| Property | Description | Default |
|----------|-------------|---------|
| **Required** | Must select an option | No |
| **Options** | List of choices | Empty |
| **Default** | Pre-selected option | None |
| **Placeholder** | Text before selection | "Select..." |
### Adding Options
1. Click the dropdown field in the editor
2. Open the Properties panel
3. In "Options," add each choice on a new line:
```
Option 1
Option 2
Option 3
```
### Dropdown vs Checkbox
| Use Dropdown | Use Checkbox |
|--------------|--------------|
| Many options (3+) | Yes/No only |
| Mutually exclusive | Multiple selections possible |
| Saves space | Self-explanatory |
---
## Choice, identity, attachment, and payment fields
- **Checkbox Group** allows multiple selections; **Radio** allows exactly one selection.
- **Name, Email, Phone, Company, VAT, and Title** are purpose-specific text fields. Use them instead of a generic Text field when validation or integration mapping benefits from a stable type.
- **Attachment** lets the assigned signer upload supporting evidence. Avoid requesting sensitive files unless they are required, and define an appropriate retention policy.
- **Label** adds non-editable instructions to the signing layer.
- **Payment** is available when the payment integration is configured and must be completed according to that integration's signing flow.
For choice fields, define clear option labels and test the final PDF output before sending.
---
## Field Placement
### Accessing the Field Editor
1. Go to **WPsigner → New Document** (or edit a **Campaign**) and open the **Fields** step
2. Field types appear in the left sidebar
3. The PDF preview is in the center — place fields directly on the page
The same field editor is used when you build a template and later save it from **Review → Save as Template**.
### Placing Fields
**Click Method**
1. Click a field type in the toolbar
2. Click on the document where you want it
3. Field appears at cursor position
**Drag Method**
1. Click and hold a field type
2. Drag to the document
3. Release to place
### Moving Fields
- Click and drag any placed field
- Fields snap to alignment guides
### Resizing Fields
- Hover a field and drag the resize handle (bottom-right corner)
- Make signature fields large enough for finger or stylus input
### Deleting Fields
- Hover the field and click the red **X** outside the top-right corner
- Or right-click the field → **Delete**
---
## Field name, mapping name, and placeholder
Every placed field (except types that open their own options modal, such as dropdown / radio / checkbox group) can be renamed with a **double-click**.
### Open Field Properties
1. **Double-click** the field on the PDF
2. A floating **Field Properties** popup appears (not inside the field box)
3. Edit the values, then click **Save** (or press Enter). **Cancel** or Escape closes without saving
| Setting | What it is | Who sees it |
|---------|------------|-------------|
| **Field name** | Friendly label shown on the field in the editor (e.g. `Client full name`) | You, in New Document / Campaign / Templates |
| **Mapping name** | Technical key for Zapier, form feeds, and the API (e.g. `client_name`) | Automations and integrations |
| **Placeholder** | Hint text the signer may see before typing | Signer on the signing page (text-like fields) |
### Mapping name rules (important)
- If you leave **Mapping name** empty, WPsigner uses the **Field name** (converted to a safe key, e.g. `Client full name` → `client_full_name`)
- Use short, stable keys for integrations: lowercase letters, numbers, and underscores (`client_name`, `property_address`)
- Keep the same mapping name if Zapier or a form feed already depends on it — changing the key breaks existing mappings
> **Two ways to set mapping keys**
1. **While placing fields** — double-click → **Mapping name** (fastest while building the PDF)
2. **After saving a template** — **WPsigner → Templates → ⋮ → Map Variables** (edit keys on an existing template)
Both point to the same variable keys used by [Zapier](/integrations/zapier/), [Uncanny Automator](/addons/uncanny-automator-actions/#prefill), and the [Templates API](/api/templates/).
### Examples
| Field name (display) | Mapping name | Used for |
|----------------------|--------------|----------|
| Client full name | `client_name` | Prefill from Zapier / Calendly |
| Property address | `property_address` | Prefill from a form or CRM |
| Appointment date | `appointment_date` | Prefill booking date |
| Company | *(leave empty)* | Key becomes `company` automatically |
---
## Field Assignment
### Assigning to Signers
Signer **#1** is the first person on the Add Signers list. Signature fields you place while that slot is active belong to them. Add more people in order for Signer #2, #3, and so on. See [Signer order](/core-features/signer-workflows/#signer-order).
When multiple signers exist:
1. Select a field
2. In Properties, find "Assigned To"
3. Select the signer from the dropdown
4. Field changes to signer's color
### Color Coding
Each signer has a unique color:
| Signer | Color | Meaning |
|--------|-------|---------|
| Signer 1 | Blue | Signer 1's fields |
| Signer 2 | Green | Signer 2's fields |
| Signer 3 | Orange | Signer 3's fields |
This helps visualize which signer completes which fields.
### Field Visibility
- Each signer only sees their assigned fields as editable
- Other signers' fields appear as read-only
- Completed fields show the entered values
---
## Field Properties Reference
### Common Properties (All Fields)
| Property | Type | Description |
|----------|------|-------------|
| `field_name` | String | Display label in the editor (Field Properties) |
| `variable_mapping` | String | Integration key; empty falls back to field name |
| `placeholder` | String | Signer hint text (text-like fields) |
| `assignedTo` | Signer | Which signer completes this |
| `required` | Boolean | Must be completed |
| `x` | Number | X position (% from left) |
| `y` | Number | Y position (% from top) |
| `width` | Number | Width (% of page) |
| `height` | Number | Height (% of page) |
| `page` | Number | Page number (1-indexed) |
### Field-Specific Properties
**Signature/Initials**
| Property | Type | Description |
|----------|------|-------------|
| `drawEnabled` | Boolean | Allow drawing |
| `typeEnabled` | Boolean | Allow typing |
| `uploadEnabled` | Boolean | Allow upload |
**Text/Text Area**
| Property | Type | Description |
|----------|------|-------------|
| `placeholder` | String | Helper text |
| `defaultValue` | String | Pre-filled value |
| `maxLength` | Number | Character limit |
**Checkbox**
| Property | Type | Description |
|----------|------|-------------|
| `checked` | Boolean | Default state |
| `label` | String | Display label |
**Dropdown**
| Property | Type | Description |
|----------|------|-------------|
| `options` | Array | List of choices |
| `defaultOption` | String | Pre-selected value |
---
## Best Practices
### Field Sizing Guide
| Field Type | Recommended Width | Recommended Height |
|------------|-------------------|-------------------|
| Signature | 200-300px | 60-80px |
| Initials | 60-100px | 40-60px |
| Date | 100-150px | 30px |
| Text | 150-300px | 30px |
| Text Area | 200-400px | 60-120px |
| Checkbox | 20px | 20px |
| Dropdown | 150-250px | 30px |
### Mobile Considerations
60%+ of documents are signed on mobile devices:
- Make signature fields larger (minimum 200px wide)
- Space fields apart (avoid overlapping)
- Use clear labels
- Test on phone before sending
### Accessibility
- Add placeholder text to explain expected input
- Use clear, descriptive labels
- Don't rely only on color to convey meaning
- Ensure sufficient field sizes for touch input
---
## Next Steps
- [Creating Documents](/core-features/creating-documents/) - Full wizard guide
- [Signer Workflows](/core-features/signer-workflows/) - Signing order options
- [Campaigns](/core-features/campaigns/) - Public signing links
---
# Security & Compliance
> Configure signer verification gates, evidence capture, certificates, and timestamping policies in WPsigner.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/core-features/security-compliance/
Markdown: https://docs.wpsigner.com/md/core-features/security-compliance.md
The **Security & Compliance** screen centralizes WPsigner's signing gates and evidence settings. Use it to decide when signers must verify an email, complete KYC, enter an access code, and which cryptographic evidence is added to completed documents. A separate per-signer option can also require a matching WordPress login before the signing page opens.
> **Lite limits**
**Lite** includes email OTP, access codes, audit trail, and local timestamps. KYC integrations, extra OTP channels, and external TSA are **Pro**. [Lite vs Pro](/getting-started/lite-vs-pro/)
Open **WPsigner → More → Security & Compliance**.
> **caution**
These controls strengthen authentication and evidence. They do not by themselves certify a signature as qualified, guarantee compliance, or replace legal advice for your jurisdiction and use case.
## Signing gate policies
OTP, KYC, and access codes each support three policies:
| Policy | Behavior |
|--------|----------|
| **Always** | Require the gate for every applicable signing request |
| **Per document** | Require it only when enabled in that document's Review step |
| **Off** | Do not apply the gate |
With **Per document**, review each document before sending and enable only the controls required for that transaction.
## Email verification (OTP)
OTP verifies that the signer can receive a one-time code through a configured channel.
| Method | Requirement |
|--------|-------------|
| **Email** | Working WordPress email delivery |
| **SMS** | Configured Twilio integration |
| **Both** | Email delivery and Twilio |
Test email and SMS delivery before requiring OTP in production. A failed delivery can prevent the signer from continuing.
WPsigner rate-limits OTP requests and verifies them through protected AJAX actions. If a firewall plugin blocks OTP, check [System Status](/getting-started/system-status-and-storage/) and allowlist the WPsigner actions it reports.
## Identity verification (KYC)
KYC uses the [Didit.me integration](/integrations/didit/) to verify a government-issued ID, selfie match, and liveness result before signing.
1. Configure and test Didit under **WPsigner → More → Integrations → Didit**.
2. Return to **Security & Compliance**.
3. Choose **Always**, **Per document**, or **Off**.
The KYC policy is unavailable or ineffective until Didit credentials are configured. WPsigner stores verification status and decision metadata; identity images remain with Didit.
## Access codes
An access code is a six-digit secret associated with the signing request. The stored code is hashed rather than saved in readable form.
When access codes are required:
1. WPsigner generates or accepts the document's code.
2. Choose whether WPsigner should email the code to signers.
3. The signer must enter the code before continuing.
For stronger separation, deliver the signing link and access code through different channels.
## WordPress login (per signer)
This gate is **opt-in per signer** and **off by default**. It is not a global Security & Compliance policy and it does not replace OTP, KYC, or access codes.
When **Require WordPress login with this email** is checked on a signer:
1. The visitor must be logged in to WordPress.
2. The logged-in account email must match that signer's email (case-insensitive).
3. The unique signing link is not enough on its own.
If nobody is logged in, the signing page asks them to log in and then returns to the same link. If they are logged in with a different account, they see that mismatch and can log out, then log in as the matching user.
Use this when the signer already has a WordPress account on your site (members, staff, LMS users). The checkbox is refused if that email is not a WordPress user — create the account first, or leave the option off. Leave it off for guests and external counterparties. Public campaign links and Bulk Send CSV rows do not use this gate — those flows have no preassigned WordPress user.
You cannot activate a public campaign on a document that already has a gated signer, and you cannot turn the checkbox on while that document has an active campaign. If someone still reaches a public link and types a gated signer's email, WPsigner re-checks the login requirement and refuses the signature until the matching WordPress account is signed in. Individual signing links for a gated signer are never redirected to the campaign URL.
The invitation email adds a short note when the flag is on. Customized email templates need the `require_wp_login` variable if you want that sentence in your own copy.
## Evidence capture
| Control | Evidence added |
|---------|----------------|
| **Capture geolocation** | Approximate signer location when permission and browser support allow |
| **Capture device information** | Browser/device metadata in the audit record |
| **Digital ID (PKI)** | Cryptographic PDF certificate signature |
| **Timestamp provider (TSA)** | Trusted time evidence for the document hash |
| **Immutable timestamping** | Additional configured timestamp evidence |
Geolocation may be unavailable when the signer denies permission, the browser blocks it, or the network obscures the location.
## Compliance score
The screen displays an orientation score based on selected controls:
| Factor | Maximum contribution |
|--------|----------------------|
| OTP policy | 25 |
| Geolocation | 10 |
| Device information | 5 |
| Custom Digital ID certificate | 10 |
| Timestamp provider | Up to 50 |
KYC and access codes are important gates but do not currently add points to this score.
| Displayed level | Score / conditions |
|-----------------|--------------------|
| **SES** | 0–39 |
| **SES+** | 40–64 |
| **AdES** | 65–79 |
| **HA (QES-oriented)** | 80+ plus an active PKI certificate and qualified/custom TSA |
> **important**
The score is configuration guidance, not a legal classification or QES certification. A true Qualified Electronic Signature depends on regulated identity, certificate, provider, and jurisdictional requirements outside a score.
## Recommended profiles
### Routine internal acknowledgement
- OTP: **Per document**
- KYC: **Off**
- Access code: **Off** or **Per document**
- Device information: On
- Geolocation: Based on privacy policy
- Audit trail and secure backups: On
### Higher-risk external agreement
- OTP: **Always**
- KYC: **Per document** or **Always**
- Access code: **Per document**
- Device and geolocation evidence: On where lawful
- Commercial certificate and reliable TSA
Document the reason for each control and avoid collecting more personal data than necessary.
## Before enabling a gate globally
1. Send a test document to accounts you control.
2. Test on desktop and mobile.
3. Confirm SMTP, Twilio, Didit, and TSA connectivity as applicable.
4. Verify the final PDF and audit trail.
5. Publish signer-facing privacy and support instructions.
6. Define retention and deletion policies for collected data.
## Troubleshooting
### KYC cannot be enabled
Configure and test Didit first. The KYC gate only operates when the integration is available.
### SMS is unavailable
Install and configure the WPsigner Twilio integration, then reload the Security & Compliance screen.
### OTP requests fail
Check SMTP, spam filtering, caching, and security-plugin logs. Use **WPsigner → More → System Status** to test email and identify blocked AJAX actions.
### Signers are unexpectedly asked for a gate
Check both the global policy and the document's Review settings. **Always** overrides per-document choice; **Per document** follows the document's saved security settings.
### The score is lower than expected
Confirm the Digital ID is active and the selected TSA provider is recognized. KYC and access codes do not increase the current score.
### Require WordPress login cannot stay checked
The signer email must already belong to a WordPress user. Create that account first, or leave the option off. WPsigner does not create users.
You also cannot turn the checkbox on while the document has an **active public campaign**, and you cannot activate a campaign if any named signer already has the gate on.
### Signer sees a WordPress login page instead of the PDF
That row has **Require WordPress login with this email** on. They must sign in with the WordPress account that uses the same email, then they return to the signing link. A different logged-in account is rejected.
## Related guides
- [Creating Documents](/core-features/creating-documents/#wordpress-users) — user picker, Add me as signer #1, and the checkbox
- [Didit.me KYC](/integrations/didit/)
- [Digital ID](/digital-identity/digital-id/)
- [Timestamping](/digital-identity/timestamping/)
- [Audit Trails](/digital-identity/audit-trails/)
- [System Status, Storage & Retention](/getting-started/system-status-and-storage/)
---
# Signer Workflows
> Complete guide to sequential and parallel signing workflows in WPsigner.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/core-features/signer-workflows/
Markdown: https://docs.wpsigner.com/md/core-features/signer-workflows.md
WPsigner supports two signing workflows: **Parallel** (everyone signs at once) and **Sequential** (one after another). Choose the right workflow based on your document requirements.
## Workflow Comparison
| Feature | Parallel | Sequential |
|---------|----------|------------|
| **Email delivery** | All at once | One at a time |
| **Signing order** | Any order | Enforced order |
| **Completion time** | Fastest | Depends on each signer |
| **Use case** | Co-signers, witnesses | Approval chains, contracts |
---
## Signer order
Signer **#1, #2, #3** is the order of the rows on **Add Signers** — the first person you add is Signer #1.
- Signature and initials fields follow that slot (Signer #1’s color, then Signer #2)
- **Add me as signer #1** only fills the first row with the current WordPress account
- Drag rows to change the order before you send
- On **Use Template**, row 1 is the template’s Signer #1 fields, row 2 is Signer #2
**Sequential** emails follow this list. **Parallel** emails go out together; the slots still decide who owns which fields.
How to add people from WordPress, require a login, or fill yourself as #1: [Creating Documents](/core-features/creating-documents/#wordpress-users).
---
## Parallel Signing
### How It Works
When you send a document with parallel signing:
1. **All signers receive the email simultaneously**
2. Each signer gets their own unique signing link
3. Signers can complete their fields in any order
4. Document completes when ALL signers finish
### Visual Flow
```
Document Sent
↓
├→ Signer A receives email → Signs → Done ✓
├→ Signer B receives email → Signs → Done ✓
└→ Signer C receives email → Signs → Done ✓
↓
All signed = Complete!
```
### When to Use Parallel
- **Co-signers**: Both parties sign the same contract
- **Witnesses**: Multiple witnesses sign independently
- **Team acknowledgments**: Everyone confirms at once
- **Speed is priority**: Need signatures ASAP
### Example: Partnership Agreement
Two business partners need to sign an agreement:
1. Add Partner A (alice@company.com)
2. Add Partner B (bob@company.com)
3. Keep workflow as "Parallel"
4. Both receive email immediately
5. Either can sign first
6. Done when both complete
---
## Sequential Signing
### How It Works
When you send a document with sequential signing:
1. **Only the first signer receives an email**
2. After Signer 1 completes, Signer 2 gets their email
3. This continues in order until all signers finish
4. Document completes when the LAST signer finishes
### Visual Flow
```
Document Sent
↓
Signer A receives email
↓
Signer A signs → Done ✓
↓
Signer B receives email (triggered)
↓
Signer B signs → Done ✓
↓
Signer C receives email (triggered)
↓
Signer C signs → Done ✓
↓
All signed = Complete!
```
### When to Use Sequential
- **Approval chains**: Manager must approve before director
- **Contracts**: Vendor signs, then client countersigns
- **Dependent signatures**: One signature validates another
- **Review processes**: Each step requires previous completion
### Configuring Signing Order
**Step 1: Enable Sequential Signing**
1. In the Signers step, select "Sequential Signing"
2. The order indicator appears next to each signer
**Step 2: Arrange Order**
1. Drag signers using the handle (≡ icon)
2. Drop in desired position
3. Numbers update automatically (1, 2, 3...)
**Step 3: Verify Order**
- Signer #1 receives email first
- Signer #2 receives email after #1 signs
- Continue in order...
### Example: Employee Contract
An employment contract needs:
1. Employee signature first
2. Manager approval second
3. HR final sign-off
Configuration:
| Order | Name | Role |
|-------|------|------|
| 1 | John Smith | Employee |
| 2 | Jane Manager | Department Manager |
| 3 | HR Team | Human Resources |
Result:
- John receives email → signs employment terms
- Jane receives email → approves hire
- HR receives email → finalizes employment
---
## Advanced Signer Options
### Signer Roles
Assign descriptive roles to each signer:
| Role | Purpose |
|------|---------|
| **Buyer** | Purchasing party |
| **Seller** | Selling party |
| **Witness** | Third-party observer |
| **Guarantor** | Financial guarantor |
| **Notary** | Official notary |
| **Agent** | Authorized representative |
Roles appear in:
- The signing interface
- Emails sent to signers
- Audit trail
- Certificate of Completion
### Access Codes (PIN)
Add extra security with a PIN:
1. Click the lock icon next to a signer
2. Enter a 4-6 digit PIN
3. Or click "Generate" for a random PIN
4. Share the PIN with the signer via separate channel
The signer must enter the PIN before viewing the document.
> **tip**
For stronger separation, send the access code by SMS or phone rather than including it with the signing link.
### Expiration Settings
Set a deadline for signing:
**Per-Document Expiration**
1. In Review step, enable "Set Expiration"
2. Choose date and time
3. Links become invalid after this date
**Signer-Specific Deadlines** (Sequential)
- Each signer can have their own deadline
- Useful for multi-stage approval processes
### Authentication Options
| Method | Security | User Experience |
|--------|----------|-----------------|
| **Email only** | Basic | Easiest |
| **Email + PIN** | Medium | Requires PIN entry |
| **Email + SMS OTP** | High | Receives code via SMS |
---
## Signer Experience
### What Signers See
**Email Notification**
- Professional signing request email
- Document title and sender info
- Prominent "Sign Now" button
- Expiration date (if set)
**Signing Page**
- Full document preview
- Required fields highlighted
- Clear instructions
- Mobile-friendly interface
**Completion**
- Success confirmation
- Download option (optional)
- Email with signed copy
### Signer Actions
From the signing interface, signers can:
| Action | Description |
|--------|-------------|
| **Sign** | Complete their assigned fields |
| **Decline** | Refuse to sign with reason |
| **Delegate** | Forward to another person (if enabled) |
| **Download** | Get a copy after signing |
### Decline Handling
If a signer declines:
1. They're asked for a reason (optional)
2. Document status changes to "Declined"
3. Document owner is notified immediately
4. Other signers are informed
5. Workflow stops
Reasons for declining might include:
- Incorrect information
- Need to review with legal
- Contract terms unacceptable
- Wrong person assigned
---
## Managing In-Progress Documents
### Tracking Status
From **WPsigner → Documents**, view real-time status:
| Status | Icon | Meaning |
|--------|------|---------|
| Sent | 📤 | Awaiting signatures |
| Viewed | 👁️ | Signer opened the link |
| Signed | ✍️ | Signer completed their fields |
| Complete | ✅ | All signers finished |
| Declined | ❌ | Signer refused |
### Sending Reminders
For signers who haven't completed:
**Manual Reminder**
1. Open the document
2. Click **Send Reminder**
3. Reminder email sent immediately
**Auto-Reminders**
Configure automatic reminders in Settings:
- After 24 hours
- After 3 days
- After 7 days
- Custom schedule
### Resending Invitation
If a signer didn't receive the email:
1. Open the document
2. Find the signer in the list
3. Click **Resend**
4. New email sent with same link
### Voiding a Document
To cancel a document before completion:
1. Open the document
2. Click **Actions → Void**
3. Enter reason (optional)
4. Confirm void action
Result:
- All signing links become invalid
- Signers are notified by email
- Document marked as "Voided"
- Audit trail records the void
---
## Workflow Best Practices
### Choosing the Right Workflow
| Scenario | Recommended |
|----------|-------------|
| Two equal parties | Parallel |
| Approval needed first | Sequential |
| Group acknowledgment | Parallel |
| Chain of command | Sequential |
| Independent witnesses | Parallel |
| Dependent signatures | Sequential |
### Reducing Signing Time
- **Use parallel when possible** - Faster completion
- **Send reminders** - Keep documents moving
- **Set reasonable deadlines** - Creates urgency
- **Pre-fill known fields** - Less work for signers
- **Mobile-friendly** - 60%+ sign on phones
### Handling Delays
If a signer isn't responding:
1. Send a manual reminder
2. Call them directly
3. Check spam folder
4. Resend the invitation
5. Consider voiding and recreating with different signer
---
## WordPress login per signer
Sequential and parallel order still come from the signer list. **Require WordPress login with this email** is a separate identity check on that row only (**Pro 3.2.0+**).
Example: signer #1 (an employee) must log in with their WordPress account; signer #2 (an external client) can open the link without logging in. Turn the checkbox on only for the employee.
The email on that row must already belong to a WordPress user. If it does not, WPsigner turns the checkbox off and shows an alert. It does not create the account.
This is not mixed with OTP, PIN, or KYC. It does not apply to public campaign links or Bulk Send CSV rows. Details: [Security & Compliance](/core-features/security-compliance/#wordpress-login-per-signer).
## Common Questions
### Can I change the order after sending?
No. Once sent, the signing order is locked. Void the document and create a new one if needed.
### What if a sequential signer is unavailable?
The workflow is blocked. Options:
- Wait for them to return
- Void and assign to someone else
- Use delegation (if enabled)
### Can signers see other signers' info?
Signers only see fields assigned to them. They can see other signers' names in the Certificate of Completion after all signatures.
### How long are signing links valid?
By default, links don't expire. Set an expiration date if you need time limits.
---
## Next Steps
- [Form Fields](/core-features/form-fields/) - All field types explained
- [Campaigns (Public Links)](/core-features/campaigns/) - Mass signing
- [Email Templates](/customization/email-templates/) - Customize notifications
---
# Customization
> Brand WPsigner with Appearance (logo, signing buttons, portal), white-label, email templates, languages, and Signed PDF fonts.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/customization/
Markdown: https://docs.wpsigner.com/md/customization.md
WPsigner is designed to disappear behind your brand. From the signing page your clients see to the emails they receive, every touchpoint can be customized to match your company's identity.
---
## Guides
| Guide | Description |
|-------|-------------|
| [Appearance](/customization/appearance/) | Brand, Signing Page buttons, and Client Portal on one admin page (Pro) |
| [Whitelabeling](/customization/whitelabeling/) | Replace WPsigner branding with your own logo, colors, and company name across the signing experience |
| [Email Templates](/customization/email-templates/) | Customize the content, layout, and design of every email WPsigner sends to signers |
| [Languages & Translations](/customization/languages/) | Language packs for the admin UI, plus Signed PDF fonts (Vietnamese and other scripts) |
---
## What You Can Customize
### Signing Experience
| Element | Customizable | Where |
|---------|-------------|-------|
| **Company logo** | Logo displayed on the signing page | Appearance → Brand |
| **Brand colors** | Primary color for buttons, links, and accents | Appearance → Brand |
| **Signing buttons** | Color, size, corners, style, light/dark theme | Appearance → Signing Page |
| **Company name** | Shown in headers and email "From" name | Appearance → Brand |
| **Client portal look** | Portal logo, colors, welcome text | Appearance → Client Portal |
### Emails
| Element | Customizable | Where |
|---------|-------------|-------|
| **From name** | Sender name shown in inbox | Email Templates |
| **From address** | Reply-to email address | Email Templates |
| **Subject line** | Per-event subject with dynamic variables | Email Templates |
| **Body content** | Full HTML email body with placeholders | Email Templates |
| **Logo in emails** | Header image in email template | Email Templates |
---
## Quick Start
1. **[Open Appearance](/customization/appearance/)** first — upload your logo, set your brand color, and style signing buttons. This is **WPsigner → Appearance**.
2. **[Whitelabeling](/customization/whitelabeling/)** if you need to rename the product or hide WPsigner branding.
3. **[Customize email templates](/customization/email-templates/)** — subject lines, body text, and design for signing requests, reminders, and completion notifications.
4. **[Choose a language](/customization/languages/)** — install a language pack from **WPsigner → Languages**, or add a custom locale with Loco Translate / Poedit. For Vietnamese or other non-Latin-1 text on the **signed PDF**, open **Signed PDF fonts** on that same page and install **Accented Latin**.
> **tip**
If you're an agency managing multiple clients, whitelabeling is especially useful. Your clients see your brand throughout the entire signing process — they never know WPsigner is running behind the scenes.
---
# Email Templates
> Complete guide to customizing all email notifications sent by WPsigner for signing requests, reminders, and more.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/customization/email-templates/
Markdown: https://docs.wpsigner.com/md/customization/email-templates.md
WPsigner sends automated emails throughout the document signing workflow. This page covers how to customize these emails to match your brand voice and provide a professional experience.
## Email Types
WPsigner sends five types of automated emails:
| Email | Purpose | When Sent |
|-------|---------|-----------|
| **Signing Request** | Invite signer to sign | When document is sent |
| **Reminder** | Follow-up for pending signatures | Automatically or manually |
| **Completed** | Notify all parties of completion | When all signers finish |
| **Declined** | Alert when signer refuses | When signer declines |
| **OTP Verification** | Identity verification code | When OTP is enabled |
---
## Why Customize Emails?
### Brand Consistency
| Default Emails | Customized Emails |
|----------------|------------------|
| Generic messaging | Your brand voice |
| Standard templates | On-brand design |
| WPsigner branding | Your company branding |
| Basic information | Tailored messaging |
### Better Results
Custom emails improve:
- **Open rates** - Familiar sender name and branding
- **Completion rates** - Clear, personalized instructions
- **Trust** - Professional, consistent experience
- **Engagement** - Brand-appropriate tone and messaging
---
## Accessing Email Templates
Navigate to:
1. **WPsigner** in the admin sidebar
2. Click **More** dropdown in the top navigation
3. Select **Email Templates**
Or go directly to: `WPsigner → More → Email Templates`
---
## Template Editor Interface
### Template Tabs
At the top, you'll see tabs for each email type:
- 📧 **Signing Request** - Invitation to sign
- 🔔 **Reminder** - Follow-up reminder
- ✅ **Completed** - Completion notification
- ❌ **Declined** - Decline notification
- 🔐 **OTP Verification** - Verification code
Click any tab to edit that template.
### Visual Editor
The editor provides:
- **Rich text editing** - Format text, add links, images
- **HTML mode** - Direct HTML editing for advanced users
- **Media library** - Insert images and files
- **Full toolbar** - All formatting options
### Variables Sidebar
On the right, you'll see available variables:
- Click any variable to insert it at cursor
- Variables are replaced with real data when sent
- Hover for descriptions
### Action Buttons
| Button | Function |
|--------|----------|
| **Preview** | See how email will look |
| **Send Test** | Send test email to yourself |
| **Save Template** | Save your changes |
| **Reset to Default** | Restore original template |
---
## Available Variables
Variables are placeholders that get replaced with real data. Use the `{{variable_name}}` syntax.
### Common Variables (All Templates)
| Variable | Description | Example Output |
|----------|-------------|----------------|
| `{{company_name}}` | Your company name | "Acme Corporation" |
| `{{company_logo}}` | Company logo URL | https://... |
| `{{signer_name}}` | Recipient's name | "John Smith" |
| `{{signer_email}}` | Recipient's email | "john@example.com" |
| `{{document_title}}` | Document name | "Service Agreement" |
| `{{sender_name}}` | Who sent the document | "Jane Doe" |
### Signing Request Variables
| Variable | Description |
|----------|-------------|
| `{{signing_url}}` | Unique signing link |
| `{{document_filename}}` | Original file name |
| `{{expires_at}}` | Expiration date |
| `{{custom_message}}` | Optional sender message |
| `{{require_wp_login}}` | Set when that signer must log in with a matching WordPress account. Use `{{#if require_wp_login}}` to show the extra sentence |
### Reminder Variables
| Variable | Description |
|----------|-------------|
| `{{signing_url}}` | Signing link |
| `{{days_pending}}` | Days since sent |
| `{{expires_at}}` | Expiration date |
| `{{require_wp_login}}` | Same flag as the signing-request template — use `{{#if require_wp_login}}` |
### Completed Variables
| Variable | Description |
|----------|-------------|
| `{{completed_at}}` | Completion timestamp |
| `{{download_url}}` | Link to download signed PDF |
| `{{total_signers}}` | Number of signers |
### Declined Variables
| Variable | Description |
|----------|-------------|
| `{{declined_by}}` | Who declined |
| `{{declined_at}}` | When they declined |
| `{{decline_reason}}` | Reason provided |
### OTP Variables
| Variable | Description |
|----------|-------------|
| `{{otp_code}}` | Verification code |
| `{{otp_expires}}` | Code expiration time |
---
## Customizing Each Template
### Signing Request Email
This is the most important email—it initiates the signing process.
**Best Practices:**
- Clear subject line: "Document awaiting your signature"
- Personalize with signer name
- Explain what the document is
- Prominent call-to-action button
- Include expiration if applicable
- Offer alternative link for button issues
**Example Structure:**
```html
Hello {{signer_name}},
{{sender_name}} has sent you a document that requires your signature:
{{document_title}}
{{#if custom_message}}
{{custom_message}}
{{/if}}
Review & Sign Document
{{#if expires_at}}
This document expires on {{expires_at}}
{{/if}}
```
### Reminder Email
Remind signers who haven't completed signing.
**Best Practices:**
- Friendly, non-aggressive tone
- Explain why it's important
- Include urgency if deadline approaching
- Re-state what the document is
- Easy access to signing link
**Example:**
```html
Hi {{signer_name}},
Just a friendly reminder that you have a document waiting for your signature.
{{document_title}}
Sign Now
This only takes a few minutes. If you have questions, contact {{sender_name}}.
```
### Completed Email
Notify all parties that the document is finished.
**Best Practices:**
- Confirmation subject: "Document Completed"
- Celebrate the completion
- Provide download link
- Include completion timestamp
- Summarize who signed
**Example:**
```html
Great news!
The document {{document_title}} has been signed by all parties.
Completed on: {{completed_at}}
Download Signed Document
A copy has been sent to all signers for their records.
```
### Declined Email
Alert the document owner when someone declines.
**Best Practices:**
- Clear subject: "Document Declined"
- Identify who declined
- Include their reason
- Suggest next steps
**Example:**
```html
Unfortunately, {{declined_by}} has declined to sign the document:
{{document_title}}
{{#if decline_reason}}
Reason: "{{decline_reason}}"
{{/if}}
You may want to contact them to discuss their concerns or create a new document with modifications.
```
### OTP Verification Email
Send verification codes for identity confirmation.
**Best Practices:**
- Clear subject: "Your verification code"
- Large, readable code
- State expiration time
- Security reminder not to share
**Example:**
```html
Hello {{signer_name}},
Your verification code is:
{{otp_code}}
This code expires in {{otp_expires}}.
If you didn't request this code, please ignore this email.
```
---
## Preview and Testing
### Preview Feature
1. Click the **Preview** button
2. View how the email will appear
3. Switch between Desktop, Tablet, and Mobile views
4. Verify formatting and layout
### Send Test Email
1. Click **Send Test**
2. Enter your email address
3. Click **Send Test Email**
4. Check your inbox for the sample
The test email uses sample data so you can see real output.
---
## Design Best Practices
### Email Design Principles
| Principle | Implementation |
|-----------|---------------|
| **Mobile-first** | Most emails read on mobile |
| **Clear CTA** | Large, prominent button |
| **Minimal text** | Concise, scannable content |
| **Brand colors** | Match your brand |
| **White space** | Easy to read |
### Technical Considerations
| Consideration | Recommendation |
|---------------|----------------|
| **Image hosting** | Use absolute URLs |
| **CSS** | Inline styles only |
| **Width** | Max 600px for mobile |
| **Fonts** | System fonts for compatibility |
| **Alt text** | Always include for images |
### Accessibility
- Use sufficient color contrast
- Include alt text for images
- Don't rely on color alone for meaning
- Keep font sizes readable (14px+)
---
## Template HTML Structure
WPsigner emails use a responsive HTML structure:
```html
Email Title
{{#if company_logo}}
{{/if}}
{{company_name}}
|
|
|
|
This email was sent by {{company_name}}.
|
|
```
---
## Conditional Content
Use Handlebars-style conditionals for dynamic content:
### If/Then Blocks
```handlebars
{{#if custom_message}}
Message from {{sender_name}}:
{{custom_message}}
{{/if}}
{{#if require_wp_login}}
You must sign in with the WordPress account that uses this email. The signing link alone is not enough.
{{/if}}
```
### With Else
```handlebars
{{#if company_logo}}
{{else}}
{{company_name}}
{{/if}}
```
---
## Resetting Templates
To restore a template to its default:
1. Open the template you want to reset
2. Click **Reset to Default**
3. Confirm the reset
4. Template reverts to original
> **caution**
Resetting a template permanently removes your customizations. Save a backup before resetting.
---
## Email Deliverability
### SMTP Configuration
For reliable email delivery, configure SMTP:
1. Install an SMTP plugin (WP Mail SMTP, FluentSMTP)
2. Configure with your email provider
3. Test delivery with WPsigner test email feature
### Best Practices
| Practice | Why |
|----------|-----|
| **Use your domain** | Better deliverability |
| **Configure SPF/DKIM** | Authentication |
| **Monitor bounces** | Maintain sender reputation |
| **Avoid spam triggers** | Stay out of spam folder |
---
## Common Issues
### Emails not sending
1. Verify SMTP is configured
2. Check email address validity
3. Review server error logs
4. Test with WPsigner's Send Test feature
### Variables not replacing
- Check variable spelling exactly
- Ensure double curly braces: `{{variable}}`
- Preview to verify replacements
### HTML not rendering correctly
- Use inline CSS styles
- Avoid complex layouts
- Test in multiple email clients
- Use the Preview feature
---
## Next Steps
- [Whitelabeling](/customization/whitelabeling/) - Full branding options
- [Settings Overview](/getting-started/installation/) - All settings explained
- [Signer Workflows](/core-features/signer-workflows/) - Workflow options
---
# Languages & Translations
> Install WPsigner language packs and Signed PDF fonts so the admin UI and flattened signed PDFs support Vietnamese and other languages.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/customization/languages/
Markdown: https://docs.wpsigner.com/md/customization/languages.md
WPsigner ships in **English** by default. Additional languages are delivered as **language packs** you install from **WPsigner → Languages** (requires an active license). Packs are not bundled inside the public plugin ZIP.
> **note**
WPsigner uses its own language pack system (License Manager catalog). It is **not** translated via translate.wordpress.org.
---
## Available languages
Official packs currently cover these locales (core + matching addon strings when included in the pack):
| Language | Locale codes |
|----------|----------------|
| English (default) | `en` / `en_US` (source strings — no pack required) |
| Español | `es`, `es_ES`, plus regional variants such as `es_MX`, `es_AR`, `es_CL`, `es_CO`, `es_CR`, `es_GT`, `es_HN`, `es_PE`, `es_US`, `es_VE` |
| Français | `fr`, `fr_FR` |
| Deutsch | `de`, `de_DE` |
| Italiano | `it`, `it_IT` |
| Português | `pt`, `pt_BR` (Brasil), `pt_PT` (Portugal) |
The exact list shown on your site comes from the **live catalog** at **WPsigner → Languages**. If a locale is missing from the catalog, it is not published yet — see [Add a missing language](#add-a-missing-language).
### What language packs cover
| Component | Text domain | Included in packs |
|-----------|-------------|-------------------|
| WPsigner core | `insigner` | Required |
| Smart Signing Forms | `insigner-smart-forms` | Optional (when present) |
| Document Builder | `insigner-document-builder` | Optional |
| WPSigner for MainWP | `insigner-mainwp` | Optional |
| ApproveMe Importer | `wpsigner-approveme-importer` | Optional |
> **tip**
Installing a language pack translates the **WordPress admin UI** and plugin strings for that locale. Document PDF content created by users is not auto-translated — only interface strings. Names and typed text in flattened signed PDFs need a **Signed PDF fonts** pack if they use characters beyond basic Latin.
---
## Signed PDF fonts
Language packs do **not** change the font used when WPsigner flattens a signed PDF. Core still uses Helvetica (Latin-1) until you install a PDF font pack (**Pro 3.2.0+**).
This is what you need for **Vietnamese** names and typed text (ă, â, ê, ô, ơ, ư, đ, and tone marks) on the completed PDF. It does **not** translate the WPsigner screens.
1. Go to **WPsigner → Languages**
2. Open the **Signed PDF fonts** section
3. For Vietnamese and other Latin languages with accents, install **Accented Latin**
4. Click **Use for signed PDFs** if it is not already active
5. Send a test document and download the completed PDF
The site needs internet only during install. After that, flattening uses the font stored on your server.
Each pack downloads a [Noto](https://fonts.google.com/noto) font (SIL Open Font License) after install and stores it in `wp-content/uploads/wps-pdf-fonts/{pack}/`. Packs are not bundled in the plugin ZIP.
| Pack | Works for |
|------|-----------|
| Accented Latin | Vietnamese, Turkish, Polish, Czech, Slovak, Romanian, Hungarian, Croatian, Slovenian, Baltic languages, Finnish, Icelandic, Maltese, Welsh, Basque, Catalan, plus French / German / Spanish / Portuguese / Italian / Nordic accents |
| Japanese | Japanese (kanji, hiragana, katakana) |
| Chinese (Simplified) | Simplified Chinese (mainland China, Singapore) |
| Chinese (Traditional) | Traditional Chinese (Taiwan, Hong Kong, Macau) |
| Korean | Korean (Hangul) |
| Arabic | Arabic; Persian and Urdu that use the Arabic script |
| Hebrew | Hebrew |
| Thai | Thai |
Install only the pack you need. You can keep several on disk; **one** pack is used for new signed PDFs at a time.
PDF font packs do **not** translate the WPsigner screens. For a translated UI, install a language pack (or a custom `.mo`) separately.
Arabic and Hebrew embed the characters. Right-to-left line layout in certificates is limited.
---
## Install and activate a language
1. Activate your WPsigner license (**WPsigner → Settings / License**)
2. Go to **WPsigner → Languages**
3. Find the language in the catalog
4. Click **Install** (downloads the pack ZIP)
5. Click **Activate**
WPsigner stores installed `.mo` files under WordPress’s languages directory:
```text
wp-content/languages/plugins/
insigner-{locale}.mo
insigner-smart-forms-{locale}.mo
…
```
You can leave the WordPress site language as-is; WPsigner’s **active pack** controls which translation the plugin loads.
---
## Where translation files live
### On your WordPress site (runtime)
| Location | Purpose |
|----------|---------|
| `wp-content/languages/plugins/` | Installed language packs (`.mo`) used in production |
| Plugin `languages/` folders | Only present in development / source trees — **not** required on customer sites |
### In the product source (developers / translators)
| Path | Contents |
|------|----------|
| `insigner/languages/` | Core template `insigner.pot` + `insigner-{locale}.po` / `.mo` |
| `insigner-smart-forms/languages/` | Addon POT/PO/MO |
| `insigner-document-builder/languages/` | Addon POT/PO/MO |
| `insigner-mainwp/languages/` | Addon POT/MO |
| `wpsigner-approveme-importer/languages/` | Addon POT/PO/MO |
File naming pattern:
```text
{text-domain}-{locale}.po ← editable translation source
{text-domain}-{locale}.mo ← compiled file WordPress loads
{text-domain}.pot ← template of all translatable strings
```
Examples:
```text
insigner-es_ES.po
insigner-es_ES.mo
insigner-fr_FR.mo
insigner-smart-forms-de_DE.mo
```
---
## Add a missing language
Use this when your locale is not in **WPsigner → Languages**, or you need a custom/override translation.
### Option A — Loco Translate (recommended for site admins)
1. Install [Loco Translate](https://wordpress.org/plugins/loco-translate/)
2. Open **Loco Translate → Plugins → WPsigner** (domain `insigner`)
3. Click **New language** → choose your locale (for example `nl_NL`)
4. Translate strings in the editor
5. Save — Loco writes `.po` / `.mo` under `wp-content/languages/plugins/` (or the plugin `languages/` folder, depending on your Loco settings)
6. Repeat for active addons (`insigner-smart-forms`, etc.) if needed
7. In **WPsigner → Languages**, keep English or another pack inactive if it conflicts; prefer loading your custom `.mo` for that locale
Loco is listed as compatible with WPsigner’s standard WordPress i18n APIs.
### Option B — Poedit (recommended for professional translators)
1. Download [Poedit](https://poedit.net/)
2. Open the template: `insigner.pot` (from the core `languages/` folder, or request it from support)
3. **Create new translation** → select your language / locale code (e.g. `nl_NL`, `ja`, `pl_PL`)
4. Translate strings and save as:
```text
insigner-{locale}.po
```
Poedit generates the matching `.mo` automatically
5. Optional: create matching files for each addon domain you use
6. Upload the `.mo` files to:
```text
wp-content/languages/plugins/
```
7. Set WordPress / WPsigner to that locale so the files load
### Option C — WP-CLI (developers)
From the plugin root (development environment):
```bash
# Refresh the template from source
wp i18n make-pot . languages/insigner.pot --domain=insigner
# Create a new PO from the template
wp i18n make-po languages/insigner.pot languages/insigner-nl_NL.po
# Compile MO after translating the PO
wp i18n make-mo languages/
```
Copy the compiled `insigner-nl_NL.mo` to `wp-content/languages/plugins/` on the site.
---
## Contribute an official language pack
If you want the language published in the **WPsigner → Languages** catalog for all customers:
1. Complete `.po` / `.mo` files for core (`insigner`) and ideally the addons you care about
2. Package a ZIP with **forward-slash** paths and this layout:
```text
wpsigner-lang-{locale}-{version}.zip
├── insigner-{locale}.mo (required)
├── insigner-smart-forms-{locale}.mo (optional)
├── insigner-document-builder-{locale}.mo (optional)
├── insigner-mainwp-{locale}.mo (optional)
└── wpsigner-approveme-importer-{locale}.mo (optional)
```
3. Send the ZIP to WPsigner support / your account manager, **or** (partners with License Manager access) upload it under **License Manager → Language Packs**
4. After publication, customers can install it from **WPsigner → Languages**
> **important**
Do not rely on translate.wordpress.org for WPsigner. Packs must go through the WPsigner language pack catalog.
---
## Troubleshooting
| Symptom | Fix |
|---------|-----|
| Languages page empty / cannot install | Activate a valid WPsigner license |
| Pack installed but UI still English | Click **Activate** on the pack; confirm the `.mo` exists under `wp-content/languages/plugins/` |
| Only some screens translated | Translate / include the matching addon domain `.mo` |
| Custom PO ignored | Check file name `{domain}-{locale}.mo`; clear caches; avoid conflicting active pack |
| Need a new locale ASAP | Use Loco or Poedit locally while waiting for an official pack |
| Vietnamese / accented names missing or boxes on the signed PDF | Install **Accented Latin** under **Signed PDF fonts**, then **Use for signed PDFs**. Re-complete a test document — already flattened PDFs are not rewritten |
| Chinese / Japanese / Korean / Arabic / Thai / Hebrew look wrong | Install that language’s PDF font pack (not Accented Latin) and make it the active pack |
| Font install fails | The site must reach the Noto download URL once. Check outbound HTTPS, then retry |
| Two packs installed, wrong script in new PDFs | Only one pack is active. Click **Use for signed PDFs** on the pack you need |
---
## Next Steps
- [Creating Documents](/core-features/creating-documents/) — Add signers and send a test PDF after installing a font pack
- [Whitelabeling](/customization/whitelabeling/) — Brand the signing experience
- [Email Templates](/customization/email-templates/) — Customize notification copy (per language workflow as needed)
- [Account Portal](/addons/account-portal/) — License and downloads
- [Support](/support/) — Contact WPsigner if you need a pack published
---
# Digital Identity & Security
> Configure signer verification, PDF certificates, cryptographic timestamps, encryption, and audit evidence in WPsigner.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/digital-identity/
Markdown: https://docs.wpsigner.com/md/digital-identity.md
WPsigner supports **signer verification**, **cryptographic timestamping**, and **tamper-evident audit trails**. These features strengthen the evidence associated with signed documents and can support a broader compliance program.
---
## Guides
| Guide | Description |
|-------|-------------|
| [Digital ID (.p12)](/digital-identity/digital-id/) | Import or generate PKI certificates to embed a digital identity into every signed PDF |
| [Timestamping (TSA)](/digital-identity/timestamping/) | Add RFC 3161 timestamps from a trusted authority to prove exactly when a document was signed |
| [Audit Trails](/digital-identity/audit-trails/) | Automatic logging of every action — IP addresses, device info, timestamps, and geolocation |
| [Security & Compliance](/core-features/security-compliance/) | Configure OTP, KYC, access codes, evidence capture, and policy modes |
---
## Why It Matters
Electronic signatures are legally valid in most jurisdictions, but the strength of that validity depends on the evidence you can provide. WPsigner's digital identity features create multiple layers of proof:
| Layer | What It Proves | Technology |
|-------|---------------|------------|
| **Digital Certificate** | Which certificate sealed the completed PDF | X.509 PKI, .p12/.pfx |
| **Timestamp** | When they signed (independently verified time) | RFC 3161 TSA |
| **Audit Trail** | What happened (complete event history) | SHA-256 hashed log entries |
| **Document Hash** | The document wasn't altered after signing | SHA-256 integrity check |
Together, these layers can help provide evidence relevant to **ESIGN**, **UETA**, **eIDAS**, and other electronic-signature frameworks. The required controls depend on the transaction, identity method, provider, and jurisdiction.
---
## How They Work Together
```
Signer Opens Document
↓
Signer gates completed (when configured)
↓
Signature Captured (drawn, typed, or uploaded)
↓
Timestamp Requested (TSA server certifies the time)
↓
Audit Trail Updated (action logged with IP, device, hash)
↓
PDF Sealed (certificate + timestamp embedded in the file)
```
The final PDF contains the digital certificate, the timestamp token, and a reference to the full audit trail — all embedded directly in the file for independent verification.
---
## Getting Started
- **Start with [Digital ID](/digital-identity/digital-id/)** if you want to embed cryptographic identity into your signed PDFs. You can use a self-generated certificate or import one from a Certificate Authority.
- **Add [Timestamping](/digital-identity/timestamping/)** to prove the exact signing time through an independent third party. WPsigner supports any RFC 3161-compliant TSA.
- **Review [Audit Trails](/digital-identity/audit-trails/)** to understand what WPsigner logs automatically and how to access the trail for compliance or disputes.
> **tip**
Choose controls according to transaction risk. A certificate, trusted timestamp, signer-verification gate, and detailed audit trail provide complementary evidence, but unnecessary identity checks can increase friction and privacy obligations.
---
# Audit Trails
> Understand the chronological evidence WPsigner records for document and signer events, and how to review or export it.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/digital-identity/audit-trails/
Markdown: https://docs.wpsigner.com/md/digital-identity/audit-trails.md
An audit trail is a chronological record of document and signer events. It can provide important evidence about identity, intent, timing, access, and integrity, but it does not automatically make a transaction enforceable or admissible.
## What is an Audit Trail?
An audit trail is a chronological record that captures:
- **Who** - The identity of each person involved
- **What** - Every action taken on the document
- **When** - Exact timestamps of each action
- **Where** - IP addresses and geographic information
- **How** - Device and browser information
This creates an unbroken chain of evidence from document creation to completion.
---
## Why Audit Trails Are Essential
### Legal Foundation
Audit trails provide the legal foundation for electronic signatures under major regulations:
| Regulation | Audit Trail Requirement |
|------------|------------------------|
| **ESIGN Act** | Record of transaction |
| **UETA** | Attribution and intent |
| **eIDAS** | Identification and authentication |
| **HIPAA** | Access logs for PHI |
| **SOX** | Financial record integrity |
### Court Admissibility
In legal proceedings, audit trails provide:
| Evidence Type | What It Proves |
|--------------|----------------|
| **Identity** | Who signed (email, IP, device) |
| **Intent** | Deliberate actions were taken |
| **Timing** | When each action occurred |
| **Integrity** | Document wasn't altered |
| **Delivery** | Notification was sent |
### Non-Repudiation
Non-repudiation means signers cannot deny they signed. Audit trails establish this through:
1. **Unique signing link** - Sent only to signer's email
2. **Access logging** - When link was accessed
3. **Device fingerprint** - Browser and device info
4. **IP geolocation** - Physical location approximation
5. **Action sequence** - Deliberate steps to complete signing
---
## What WPsigner Captures
### Document Events
| Event | Captured Data |
|-------|---------------|
| **Created** | Creator user ID, timestamp, document hash |
| **Sent** | Send time, recipient emails |
| **Viewed** | View time, viewer identity, IP address |
| **Downloaded** | Download time, downloader, IP |
| **Voided** | Void time, reason, user who voided |
| **Expired** | Expiration timestamp |
### Signer Events
| Event | Captured Data |
|-------|---------------|
| **Email Delivered** | Delivery timestamp, email service response |
| **Link Accessed** | Access time, IP address, user agent |
| **Document Viewed** | View duration, pages viewed |
| **Fields Completed** | Each field with timestamp |
| **Signature Drawn** | Stroke data, completion time |
| **Submitted** | Final submission timestamp |
| **Declined** | Decline reason, timestamp |
### Technical Metadata
| Data Point | Description | Purpose |
|------------|-------------|---------|
| **IP Address** | IPv4/IPv6 address | Geographic attribution |
| **User Agent** | Browser and OS | Device identification |
| **Geolocation** | Approximate location | Location verification |
| **Session ID** | Unique session identifier | Action correlation |
| **Timezone** | Signer's timezone | Time context |
---
## Certificate of Completion
### What Is It?
The Certificate of Completion is a human-readable summary of the audit trail, automatically appended to the final signed PDF.
### Why It's Important
- **Self-contained** - All evidence in one document
- **Readable** - Non-technical parties can understand
- **Comprehensive** - Full history at a glance
- **Portable** - Travels with the document forever
### Certificate Contents
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CERTIFICATE OF COMPLETION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Document: Service Agreement 2026
Document ID: 7f8c9d2e-1234-5678-abcd-ef1234567890
Status: COMPLETED
DOCUMENT HASH (SHA-256):
a1b2c3d4e5f6789...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SIGNERS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Signer 1: John Smith (john@company.com)
• Role: Buyer
• Viewed: Jan 15, 2026 10:32:15 AM UTC
• Signed: Jan 15, 2026 10:35:42 AM UTC
• IP Address: 192.168.1.100
• Device: Chrome 120 on Windows 11
Signer 2: Jane Doe (jane@vendor.com)
• Role: Seller
• Viewed: Jan 15, 2026 2:15:22 PM UTC
• Signed: Jan 15, 2026 2:18:03 PM UTC
• IP Address: 10.0.0.50
• Device: Safari 17 on macOS Sonoma
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TIMELINE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Jan 14, 2026 3:00:00 PM - Document created
Jan 14, 2026 3:05:12 PM - Sent for signing
Jan 15, 2026 10:32:15 AM - Viewed by John Smith
Jan 15, 2026 10:35:42 AM - Signed by John Smith
Jan 15, 2026 2:15:22 PM - Viewed by Jane Doe
Jan 15, 2026 2:18:03 PM - Signed by Jane Doe
Jan 15, 2026 2:18:03 PM - Document completed
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Powered by WPsigner | Verify at: wpsigner.com/verify
```
### QR Code Verification
Each certificate includes a QR code that links to an online verification page, allowing anyone to:
- Confirm document authenticity
- View the complete audit trail
- Verify timestamp validity
- Download the original signed PDF
---
## Viewing Audit Trails
### In WordPress Admin
1. Go to **WPsigner → Documents**
2. Click on any document
3. Click the **Audit Trail** tab
4. View complete history with all events
### In the Downloaded PDF
1. Open the signed PDF
2. Scroll to the last page(s)
3. View the Certificate of Completion
4. Scan QR code for online verification
### Via REST API
```http
GET /wp-json/insigner/v1/documents/{id}/audit
```
Returns JSON with complete audit history:
```json
{
"document_id": 123,
"events": [
{
"type": "created",
"timestamp": "2026-01-14T15:00:00Z",
"user_id": 1,
"ip_address": "192.168.1.1"
},
{
"type": "viewed",
"timestamp": "2026-01-15T10:32:15Z",
"signer_id": 1,
"ip_address": "192.168.1.100",
"user_agent": "Mozilla/5.0..."
}
]
}
```
---
## Legal Best Practices
### Document Retention
| Industry | Retention Period | Regulation |
|----------|-----------------|------------|
| General business | 7 years | General practice |
| Healthcare | 6-10 years | HIPAA |
| Financial | 7 years | SOX |
| Employment | Duration + 7 years | Various |
| Government | Varies | Specific regulations |
### Backup Strategy
Protect your audit trails:
1. **Regular backups** - Daily database backups
2. **Off-site storage** - Store copies externally
3. **Encryption** - Encrypt backup files
4. **Testing** - Verify restore capability
5. **Retention policy** - Define how long to keep
### Access Control
Limit who can view audit trails:
| Role | Access Level |
|------|-------------|
| **WordPress Administrator / WPsigner Admin** | Full access to all audits |
| **Manager** | Audit trails for all documents |
| **Viewer** | Read-only audit access for all documents; sensitive signer details remain permission-scoped |
| **Sender** | Audit trails for documents they created |
See [Team Roles & Permissions](/core-features/team-roles/) for the full document and signer-detail access matrix.
---
## Audit Trail Integrity
### How Integrity Is Ensured
WPsigner protects audit trail integrity through:
| Protection | Method |
|------------|--------|
| **Immutability** | Events are append-only, never modified |
| **Timestamps** | Server-based, not client-provided |
| **Hashing** | SHA-256 hash of event chain |
| **Database** | Structured storage with constraints |
| **Signing** | Digital signature on completion |
### Tamper Detection
If someone attempts to modify an audit trail:
1. Hash chain breaks
2. Digital signature becomes invalid
3. Adobe Reader shows "Document has been modified"
4. Certificate of Completion doesn't match data
---
## Compliance & Regulations
### ESIGN Act Requirements
The ESIGN Act requires:
- ✅ Record of transaction process
- ✅ Consent to electronic records
- ✅ Ability to retain records
**WPsigner provides**: Complete audit trails fulfill all requirements.
### HIPAA Audit Requirements
For healthcare documents:
- ✅ Access logs (who viewed what, when)
- ✅ User identification
- ✅ Automatic logoff (session management)
**WPsigner provides**: Full access logging with IP and device info.
### SOX Compliance
For financial documents:
- ✅ Document integrity verification
- ✅ Access controls
- ✅ Audit trail of all modifications
**WPsigner provides**: Immutable audit trails with hash verification.
---
## Frequently Asked Questions
### How long are audit trails stored?
By default, audit trails are stored indefinitely in your WordPress database. Define a retention policy based on your industry requirements.
### Can audit trails be exported?
Yes. Export as:
- JSON via REST API
- Part of signed PDF (Certificate of Completion)
- CSV export from admin panel
### What if a signer disputes their signature?
The audit trail provides evidence of:
- Email delivery to their address
- Link accessed from specific IP
- Device information matching their typical device
- Specific actions taken (drawing signature, clicking submit)
This evidence typically resolves disputes definitively.
### Are IP addresses accurate?
IP addresses are captured accurately, but:
- VPNs may mask true location
- Corporate networks may show company IP
- Mobile networks may show carrier IP
The IP combined with other factors (email, device) establishes identity.
---
## Next Steps
- [Digital ID](/digital-identity/digital-id/) - Cryptographic signing
- [Timestamping (TSA)](/digital-identity/timestamping/) - Prove when signed
- [Compliance](/compliance/) - Regulatory requirements
---
# Digital ID (PKI Certificates)
> Configure the PKI certificate WPsigner uses to cryptographically seal completed PDFs and help recipients detect later changes.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/digital-identity/digital-id/
Markdown: https://docs.wpsigner.com/md/digital-identity/digital-id.md
A Digital ID (also called a digital certificate or PKI certificate) lets WPsigner cryptographically seal a completed PDF. This page explains what certificates do, their trust limitations, and how to configure them.
## What is a Digital ID?
A Digital ID is a cryptographic certificate that:
1. **Verifies your identity** - Proves who signed the document
2. **Seals the document** - Creates a tamper-evident container
3. **Establishes trust** - Third-party validation of authenticity
4. **Enables long-term validity** - Signatures remain valid for years
Think of it as a digital passport or notary stamp for your electronic documents.
---
## Why Digital IDs Matter
### The Problem Without Digital IDs
Without a Digital ID, your signed PDF is essentially just an image of a signature placed on a document. Anyone could:
- Modify the document after signing
- Claim the signature was forged
- Dispute when the document was signed
- Question who actually signed
### The Solution With Digital IDs
A Digital ID provides cryptographic proof:
| Without Digital ID | With Digital ID |
|-------------------|-----------------|
| Signature is just an image | Signature is cryptographically bound |
| Document can be modified | Any modification breaks the seal |
| No identity verification | Identity verified by certificate |
| Less independent integrity evidence | Stronger technical evidence |
| Fewer compliance controls | Can support a broader compliance program |
---
## Legal Importance
### Regulatory Compliance
Digital IDs enable compliance with major e-signature regulations:
| Regulation | Region | Digital ID Role |
|------------|--------|-----------------|
| **ESIGN Act** | USA | Provides intent attribution |
| **UETA** | USA (all states) | Establishes signer identity |
| **eIDAS** | European Union | Required for Advanced/Qualified signatures |
| **ZertES** | Switzerland | Required for qualified signatures |
| **IT Act** | India | Required for legally valid signatures |
### Court Admissibility
In a dispute, a valid certificate signature can provide evidence that:
- **Certificate identity** - Identifies the certificate that sealed the PDF
- **Tamper evidence** - Later PDF changes can invalidate the signature
- **Integrity** - Connects the signed byte range to the certificate's private key
- **Time evidence** - A trusted timestamp can establish independent time evidence
It does not by itself prove the human signer's identity or make a document automatically admissible or enforceable.
### Industry Requirements
Certain industries require digital certificates:
| Industry | Requirement | Reason |
|----------|-------------|--------|
| **Healthcare** | HIPAA compliance | PHI protection |
| **Finance** | SOX, PCI-DSS | Financial records integrity |
| **Government** | NIST, FedRAMP | Security standards |
| **Legal** | Bar association rules | Document authenticity |
| **Pharma** | FDA 21 CFR Part 11 | Regulatory submissions |
---
## Types of Digital Certificates
### Self-Signed Certificates
Created by you, for internal use.
**Best For:**
- Internal company documents
- Testing and development
- Non-legal agreements
- Team acknowledgments
**Pros:**
- Free to create
- Instant availability
- Full control
**Cons:**
- Not trusted by default in Adobe Reader
- Recipients see "Unknown Signer" warning
- Less credible for external parties
### Commercially Issued Certificates
Purchased from a trusted Certificate Authority (CA).
**Best For:**
- Client-facing contracts
- Legal agreements
- Regulatory filings
- Any document requiring third-party validation
**Pros:**
- Automatically trusted in Adobe Reader
- CA verifies your identity
- Stronger third-party trust signal
- Green checkmark in Adobe
**Cons:**
- Annual cost ($200-$500/year)
- Identity verification process
- Renewal required
### Certificate Authority Comparison
| Certificate Authority | Price Range | Verification Level |
|----------------------|-------------|-------------------|
| **DigiCert** | $300-500/yr | Organization validated |
| **Sectigo (Comodo)** | $150-300/yr | Organization validated |
| **GlobalSign** | $250-400/yr | Organization validated |
| **SSL.com** | $150-250/yr | Individual/Organization |
| **Entrust** | $300-500/yr | Enterprise grade |
> **tip**
For most businesses, **DigiCert** or **GlobalSign** offer the best balance of trust and support. Their certificates are on Adobe's Approved Trust List (AATL).
---
## How Digital Signing Works
### The Signing Process
When WPsigner finalizes a document with your Digital ID:
```
1. Document Hash Created
└─ SHA-256 hash of entire PDF content
2. Hash Encrypted
└─ Your private key encrypts the hash
3. Signature Embedded
└─ Encrypted hash + your certificate added to PDF
4. Timestamp Applied
└─ TSA server certifies the signing time
5. Sealed PDF Created
└─ Final document with digital signature
```
### Verification Process
When someone opens the signed PDF in Adobe Reader:
```
1. Extract Signature
└─ Adobe reads the embedded signature
2. Verify Certificate
└─ Checks if CA is trusted (AATL)
3. Validate Hash
└─ Recalculates hash and compares
4. Check Timestamp
└─ Verifies signing time
5. Display Status
└─ ✅ Valid or ❌ Invalid
```
---
## Configuring Your Digital ID
### Accessing Digital ID Settings
1. Go to **WPsigner → More → Digital ID**
2. Use **WPsigner → More → Security & Compliance** to configure the related signature security policies and timestamp provider
### Option 1: Generate Self-Signed Certificate
For testing or internal use:
1. Click **Generate Self-Signed Certificate**
2. Fill in the certificate details:
| Field | Description | Example |
|-------|-------------|---------|
| **Common Name** | Your name or company | Acme Corporation |
| **Organization** | Company name | Acme Corp |
| **Department** | Optional department | Legal Department |
| **City** | Your city | San Francisco |
| **State/Province** | Your state | California |
| **Country** | Two-letter code | US |
| **Email** | Contact email | legal@acme.com |
| **Valid Years** | Certificate lifetime | 3 years |
3. Click **Generate Certificate**
4. Certificate is created and activated immediately
### Option 2: Upload Commercial Certificate
For production use with purchased certificate:
1. Obtain a .p12 or .pfx file from your CA
2. Click **Upload Certificate**
3. Select your .p12/.pfx file
4. Enter the certificate password
5. Click **Upload and Activate**
### Certificate File Formats
| Format | Extension | Description |
|--------|-----------|-------------|
| **PKCS#12** | .p12, .pfx | Contains private key + certificate |
| **PEM** | .pem, .crt | Certificate only (convert to .p12) |
| **DER** | .der, .cer | Binary format (convert to .p12) |
WPsigner accepts **.p12** and **.pfx** files directly.
---
## Adobe Trust List (AATL)
### What is AATL?
The Adobe Approved Trust List is a list of Certificate Authorities that Adobe automatically trusts. When you sign with an AATL certificate:
- Adobe Reader shows a **green checkmark** ✅
- Recipients see "Signature is VALID"
- No manual trust configuration needed
- Maximum legal credibility
### AATL Members Include:
- DigiCert
- GlobalSign
- Sectigo
- Entrust
- IdenTrust
- DocuSign (certificate program)
- SwissSign
### Non-AATL Certificates
Self-signed certificates show:
- Yellow warning triangle ⚠️
- "Signature validity is UNKNOWN"
- Recipient must manually trust your certificate
The cryptographic signature can still be verified, but recipients must establish trust manually. Legal effect depends on the complete transaction and applicable law.
---
## Certificate Best Practices
### Security
| Practice | Why |
|----------|-----|
| **Strong password** | Protect your private key |
| **Secure storage** | Store .p12 file safely |
| **Limited access** | Only authorized staff should access |
| **Backup** | Keep secure backup of certificate |
| **Regular rotation** | Replace before expiration |
### Organizational
| Practice | Why |
|----------|-----|
| **Centralized management** | One certificate for all documents |
| **Document policy** | Define which docs need signing |
| **Training** | Educate staff on certificate importance |
| **Audit logging** | Track certificate usage |
### Renewal Planning
Certificates expire. Plan ahead:
1. **Set calendar reminder** - 60 days before expiration
2. **Budget annually** - Include in IT budget
3. **Test new certificate** - Verify before old expires
4. **Update WPsigner** - Upload new certificate
---
## Troubleshooting
### "Certificate password incorrect"
- Verify the password provided by your CA
- Passwords are case-sensitive
- No spaces before/after password
### "Certificate format not supported"
- Convert to .p12 format using OpenSSL:
```bash
openssl pkcs12 -export -out certificate.p12 -inkey private.key -in certificate.crt
```
### "Certificate has expired"
- Purchase a renewal from your CA
- Generate a new self-signed certificate
- Upload the new certificate to WPsigner
### Adobe shows "Signature validity unknown"
For self-signed certificates, recipients must:
1. Click on the signature
2. Click "Validate Signature"
3. Choose "Trust this certificate"
---
## Certificate vs No Certificate
### Documents Signed Without Digital ID
```
┌─────────────────────────────────┐
│ Signed PDF │
│ ┌─────────────────────────────┐ │
│ │ [Signature Image] │ │
│ │ - Just a PNG image │ │
│ │ - No cryptographic seal │ │
│ │ - Can be modified │ │
│ └─────────────────────────────┘ │
│ ⚠️ No verification available │
└─────────────────────────────────┘
```
### Documents Signed With Digital ID
```
┌─────────────────────────────────┐
│ Digitally Signed PDF │
│ ┌─────────────────────────────┐ │
│ │ [Signature + Certificate] │ │
│ │ ┌───────────────────────┐ │ │
│ │ │ SHA-256 Hash │ │ │
│ │ │ Private Key Signature │ │ │
│ │ │ X.509 Certificate │ │ │
│ │ │ RFC 3161 Timestamp │ │ │
│ │ └───────────────────────┘ │ │
│ └─────────────────────────────┘ │
│ ✅ Signature valid. Document │
│ has not been modified. │
└─────────────────────────────────┘
```
---
## Frequently Asked Questions
### Do I need a Digital ID for legal signatures?
For basic contracts in the US under ESIGN/UETA, a signature without Digital ID can be legally valid. However, a Digital ID provides much stronger legal protection and is recommended for:
- High-value contracts
- Regulated industries
- International agreements
- Long-term records
### Can I use one certificate for multiple documents?
Yes. Your certificate is reused for all documents you sign. There's no per-document cost or limit.
### What happens if my certificate expires?
- Previously signed documents remain valid (signature was valid at signing time)
- New documents cannot be signed until you upload a new certificate
- Consider timestamping to extend long-term validity
### Is a self-signed certificate legally valid?
A self-signed certificate can provide integrity evidence, but it does not provide third-party identity validation. Whether the overall electronic signature is legally effective depends on the transaction, signer evidence, consent, retention, and applicable law.
---
## Next Steps
- [Audit Trails](/digital-identity/audit-trails/) - Understand the legal record
- [Timestamping (TSA)](/digital-identity/timestamping/) - Prove when documents were signed
- [Compliance](/compliance/) - Regulatory requirements
---
# Document Encryption
> How WPsigner encrypts documents at rest with AES-256-GCM, and how to configure a dedicated encryption key for maximum security.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/digital-identity/encryption/
Markdown: https://docs.wpsigner.com/md/digital-identity/encryption.md
WPsigner encrypts all uploaded documents and signature images at rest using **AES-256-GCM**, the same encryption standard used by banks and government agencies. This ensures that even if your server's filesystem or database is compromised, your documents remain unreadable.
## How It Works
### Encryption at Rest
When a document is uploaded to WPsigner:
1. **Random filename generated** — A cryptographically random 128-bit filename replaces the original
2. **File encrypted** — AES-256-GCM encrypts the file contents with a unique IV (initialization vector)
3. **Stored securely** — The encrypted file is saved with a `.enc` extension
4. **Decrypted on demand** — Only when an authorized user requests the file
| Layer | Protection |
|-------|-----------|
| **Encryption** | AES-256-GCM (authenticated encryption) |
| **Filename** | Random 128-bit hex (impossible to guess) |
| **Access control** | `.htaccess` blocks direct URL access |
| **Directory listing** | `index.php` prevents browsing |
### What Gets Encrypted
| Content | Encrypted? |
|---------|-----------|
| Uploaded PDF documents | ✅ Yes |
| Signature images | ✅ Yes |
| Completed signed PDFs | Generated on-the-fly |
| Database records | No (metadata only) |
---
## Encryption Key
WPsigner derives its encryption key automatically from your WordPress security salts (`AUTH_KEY` and `SECURE_AUTH_SALT` in `wp-config.php`). This works out of the box, but has one risk: **if those salts are ever regenerated, all encrypted documents become permanently unreadable**.
### Why Define a Dedicated Key
Defining `WPS_ENCRYPTION_KEY` in your `wp-config.php` eliminates this risk entirely:
| Scenario | Without `WPS_ENCRYPTION_KEY` | With `WPS_ENCRYPTION_KEY` |
|----------|------------------------------|---------------------------|
| Normal operation | ✅ Works | ✅ Works |
| WordPress salts rotated | ❌ **Documents lost** | ✅ No impact |
| Security plugin regenerates salts | ❌ **Documents lost** | ✅ No impact |
| Migrate to new server | ⚠️ Must copy exact salts | ✅ Just copy the key |
| Multiple environments | ⚠️ Must sync salts | ✅ Share one key |
> **caution**
WordPress security plugins like **Solid Security (iThemes)**, **Wordfence**, and **SG Security** can regenerate salts with a single click. If you haven't defined `WPS_ENCRYPTION_KEY`, this can make encrypted documents permanently inaccessible.
---
## Setting Up Your Encryption Key
### Step 1: Generate a Key
WPsigner shows a generated key in the admin notice. You can also generate one manually:
**Using WP-CLI:**
```bash
wp eval "echo base64_encode(random_bytes(32));"
```
**Using PHP:**
```php
echo base64_encode(random_bytes(32));
```
This produces a 44-character Base64 string like `a8f3c9d1e6b20a4f7b8c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3g==`.
### Step 2: Add to wp-config.php
Open your `wp-config.php` file and add this line **before** the line that says `/* That's all, stop editing! */`:
```php
define('WPS_ENCRYPTION_KEY', 'your-generated-key-here');
```
### Step 3: Save Your Key
> **important**
**Store your encryption key in a secure location** (password manager, encrypted note, or offline backup). If you lose this key and need to reinstall WordPress, your encrypted documents cannot be recovered.
Recommended backup locations:
- Password manager (1Password, Bitwarden, etc.)
- Encrypted USB drive
- Printed and stored in a safe
- Your hosting provider's secret management
### Step 4: Verify
After adding the key, go to any WPsigner admin page. The security recommendation notice should disappear, confirming that WPsigner is now using your dedicated key.
---
## Key Priority
WPsigner checks for encryption keys in this order:
| Priority | Source | Where it lives |
|----------|--------|---------------|
| 1 (highest) | `WPS_ENCRYPTION_KEY` constant | `wp-config.php` (filesystem) |
| 2 (fallback) | Derived from WordPress salts | `wp-config.php` (filesystem) |
In both cases, the key **never** touches the database. It exists only in `wp-config.php` on the filesystem, protecting against SQL injection attacks.
---
## Salt Mismatch Warning
If WPsigner detects that your WordPress salts have changed (and you haven't defined `WPS_ENCRYPTION_KEY`), it will show a **critical red notice** in the admin:
> 🚨 **WPsigner — Encryption Key Changed**
> WordPress security salts have been regenerated. Previously encrypted documents cannot be decrypted with the current salts.
### How to Recover
1. **Restore original salts** — Find the original `AUTH_KEY` and `SECURE_AUTH_SALT` values from a backup of your `wp-config.php` and restore them
2. **If no backup exists** — The encrypted documents are permanently lost. You can dismiss the notice to reset the key for future documents
### Preventing This Issue
The best prevention is to define `WPS_ENCRYPTION_KEY` **before** any salt rotation occurs. Once defined, salt changes have zero impact on document encryption.
---
## Technical Details
### Cipher Specification
| Parameter | Value |
|-----------|-------|
| **Algorithm** | AES-256-GCM |
| **Key size** | 256 bits (32 bytes) |
| **IV size** | 96 bits (12 bytes, per NIST recommendation) |
| **Authentication tag** | 128 bits (16 bytes) |
| **Key derivation** | HMAC-SHA256 (when using salt fallback) |
### Why AES-256-GCM?
- **Authenticated encryption** — Detects any tampering with encrypted data
- **NIST approved** — Standard for US government classified information
- **Performance** — Hardware-accelerated on modern CPUs (AES-NI)
- **No padding oracle attacks** — GCM mode is immune to these
### File Format
Encrypted files are stored as:
```
Base64( IV (12 bytes) + Auth Tag (16 bytes) + Ciphertext )
```
The IV is generated using PHP's `random_bytes()` (CSPRNG) for each encryption operation, ensuring no two files share an IV.
---
## Frequently Asked Questions
### What happens if I change my WPS_ENCRYPTION_KEY?
All previously encrypted documents will become unreadable. Only change this key if you have no existing encrypted documents, or if you're prepared to lose access to them.
### Can I disable encryption?
Encryption is applied automatically when the OpenSSL extension is available (which is standard on all modern PHP installations). If OpenSSL is not available, files are stored without encryption with a warning in the logs.
### Does encryption affect performance?
Minimally. AES-256-GCM with hardware acceleration (AES-NI) encrypts at several GB/s. For typical documents (1-10MB), the overhead is imperceptible.
### Is the encryption key exposed in the database?
**No.** Whether you use `WPS_ENCRYPTION_KEY` or the salt-derived fallback, the key exists only in `wp-config.php` on the filesystem. A database breach (SQL injection) cannot expose the encryption key.
---
## Next Steps
- [Timestamping (TSA)](/digital-identity/timestamping/) — Add cryptographic timestamps to documents
- [Audit Trails](/digital-identity/audit-trails/) — Understanding the legal record
- [Digital ID](/digital-identity/digital-id/) — Configure your signing certificate
---
# Timestamping (TSA)
> Configure RFC 3161 timestamping to add independent cryptographic time evidence to completed PDFs.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/digital-identity/timestamping/
Markdown: https://docs.wpsigner.com/md/digital-identity/timestamping.md
Timestamping adds an independently signed time assertion for a document hash. It can support long-term verification when the certificate chain, timestamp token, revocation information, and PDF signature remain valid.
> **Lite vs Pro**
**Lite** records a **local** completion timestamp on your server. **External TSA** (RFC 3161) providers require **Pro**. [Lite vs Pro](/getting-started/lite-vs-pro/) · [Upgrade to Pro](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=upgrade&utm_campaign=timestamping)
## What is Timestamping?
A timestamp is a digitally signed assertion from a trusted third party (Timestamp Authority or TSA) that certifies:
1. **The document existed** at a specific moment
2. **The exact time** down to the second
3. **Independent verification** - not from your server
Think of it as a digital notary's date stamp that can never be forged or disputed.
---
## Why Timestamps Matter
### The Problem They Solve
Without timestamps, several issues arise:
| Problem | Risk | Example |
|---------|------|---------|
| **Backdating** | Someone claims document was signed earlier | Antedating a contract |
| **Expiration disputes** | Unclear if signed before deadline | Insurance claims |
| **Certificate expiry** | Signature invalid after cert expires | Old agreements |
| **Time manipulation** | Server clock changes | Fraud attempts |
### The Solution Timestamps Provide
| Benefit | How Timestamps Help |
|---------|---------------------|
| **Immutable proof** | Third-party certifies the exact moment |
| **Long-term validity** | Valid decades after certificate expires |
| **Independent verification** | Not dependent on your server |
| **Non-repudiation** | Signer cannot claim different date |
| **Regulatory compliance** | Meets strict archival requirements |
---
## Legal Importance
### Long-Term Validation (LTV)
LTV ensures signatures remain valid indefinitely:
| Without LTV | With LTV (Timestamp) |
|-------------|---------------------|
| Signature expires with certificate | Signature valid forever |
| Must verify against expired cert | Timestamp proves signing date |
| Questionable after years | Holds up in court decades later |
| Not suitable for archives | Perfect for long-term storage |
### Regulatory Requirements
Many regulations require or recommend timestamping:
| Regulation | Timestamping Requirement |
|------------|--------------------------|
| **eIDAS (EU)** | Required for Qualified Signatures |
| **FDA 21 CFR Part 11** | Required for pharma records |
| **HIPAA** | Recommended for healthcare records |
| **SOX** | Recommended for financial records |
| **ISO 27001** | Best practice for compliance |
### Court Acceptability
In legal proceedings, timestamps provide:
- **Definitive proof** of when signature occurred
- **Third-party validation** (not self-asserted)
- **Cryptographic evidence** that's mathematically verifiable
- **Chain of custody** for document timing
---
## How Timestamping Works
### The Technical Process
When WPsigner creates a timestamp:
```
1. Document Hash Created
└─ SHA-256 hash of the signed document
2. Timestamp Request Sent
└─ Hash sent to TSA server (not the document)
3. TSA Signs the Hash + Time
└─ TSA adds current time and digitally signs
4. Timestamp Response Returned
└─ Signed timestamp token received
5. Timestamp Embedded in PDF
└─ Token stored in document signature
```
### What Gets Sent to TSA?
**Only the document hash** - not the document itself.
| Sent | NOT Sent |
|------|----------|
| SHA-256 hash (32 bytes) | Document content |
| | Signer information |
| | Any personal data |
This means your documents remain completely private while still getting verified timestamps.
### Verification Process
When someone verifies a timestamped document:
1. Adobe extracts the timestamp token
2. Verifies TSA's digital signature
3. Confirms the hash matches the document
4. Displays the verified signing time
---
## RFC 3161 Standard
### What is RFC 3161?
RFC 3161 is the Internet standard for trusted timestamping, published by the IETF. It defines:
- Request/response format
- Cryptographic requirements
- Trust model
- Implementation guidelines
### RFC 3161 Compliance
WPsigner fully implements RFC 3161:
| Feature | Status |
|---------|--------|
| Standard request format | ✅ Compliant |
| SHA-256 hash algorithm | ✅ Supported |
| Nonce inclusion | ✅ Implemented |
| Certificate chain | ✅ Embedded |
| Response validation | ✅ Verified |
---
## Configuring Timestamping
### Accessing TSA Settings
1. Go to **WPsigner → More → Security & Compliance**
2. Find the **Timestamping** section
3. Enable timestamping with the toggle
### Configuration Options
| Setting | Description | Example |
|---------|-------------|---------|
| **Enable Timestamping** | Turn on/off | On |
| **TSA URL** | Timestamp server address | https://freetsa.org/tsr |
| **TSA Username** | If authentication required | (optional) |
| **TSA Password** | If authentication required | (optional) |
| **Hash Algorithm** | Hash type to use | SHA-256 |
### Default Configuration
WPsigner comes pre-configured with FreeTSA.org:
```
TSA URL: https://freetsa.org/tsr
Authentication: None required
Hash: SHA-256
```
This works immediately with no configuration needed.
---
## Timestamp Authorities
### Free TSA Services
| Provider | URL | Notes |
|----------|-----|-------|
| **FreeTSA.org** | https://freetsa.org/tsr | Free, reliable |
| **DigiCert** | https://timestamp.digicert.com | Free tier available |
| **Sectigo** | http://timestamp.sectigo.com | Free |
| **Apple** | http://timestamp.apple.com/ts01 | Free |
### Commercial TSA Services
For higher volumes or SLA guarantees:
| Provider | Features | Pricing |
|----------|----------|---------|
| **DigiCert** | High availability, support | Contact sales |
| **GlobalSign** | Enterprise SLA | Contact sales |
| **SwissSign** | Swiss privacy laws | Contact sales |
| **Entrust** | Government-grade | Contact sales |
### Choosing a TSA
Consider these factors:
| Factor | Importance | Notes |
|--------|------------|-------|
| **Reliability** | Critical | Must be available 24/7 |
| **Speed** | Important | Should respond in < 1 second |
| **Trust** | Critical | Well-known, established provider |
| **Location** | Consider | May matter for data residency |
| **Cost** | Variable | Free options available |
> **tip**
For most users, **FreeTSA.org** or **DigiCert's free service** is sufficient. Only consider paid services for enterprise volumes (1000+ documents/day) or strict SLA requirements.
---
## Testing Your Configuration
### Manual Test
1. Go to **WPsigner → More → Security**
2. Click **Test Timestamp Server**
3. WPsigner sends a test request
4. Result shows success or error message
### Verify in Signed PDF
1. Create and sign a test document
2. Download the completed PDF
3. Open in Adobe Reader
4. Click on the signature
5. View signature details
6. Check for "Timestamp" entry with time
### What Success Looks Like
In Adobe Reader, you'll see:
```
Signature is VALID
- Signed by: Your Name
- Signing time: Jan 15, 2026 2:30:15 PM
- The signature includes an embedded timestamp ✅
- Timestamp verified by: FreeTSA
```
---
## Understanding Timestamp Validity
### Timestamp vs Certificate Expiry
| Scenario | Signature Status |
|----------|-----------------|
| Certificate valid, no timestamp | ✅ Valid until cert expires |
| Certificate expired, no timestamp | ⚠️ Validity unknown |
| Certificate valid, with timestamp | ✅ Valid |
| Certificate expired, with timestamp | ✅ Still valid (LTV) |
### Long-Term Validation Explained
With a timestamp, validity works like this:
1. **At signing time**: Certificate was valid → timestamp records this
2. **Years later**: Certificate has expired
3. **Verification**: Timestamp proves cert was valid when signed
4. **Result**: Signature still valid, indefinitely
This is why timestamps are essential for documents you need to keep for years.
---
## Performance Considerations
### Timestamp Request Time
Each document requires a round-trip to the TSA:
| Factor | Impact |
|--------|--------|
| **TSA location** | Closer = faster |
| **Network latency** | Typically 100-500ms |
| **TSA load** | Varies by provider |
| **Your server location** | Affects latency |
### Optimization
For high-volume signing:
1. **Use a reliable TSA** - Avoid slow or unreliable servers
2. **Consider location** - Use geographically close TSA
3. **Background processing** - Timestamp asynchronously if possible
4. **Caching** - Not applicable (each doc needs unique timestamp)
---
## Troubleshooting
### "Timestamp request failed"
**Causes:**
- TSA server is down
- Network connectivity issues
- Incorrect TSA URL
- Firewall blocking requests
**Solutions:**
1. Test the TSA URL directly: `curl -I https://freetsa.org/tsr`
2. Try a different TSA server
3. Check firewall rules for outbound HTTPS
4. Verify server has internet access
### "Invalid timestamp response"
**Causes:**
- TSA server misconfiguration
- Response format error
- Certificate chain issue
**Solutions:**
1. Try a different TSA
2. Update PHP OpenSSL extension
3. Check PHP error logs for details
### "Timestamp not appearing in PDF"
**Causes:**
- Timestamping not enabled
- TSA request failed silently
- PDF generation issue
**Solutions:**
1. Verify timestamping is enabled in settings
2. Check that test timestamp works
3. Review document generation logs
---
## Comparing With and Without Timestamps
### Document Without Timestamp
```
┌─────────────────────────────────────┐
│ Signed PDF │
│ ┌─────────────────────────────────┐ │
│ │ Digital Signature │ │
│ │ • Signed: [Server time] │ │
│ │ • Certificate valid until 2027 │ │
│ └─────────────────────────────────┘ │
│ │
│ ⚠️ In 2028: "Certificate expired, │
│ signature validity unknown" │
└─────────────────────────────────────┘
```
### Document With Timestamp
```
┌─────────────────────────────────────┐
│ Signed PDF with Timestamp │
│ ┌─────────────────────────────────┐ │
│ │ Digital Signature │ │
│ │ • Signed: Jan 15, 2026 2:30 PM │ │
│ │ • Certificate valid until 2027 │ │
│ │ ┌───────────────────────────┐ │ │
│ │ │ RFC 3161 Timestamp │ │ │
│ │ │ • Time: Jan 15, 2026 │ │ │
│ │ │ • TSA: FreeTSA.org │ │ │
│ │ │ • Hash verified ✓ │ │ │
│ │ └───────────────────────────┘ │ │
│ └─────────────────────────────────┘ │
│ │
│ ✅ In 2028 and beyond: "Signature │
│ valid. Timestamp verified." │
└─────────────────────────────────────┘
```
---
## Frequently Asked Questions
### Is timestamping required for legal validity?
For basic e-signatures in the US, no. However, timestamps are required or recommended for:
- European qualified signatures (eIDAS)
- Pharmaceutical submissions (FDA)
- Long-term archival documents
- High-value contracts
### Does timestamping slow down signing?
Minimally. Typical overhead is 100-500ms per document. Users won't notice this in the signing flow.
### What if the TSA is down?
WPsigner will:
1. Retry the request
2. If still failing, complete signature without timestamp
3. Log the failure for your review
You can enforce timestamps by enabling "Require Timestamp" in settings.
### Can I add timestamps to old documents?
No. Timestamps must be applied at signing time. They prove when the signature was created - adding one later would defeat the purpose.
---
## Next Steps
- [Digital ID](/digital-identity/digital-id/) - Configure your certificate
- [Audit Trails](/digital-identity/audit-trails/) - Understanding the legal record
- [Compliance](/compliance/) - Regulatory requirements
---
# Getting Started
> Everything you need to install, configure, and start sending documents for signature with WPsigner.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/getting-started/
Markdown: https://docs.wpsigner.com/md/getting-started.md
Welcome to WPsigner — the self-hosted electronic signature plugin for WordPress. This section walks you through setup, from server checks to your first signed PDF.
WPsigner ships as **Lite** (free) and **Pro**. See **[Lite vs Pro](/getting-started/lite-vs-pro/)** before you install if you are unsure which edition you need.
---
## What You'll Learn
| Guide | Description | Time |
|-------|-------------|------|
| [Introduction](/getting-started/introduction/) | What WPsigner is, Lite vs Pro, and how it compares to SaaS | 5 min |
| [Lite vs Pro](/getting-started/lite-vs-pro/) | Feature matrix, limits, and upgrade without losing documents | 5 min |
| [System Requirements](/getting-started/requirements/) | PHP version, extensions, and server settings | 3 min |
| [Hosting Compatibility](/getting-started/hosting-compatibility/) | Recommended hosts, shared hosting, and go-live checklist | 3 min |
| [Installation](/getting-started/installation/) | Install Lite (wordpress.org) or Pro (Account Portal) | 5 min |
| [First Document (Lite)](/getting-started/first-document-lite/) | PDF → up to two signers → send (WordPress.org path) | 5 min |
| [Quick Start](/getting-started/quick-start/) | Create and send your first document for signature | 5 min |
| [System Status, Storage & Retention](/getting-started/system-status-and-storage/) | Diagnose cron, email, PDF, database, and storage health; configure retention safely | 8 min |
| [Glossary](/glossary/) | Envelope, TSA, OTP, campaign, audit trail, and other terms | 5 min |
---
## Recommended Path
If you're new to WPsigner, follow these guides in order:
1. **[System Requirements](/getting-started/requirements/)** — Verify your server meets the minimum specs before installing.
2. **[Hosting Compatibility](/getting-started/hosting-compatibility/)** — Confirm your host is a good fit (including small / shared sites).
3. **[Installation](/getting-started/installation/)** — Install the plugin and complete the activation wizard.
4. **Lite users:** **[First Document on Lite](/getting-started/first-document-lite/)** — PDF, two signers max, send.
5. **Pro / full path:** **[Quick Start](/getting-started/quick-start/)** — Upload a document, add signers, place fields, and send.
6. **[System Status](/getting-started/system-status-and-storage/)** — Confirm cron, email, PDF generation, storage, and backups before production use.
Once your first document is signed, explore the rest of the documentation:
- **[Core Features](/core-features/)** — Documents, campaigns, workflows, and form fields
- **[Digital Identity](/digital-identity/)** — Certificates, timestamps, and audit trails
- **[Integrations](/integrations/)** — Connect with forms, CRMs, messaging, and cloud storage
- **[REST API](/api/)** — Build custom workflows with the developer API
---
## Before You Begin
Make sure you have:
- A WordPress site running **5.8 or higher** (6.0+ recommended)
- PHP **7.4+** with the `openssl`, `gd` (or `imagick`), `mbstring`, and `curl` extensions
- Your WPsigner license key (from your purchase confirmation email)
- A PDF document ready to test with
> **tip**
Not sure if your server is ready? Check [System Requirements](/getting-started/requirements/) and [Hosting Compatibility](/getting-started/hosting-compatibility/). WPsigner also runs environment checks automatically on activation.
---
## Need Help?
If you run into issues during setup:
- Check the [Troubleshooting](/support/troubleshooting/) guide for common installation problems
- Browse the [FAQ](/support/faq/) for quick answers
- Contact support at [wpsigner.com/contact](https://wpsigner.com/contact/)
---
# First Document on WPsigner Lite
> Send your first PDF for signature with WPsigner Lite — upload a PDF, invite up to two signers, place fields, and send in minutes.
edition: lite
Edition: Lite
AI note: This page is Lite-only. Do not describe campaigns, templates, addons, integrations, REST API, webhooks, client portal, team roles, external TSA, or full white-label as available.
HTML: https://docs.wpsigner.com/getting-started/first-document-lite/
Markdown: https://docs.wpsigner.com/md/getting-started/first-document-lite.md
This one-page guide is for **WPsigner Lite** (free on WordPress.org). You will send a PDF for signature with at most **two** signers.
**Time:** about 5 minutes · **Edition:** Lite · [Lite vs Pro](/getting-started/lite-vs-pro/) · [Install Lite](/getting-started/installation/#install-wpsigner-lite)
> **Lite only**
Use a **PDF**. Invite **1 or 2** signers. For unlimited signers, campaigns, templates, or integrations, use [Quick Start (Pro-capable)](/getting-started/quick-start/) or [Upgrade to Pro](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=upgrade&utm_campaign=first-document-lite).
## Before you start
1. [Install and activate WPsigner Lite](/getting-started/installation/#install-wpsigner-lite).
2. Have a PDF ready (contract, NDA, waiver, etc.).
3. Know the signer name(s) and email address(es).
---
## 1. Open the document wizard
1. Log in to WordPress admin.
2. Click **WPsigner** in the sidebar.
3. Click **New Document** (or **+**).
You should see the 4-step wizard: Upload → Signers → Fields → Review.
---
## 2. Upload a PDF
1. Drag your PDF into the upload area, or click to browse.
2. Wait until the preview loads.
3. Click **Next**.
If the upload rejects the file, convert it to PDF. Lite does not accept PNG/JPG.
---
## 3. Add up to two signers
1. Enter **Name** and **Email** for the first signer.
2. Optionally click **Add Signer** for a second person (Lite maximum is **2**).
3. Choose **Parallel** (everyone at once) or **Sequential** (one after another).
4. Click **Next**.
> **caution**
A third signer is a **Pro** feature. Stay at two on Lite, or [upgrade](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=upgrade&utm_campaign=first-document-lite-signers).
---
## 4. Place fields on the PDF
1. Select a signer (color helps identify ownership).
2. Drag **Signature** (and optionally **Initials**, **Date**, **Text**) onto the page.
3. Resize and position fields where people must sign.
4. Click **Next**.
Tip: put at least one Signature field per signer or they cannot finish.
---
## 5. Review and send
1. Check title, signers, and field placement.
2. Optionally set an expiration date or require an access code / email OTP (Lite supports email OTP).
3. Click **Send**.
Each signer gets an email with a unique signing link. They can draw, type, or upload a signature on the public signing page.
---
## 6. Get the signed PDF
1. Open **WPsigner → Documents**.
2. When status is **Completed**, open the document.
3. Download the signed PDF and review the [audit trail](/digital-identity/audit-trails/).
Lite stores a **local** completion timestamp on your server (not an external TSA).
---
## Done — next steps
| Goal | Link |
|------|------|
| Understand Lite limits | [Lite vs Pro](/getting-started/lite-vs-pro/) |
| Terms (OTP, TSA, audit trail) | [Glossary](/glossary/) |
| Install or reinstall | [Installation](/getting-started/installation/) |
| Full product quick start (Pro features noted) | [Quick Start](/getting-started/quick-start/) |
| Field types reference | [Form Fields](/core-features/form-fields/) |
| Upgrade without losing documents | [Pricing](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=upgrade&utm_campaign=first-document-lite-footer) |
Need more than 2 signers? Upgrade to Pro
---
# Hosting Compatibility
> Hosting compatibility for WPsigner — recommended providers, shared hosting guidance, and hosts that may need extra configuration.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/getting-started/hosting-compatibility/
Markdown: https://docs.wpsigner.com/md/getting-started/hosting-compatibility.md
WPsigner runs on standard WordPress hosting. If your host supports WordPress and meets the [system requirements](/getting-started/requirements/), WPsigner will work. Performance scales with your server resources — larger PDFs, more concurrent signers, and heavy integrations benefit from adequate memory, CPU, and PHP execution time.
We regularly test WPsigner on small WordPress sites (shared hosting and lightweight VPS). On those environments the plugin runs smoothly for typical workloads: sending contracts, collecting signatures, and storing signed PDFs.
## What You'll Learn
- Recommended hosting providers for WPsigner
- How well WPsigner fits small sites and shared hosting
- Hosts or setups that may need additional configuration
- How to check firewall, cron, and PHP limits before go-live
---
## Recommended Hosts
### For freelancers and small companies
These providers are a good fit for freelancers, solo consultants, and small businesses on shared or entry-level WordPress plans. We use and recommend them for typical WPsigner workloads (contracts, signatures, and signed PDF storage) when [system requirements](/getting-started/requirements/) are met:
| Host | Best for | Notes |
|------|----------|-------|
| **[Raiola Networks](https://raiolanetworks.com)** | Freelancers and SMBs (especially Spanish-speaking markets) | WordPress-friendly shared and cloud plans with solid support |
| **[VeyoHost](https://veyohost.com)** | Small sites and agencies needing affordable WordPress hosting | Shared / WordPress plans suitable for day-to-day signing |
| **[SiteGround](https://siteground.com)** | Freelancers and small companies wanting managed WordPress tools | Easy PHP version control; confirm memory and upload limits for larger PDFs |
| **[Namecheap](https://www.namecheap.com)** | Budget-friendly shared hosting for small sites | Use a plan with PHP 8.1+, OpenSSL, and enough upload/memory headroom |
| **[Hostinger](https://www.hostinger.com)** | Freelancers and startups starting on shared hosting | Affordable WordPress hosting; raise PHP limits if you send large PDFs |
> **tip**
On these hosts, enable **PHP 8.1+** (or at least 7.4+), **OpenSSL**, and aim for **256MB** memory with a **10MB+** upload limit for comfortable PDF signing.
### Managed and higher-volume hosting
These hosts offer WordPress-optimized or cloud environments when you need more performance, staging, or daily high volume:
**[Cloudways](https://cloudways.com)** — Managed cloud hosting with easy PHP configuration. Ideal when you need higher `memory_limit`, upload limits, and outbound HTTPS for integrations.
**[Kinsta](https://kinsta.com)** — Managed WordPress on Google Cloud with strong performance, staging, and support — a solid choice for agencies sending documents daily.
**[Pressable](https://pressable.com)** — Managed WordPress with reliable uptime and WordPress.com infrastructure.
**[DigitalOcean](https://digitalocean.com) / [Vultr](https://vultr.com) / [Hetzner](https://hetzner.com)** — VPS options with full control over PHP extensions (OpenSSL, GD/Imagick) and limits. Best when you want to tune the server yourself.
> **note**
For day-to-day signing on small sites, shared hosting (Raiola, VeyoHost, SiteGround, Namecheap, Hostinger, and similar) is usually enough. Choose a managed or VPS plan when you process large PDFs often, use cloud storage sync, or need stricter uptime SLAs.
---
## General Compatibility
WPsigner has no inherent site-size limit. A slow or underpowered server affects the plugin the same way it affects WordPress overall — especially PDF upload, rendering, and digital sealing.
Before choosing a host:
1. Review the [System Requirements](/getting-started/requirements/)
2. Confirm the host meets [WordPress hosting requirements](https://wordpress.org/hosting/)
3. Verify required PHP extensions: `openssl`, `gd` or `imagick`, `mbstring`, `curl`, `json`, `zip`
4. Ensure HTTPS is available (required for production signing URLs)
### Small sites
WPsigner is a good fit for freelancers, agencies, and small businesses running WordPress on shared or entry-level plans. Typical small-site usage (a few documents per week, standard PDF sizes) does not require dedicated servers.
What helps most on small sites:
- PHP memory at least **128MB** (256MB+ preferred for larger PDFs)
- Upload limit at least **10MB** (32–64MB recommended)
- Working **WP-Cron** (or a real server cron) for reminders and webhooks
- Outbound HTTPS allowed (for TSA, webhooks, and cloud integrations)
---
## Hosts Requiring Additional Configuration
Most hosts work out of the box. These situations sometimes need an extra step:
| Scenario | Configuration needed | Where to look |
|----------|----------------------|---------------|
| Strict managed hosts (e.g. WP Engine) | Raise PHP memory / upload limits if large PDFs fail | Host panel or support ticket; see [Troubleshooting](/support/troubleshooting/) |
| Hosts that disable PHP functions | Ensure `curl`, OpenSSL, and temp-file related functions are available | Ask support to enable required extensions/functions |
| Shared plans with low limits | Increase `memory_limit`, `upload_max_filesize`, `post_max_size`, `max_execution_time` | `php.ini`, `.htaccess`, or host PHP selector |
| Security / WAF layers (Sucuri, Cloudflare, host WAF) | Allow PDF uploads and signing-page POSTs if blocked | WAF allowlist or [Troubleshooting](/support/troubleshooting/) |
| Outbound HTTPS blocked | Allow requests to TSA, webhook endpoints, Google APIs, etc. | Host firewall / outbound rules |
---
## Shared Hosting Considerations
Shared hosting environments sometimes limit PHP memory, upload size, or maximum run time. If you experience issues:
- Confirm OpenSSL and GD/Imagick are enabled
- Request higher `memory_limit` (256M) and `max_execution_time` (120+) for large documents
- Check whether the host disables outbound cURL — needed for webhooks, timestamping, and many integrations
- Prefer a real cron job if WP-Cron is unreliable under low traffic
- Keep PDFs reasonably sized; optimize before upload when possible
If signing or PDF processing still times out after raising limits, move to a VPS or managed WordPress plan with more CPU and memory.
---
## Firewall and Security Plugins
Some hosts and security plugins use web application firewalls (WAFs) that may block PDF uploads, signing form submissions, or webhook callbacks.
If something fails unexpectedly:
1. Check [Troubleshooting](/support/troubleshooting/) for upload and signing errors
2. Temporarily disable the WAF or security plugin to confirm the cause
3. Allowlist your signing URLs and, when relevant, webhook source IPs (e.g. identity providers)
4. Re-enable protection after allowlisting — do not leave the WAF off in production
---
## Self-Check Checklist
- [ ] Host meets [WPsigner system requirements](/getting-started/requirements/)
- [ ] PHP extensions enabled (`openssl`, `gd`/`imagick`, `mbstring`, `curl`)
- [ ] HTTPS active on the site
- [ ] Memory and upload limits suitable for your typical PDF size
- [ ] WP-Cron (or server cron) running for reminders and webhooks
- [ ] No WAF blocking uploads or signing POSTs
- [ ] Outbound HTTPS allowed if you use TSA, webhooks, or cloud storage
After install, open **WPsigner → More → System Status** and fix any ⚠️ / ❌ items.
---
## Related Resources
- [System Requirements](/getting-started/requirements/) — Minimum and recommended server specs
- [Installation](/getting-started/installation/) — Install and activate WPsigner
- [Troubleshooting](/support/troubleshooting/) — Fix common hosting and performance issues
- [FAQ](/support/faq/) — Licensing, features, and compatibility questions
---
# Installing WPsigner
> Install WPsigner Lite from WordPress.org or WPsigner Pro from the Account Portal — step-by-step for WordPress.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/getting-started/installation/
Markdown: https://docs.wpsigner.com/md/getting-started/installation.md
This guide covers both editions. Pick your path first, then follow the matching steps.
| Edition | Install from | Details |
|---------|--------------|---------|
| **Lite** (free) | WordPress admin → **Plugins → Add New**, or wordpress.org | PDF, max 2 signers — [Lite vs Pro](/getting-started/lite-vs-pro/) |
| **Pro** | [Account Portal](https://app.wpsigner.com/) ZIP | Full feature set |
> **Do not run both plugins active**
When **Pro** is active, Lite does not load. Keep one edition active. Upgrading to Pro keeps your existing Lite documents (same `wps_*` tables).
## Before You Begin
Ensure your server meets the [system requirements](/getting-started/requirements/):
- WordPress 5.8 or higher
- PHP 7.4 or higher
- OpenSSL extension enabled
- 128MB memory limit minimum
---
## Install WPsigner Lite
### Method A: Plugins → Add New (recommended)
1. Log in to WordPress admin
2. Go to **Plugins → Add New**
3. Search for **WPsigner**
4. Click **Install Now**, then **Activate**
5. Open the WPsigner menu and create your first PDF document (max two signers)
### Method B: Upload the Lite ZIP
1. Download the Lite package from wordpress.org (or your distribution ZIP named `wpsigner`)
2. In WordPress go to **Plugins → Add New → Upload Plugin**
3. Choose the ZIP → **Install Now** → **Activate**
---
## Install WPsigner Pro
### Method 1: Upload via WordPress Admin (Recommended)
This is the easiest method for most Pro customers.
**Step 1: Download the Plugin**
1. Log in to your [WPsigner Account Portal](https://app.wpsigner.com/)
2. Open the **Downloads** tab for the main WPsigner plugin
3. For official addons (for example Smart Signing Forms), use the **[Addons](https://app.wpsigner.com/account/?portal_tab=addons)** tab instead
4. Click **Download** to get the latest ZIP file
5. Save the file to your computer (do not unzip it)
See [Account Portal](/addons/account-portal/) and [Addons Overview](/addons/overview/) for addon downloads.
**Step 2: Upload to WordPress**
1. Log in to your WordPress admin dashboard
2. Navigate to **Plugins → Add New**
3. Click the **Upload Plugin** button at the top
4. Click **Choose File** and select the Pro ZIP file
5. Click **Install Now**
6. Wait for the upload and installation to complete
**Step 3: Activate the Plugin**
1. After installation, click **Activate Plugin**
2. You'll be redirected to the WPsigner dashboard
3. Follow the welcome wizard to complete initial setup
If Lite was installed earlier, deactivate or remove Lite after Pro activates successfully. Your documents remain.
---
### Method 2: FTP/SFTP Upload
Use this method if you have server access or the admin upload fails.
**Step 1: Extract the Plugin**
1. Download the Pro ZIP from your account
2. Extract/unzip the file on your computer
3. You should have a folder for the Pro plugin (typically `insigner` or as documented in your download)
**Step 2: Connect via FTP**
1. Open your FTP client (FileZilla, Cyberduck, etc.)
2. Connect to your server using your FTP credentials
3. Navigate to `/wp-content/plugins/`
**Step 3: Upload the Folder**
1. Upload the entire Pro plugin folder (for example `insigner`) to `/wp-content/plugins/`
2. Wait for all files to transfer (this may take a few minutes)
3. Verify the main plugin file is present inside that folder (for example `insigner.php`)
**Step 4: Activate in WordPress**
1. Log in to WordPress admin
2. Go to **Plugins → Installed Plugins**
3. Find **WPsigner** (Pro) in the list
4. Click **Activate**
5. If Lite is also installed, deactivate Lite so only Pro runs
---
### Method 3: WP-CLI (Advanced)
For developers and automated deployments:
```bash
# Navigate to WordPress directory
cd /path/to/wordpress
# Install from local zip file
wp plugin install /path/to/wpsigner.zip --activate
# Or if you have direct download URL
wp plugin install https://wpsigner.com/download/wpsigner.zip --activate
```
---
## Post-Installation Setup
After activating WPsigner, complete these essential configuration steps:
### 1. Configure Digital ID
Your Digital ID is required for signing documents with legal validity.
1. Go to **WPsigner → More → Digital ID**
2. Choose between:
- **Generate Self-Signed**: Quick setup for testing or internal use
- **Upload Certificate**: Use your own .p12/.pfx certificate from a Certificate Authority
> **tip**
For production workflows that need a publicly trusted PDF certificate, evaluate an appropriate certificate from a recognized provider such as DigiCert, Sectigo, or GlobalSign.
### 2. Set Up Email
Ensure signing request emails are delivered reliably.
1. Go to **WPsigner → Settings → Email**
2. Configure SMTP settings (recommended) or use default WordPress mail
3. Customize email templates if desired
4. Send a test email to verify delivery
**Recommended SMTP plugins:**
- WP Mail SMTP
- FluentSMTP
- Post SMTP
### 3. Configure Branding (Optional)
Add your company's branding for a professional experience.
1. Go to **WPsigner → Settings → Branding**
2. Upload your company logo
3. Set your brand colors
4. Customize the signing page appearance
### 4. Set Permalinks
WPsigner requires pretty permalinks for signing URLs.
1. Go to **Settings → Permalinks**
2. Select any option except "Plain"
3. Click **Save Changes**
---
## Verifying Installation
### Check System Status
1. Go to **WPsigner → More → System Status**
2. Review the health check results
3. Ensure all requirements show green checkmarks
### Common Status Checks
| Check | Expected Result |
|-------|-----------------|
| PHP Version | ✅ 7.4 or higher |
| OpenSSL | ✅ Enabled |
| Memory Limit | ✅ 128MB+ |
| Upload Size | ✅ 10MB+ |
| Permalinks | ✅ Enabled |
| WP Cron | ✅ Working |
### Create a Test Document
1. Go to **WPsigner → New Document**
2. Upload a sample PDF
3. Add yourself as a signer
4. Place a signature field
5. Send the document
6. Check your email and complete the signing
If the test completes successfully, your installation is working correctly!
---
## Updating WPsigner
### Automatic Updates
WPsigner supports WordPress automatic updates:
1. Go to **Plugins → Installed Plugins**
2. Find WPsigner
3. Click **Enable auto-updates** (if available)
### Manual Updates
1. Download the latest version from your account
2. Deactivate the current WPsigner plugin
3. Delete the old plugin (your data is safely stored in the database)
4. Install the new version following Method 1 above
5. Activate the plugin
> **important**
Your documents, signers, and settings are stored in the database and are not deleted by a normal plugin update. Create a backup before updating.
---
## Multisite Installation
For WordPress Multisite networks:
### Network Activation
1. Download and upload `wpsigner.zip`
2. Go to **Network Admin → Plugins**
3. Click **Network Activate** for all sites
### Per-Site Activation
1. Upload the plugin to the network
2. Each site admin can activate independently
3. Settings are configured per-site
---
## Troubleshooting Installation
### "Plugin could not be activated"
**Cause**: PHP version too low or missing extension
**Solution**:
1. Check your PHP version (minimum 7.4)
2. Ensure OpenSSL extension is enabled
3. Contact your host if needed
### "Upload failed - file size exceeds limit"
**Cause**: Server upload limit too small
**Solution**:
1. Increase `upload_max_filesize` in php.ini
2. Or use FTP upload method instead
### "Fatal error after activation"
**Cause**: Plugin conflict or memory issue
**Solution**:
1. Increase WordPress memory limit in wp-config.php:
```php
define('WP_MEMORY_LIMIT', '256M');
```
2. Deactivate other plugins temporarily to identify conflicts
### White screen after activation
**Cause**: PHP error being suppressed
**Solution**:
1. Enable WordPress debug mode in wp-config.php:
```php
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
```
2. Check `/wp-content/debug.log` for error details
---
## Getting Help
If you encounter issues during installation:
- **[System Requirements](/getting-started/requirements/)** - Verify server compatibility
- **[Troubleshooting Guide](/support/troubleshooting/)** - Common issues and solutions
- **[Contact Support](https://wpsigner.com/contact/)** - Get personalized help
---
## Next Steps
Now that WPsigner is installed:
1. **[Quick Start Guide](/getting-started/quick-start/)** - Create your first document
2. **[Creating Documents](/core-features/creating-documents/)** - Learn the 4-step wizard
3. **[Digital ID Setup](/digital-identity/digital-id/)** - Configure certificates
---
# Introduction to WPsigner
> Overview of WPsigner Lite and Pro — self-hosted electronic signatures for WordPress, shared core workflows, and when to upgrade.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/getting-started/introduction/
Markdown: https://docs.wpsigner.com/md/getting-started/introduction.md
WPsigner is a self-hosted electronic-signature plugin that turns a WordPress site into a document-signing platform. Document files and records stay on your infrastructure by default. There are two editions:
| Edition | Best for | Where to get it |
|---------|----------|-----------------|
| **[WPsigner Lite](/getting-started/lite-vs-pro/)** | Free PDF signing (max 2 signers), audit trail, email OTP | WordPress.org / Plugins → Add New |
| **WPsigner Pro** | Unlimited signers, campaigns, templates, addons, integrations, full white-label, API | [wpsigner.com](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=upgrade&utm_campaign=introduction) |
Compare limits side by side: **[Lite vs Pro](/getting-started/lite-vs-pro/)**. Most guides below describe shared workflows and Pro-only features; each page shows an edition badge.
## Why WPsigner?
### Self-Hosted & Private
By default, document files and records remain on your WordPress infrastructure. Data is sent to a third party only when you configure an external service such as cloud storage, KYC, messaging, payments, or automation (Pro integrations).
### No Per-Envelope Fees
WPsigner does not charge a fee for each envelope. Hosting resources, license terms (Pro), and charges from configured third-party services still apply.
### Legal and compliance support
Electronic-signature laws recognize electronic records in many jurisdictions. WPsigner provides evidence and workflow controls that can support compliance, but enforceability depends on the document type, intent, consent, identity method, record retention, and local law.
| Framework | Region | WPsigner relevance |
|-----------|--------|--------------------|
| **ESIGN Act / UETA** | United States | Intent, consent, attribution, and retained records |
| **eIDAS** | European Union | SES-oriented workflows; AdES/QES require additional technical and provider conditions |
| **PIPEDA and provincial laws** | Canada | Electronic records plus privacy obligations |
| **Electronic Transactions Acts** | Australia | Electronic transactions subject to transaction-specific exceptions |
See [Legal Compliance](/compliance/) and consult qualified counsel for your use case.
### White-Label Ready (Pro)
**Pro** can remove WPsigner branding and replace it with your company logo, colors, and email identity. Lite includes editable email/on-screen texts but not full white-label renaming.
---
## Core Features
### Document Management
- **PDF Upload**: Lite supports PDF; Pro also supports PNG and JPG
- **4-Step Wizard**: Intuitive document creation flow
- **Field Placement**: Drag-and-drop signature fields onto any location
- **Multi-Signer**: Lite allows up to **2** invited signers; Pro allows unlimited
- **Template Library**: Reusable templates (**Pro**)
- **WordPress signers**: Search users, add yourself as signer #1, optional matching WordPress login (**Pro 3.2.0+**)
- **Signed PDF fonts**: Vietnamese and other scripts on flattened PDFs (**Pro 3.2.0+**)
- **Bulk Send**: CSV invitations from a template, with a tag per batch (**Pro**)
### Signing Workflows
- **Parallel Signing**: All signers receive emails simultaneously
- **Sequential Signing**: Signers receive emails in a specific order
- **Auto-Reminders**: Automatic email reminders for pending signatures
- **Expiration Dates**: Set deadlines for document completion
### Security & Compliance
- **Digital Certificates**: PKI support with .p12/.pfx certificates
- **Timestamping**: Local timestamp in Lite; external TSA in **Pro**
- **Audit Trail**: Complete history of every action with IP, timestamp, and device info
- **Access Codes**: Optional PIN protection for sensitive documents
- **OTP**: Email OTP in Lite; additional channels in **Pro**
- **Document Integrity**: SHA-256 hashing to detect tampering
### Mobile Experience
- **Responsive Design**: Perfect signing on phones and tablets
- **Touch Signatures**: Draw signatures with your finger
- **Pinch-to-Zoom**: Native zoom for reviewing documents
- **Progressive Loading**: Fast page-by-page rendering
---
## How It Works
**Upload PDF** → **Add Signers** → **Place Fields** → **Send for Signing** → **Signers Sign** → **Download Certified PDF**
### Step-by-Step Process
1. **Upload Your Document**
- Go to WPsigner → New Document
- Drag and drop your PDF or click to browse
- The document is securely stored on your server
2. **Add Signers**
- Enter name and email for each signer
- Choose parallel or sequential signing
- Assign colors for easy field identification
3. **Place Signature Fields**
- Drag fields from the toolbar onto the PDF
- Position signature, date, text, and checkbox fields
- Assign each field to a specific signer
4. **Send for Signing**
- Review the document summary
- Click "Send" to deliver emails to all signers
- Track progress from your dashboard
5. **Signers Complete Fields**
- Signers receive a secure link via email
- They can sign on any device (desktop, tablet, phone)
- Each signature is captured with timestamp and IP
6. **Document Completion**
- Once all signers finish, the PDF is sealed
- A certificate of completion is appended
- All parties receive the final signed document
---
## Field Types
WPsigner supports various field types for comprehensive document workflows:
| Field Type | Description | Use Case |
|------------|-------------|----------|
| **Signature** | Capture handwritten or typed signatures | Contracts, agreements |
| **Initials** | Smaller signature field for initials | Multi-page documents |
| **Date** | Current date auto-filled | Document dating |
| **Text** | Free-form text input | Names, addresses, notes |
| **Checkbox** | Yes/no selection boxes | Terms acceptance, options |
| **Dropdown** | Select from predefined options | Multiple choice fields |
---
## Integration Options
WPsigner integrates with your existing WordPress ecosystem:
### Built-in Integrations
- **WooCommerce**: Auto-send contracts after purchase
- **Fluent Forms**: Trigger signatures from form submissions
- **Elementor**: Display signature status in your designs
### Automation Platforms
- **Zapier**: 5,000+ app connections
- **Make (Integromat)**: Visual automation workflows
- **n8n**: Self-hosted automation
- **Pabbly Connect**: Budget-friendly automation
### Developer Tools
- **REST API**: Full programmatic access to all features
- **Webhooks**: Real-time event notifications
- **Action Hooks**: WordPress hooks for customization
- **Filter Hooks**: Modify behavior without code changes
---
## System Requirements
Before installing WPsigner, ensure your server meets these requirements:
| Requirement | Minimum | Recommended |
|------------|---------|-------------|
| WordPress | 5.8+ | 6.0+ |
| PHP | 7.4+ | 8.1+ |
| MySQL | 5.7+ | 8.0+ |
| Memory | 128MB | 256MB+ |
| OpenSSL | Any version | 1.1.1+ |
### Required PHP Extensions
- `openssl` - For digital certificates and PDF signing
- `gd` OR `imagick` - For signature image processing
- `mbstring` - For multi-byte string handling
- `curl` - For webhook delivery
---
## Getting Started
Ready to start signing documents? Follow these steps:
1. **[Install WPsigner](/getting-started/installation/)** - Download and activate the plugin
2. **[Quick Start Guide](/getting-started/quick-start/)** - Create your first document in 5 minutes
3. **[Configure Settings](/customization/whitelabeling/)** - Add your branding
4. **[Set Up Security](/digital-identity/digital-id/)** - Configure digital certificates
---
## Support & Resources
### Documentation
- [Creating Documents](/core-features/creating-documents/) - Detailed document creation guide
- [Signer Workflows](/core-features/signer-workflows/) - Sequential vs parallel signing
- [REST API](/api/) - Developer API reference
- [Troubleshooting](/support/troubleshooting/) - Common issues and solutions
### Community
- [Feature Requests](https://wpsigner.com/contact/) - Suggest new features
- [Bug Reports](https://wpsigner.com/contact/) - Report issues
- [Changelog](/changelog/) - See what's new in each version
> **tip**
New to electronic signatures? Start with the [Quick Start Guide](/getting-started/quick-start/) to create a test document.
---
# WPsigner Lite vs Pro
> Compare WPsigner Lite (free on WordPress.org) and WPsigner Pro — limits, features, upgrade path, and what data you keep.
edition: lite
Edition: Lite
AI note: This page is Lite-only. Do not describe campaigns, templates, addons, integrations, REST API, webhooks, client portal, team roles, external TSA, or full white-label as available.
HTML: https://docs.wpsigner.com/getting-started/lite-vs-pro/
Markdown: https://docs.wpsigner.com/md/getting-started/lite-vs-pro.md
**WPsigner Lite** is the free edition on [WordPress.org](https://wordpress.org/plugins/wpsigner/). **WPsigner Pro** is the full product sold on [wpsigner.com](https://wpsigner.com/). This page shows what each edition includes so you can choose (or upgrade) without guessing.
Upgrade to Pro
## Quick summary
| | Lite | Pro |
|---|---|---|
| Price | Free | Paid license |
| Where to get it | WordPress.org / Plugins → Add New | [Account Portal](https://app.wpsigner.com/) |
| PDF signing + audit trail | Yes | Yes |
| Max signers per document | 2 | Unlimited |
| File types | PDF only | PDF, PNG, JPG |
| OTP | Email only | Email and additional channels |
| Timestamp | Local only | Local + external TSA |
| Campaigns, templates, addons, integrations | No | Yes |
| Full white-label | No | Yes |
| Upgrade keeps your documents | — | Yes (same `wps_*` tables) |
See the full matrix below. For install steps, open [Installation](/getting-started/installation/).
---
## Feature comparison
### Documents and signing
| Capability | Lite | Pro |
|---|---|---|
| Upload and place fields | Yes (PDF) | Yes (PDF, PNG, JPG) |
| Draw / type / upload signature | Yes | Yes |
| Parallel or sequential order | Yes | Yes |
| Maximum invited signers | **2** | Unlimited |
| Document access code | Yes | Yes |
| Auto-reminders and expiration | Yes (within Lite scope) | Yes |
| Reusable document templates | No | Yes |
| Pick signers from WordPress users / Add me as signer #1 | No | Yes (3.2.0+) |
| Require WordPress login per signer | No | Yes (3.2.0+) |
| Bulk Send (CSV + tag per batch) | No | Yes |
| Campaigns (public signing links) | No | Yes |
### Security and evidence
| Capability | Lite | Pro |
|---|---|---|
| Audit trail | Yes | Yes |
| Local completion timestamp | Yes | Yes |
| External timestamp authority (TSA) | No | Yes |
| Email OTP | Yes | Yes |
| Additional OTP channels (e.g. SMS) | No | Yes |
| Digital ID / certificate settings | Yes | Yes |
| Document encryption tools | Limited / local focus | Full Pro toolkit |
### Portal, team, and automation
| Capability | Lite | Pro |
|---|---|---|
| Client portal shortcodes | No | Yes |
| Team roles and permissions matrix | No | Yes |
| Public REST API + API keys | No | Yes |
| Webhooks | No | Yes |
| Official addons (Document Builder, MainWP, Uncanny Automator, etc.) | No | Yes |
| Integrations (forms, CRM, WooCommerce, cloud, KYC, Zapier, …) | No | Yes |
### Branding and customization
| Capability | Lite | Pro |
|---|---|---|
| Editable email templates and on-screen texts | Yes | Yes |
| Optional “Powered by” credit toggle | Yes | Yes |
| Appearance hub (Brand, Signing Page, Client Portal) | No | Yes |
| Full white-label (rename product everywhere) | No | Yes |
| Languages / translations | Yes | Yes |
| Signed PDF fonts (Vietnamese and other scripts) | No | Yes (3.2.0+) |
Lite is a complete free product, not a time-limited trial. It does not hide Pro code behind a license key; Pro is a separate plugin.
---
## What you keep when you upgrade
Lite and Pro share the same data model:
- Database tables with the `wps_*` prefix (documents, signers, fields, audit logs, signatures, tags, and related rows)
- Secure file storage used by the plugin on your server
- Encryption key handling compatible with Pro
When Pro is active, Lite does not load. Your existing documents, signers, and audit history remain. You do not re-upload completed work to “migrate.”
Upgrade to Pro
---
## Which edition should you use?
**Choose Lite** if you need a few PDF signatures on your own WordPress site, at most two signers per document, and you are fine with local timestamps and email OTP.
**Choose Pro** if you need unlimited signers, Bulk Send, campaigns or templates, integrations, addons, client portal, REST API/webhooks, external TSA, or full white-label branding.
---
## FAQ
### Is Lite a trial?
No. Lite stays free with its published limits. Pro is a separate paid product.
### Can Lite and Pro run at the same time?
Do not rely on both being active together. When Pro is installed and active, Lite steps aside so only one product UI loads. Keep one edition active.
### Where do I install each edition?
- **Lite:** WordPress admin → Plugins → Add New (search WPsigner), or the wordpress.org listing when published.
- **Pro:** Download from the [Account Portal](https://app.wpsigner.com/) and install the ZIP. Details: [Installation](/getting-started/installation/).
### Will I lose documents if I buy Pro?
No. Pro reads the same tables and storage. See [What you keep when you upgrade](#what-you-keep-when-you-upgrade).
### Does this documentation cover Lite or Pro?
Most guides describe the full product (Pro) and shared workflows. Each page shows an edition badge (**Lite**, **Pro**, or **Lite + Pro**). Pro-only pages include an Upgrade button. This comparison page is the SEO hub for Lite vs Pro.
---
## Next steps
- [First Document on Lite](/getting-started/first-document-lite/) — PDF → two signers → send
- [Glossary](/glossary/) — envelope, TSA, OTP, campaign, audit trail
- [Install WPsigner](/getting-started/installation/) — Lite and Pro paths
- [Quick Start](/getting-started/quick-start/) — full product path (Pro features noted)
- [Introduction](/getting-started/introduction/) — product overview
- [Pricing / Upgrade to Pro](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=upgrade&utm_campaign=lite-vs-pro-footer)
- Product summary for AI: [wpsigner.com/llms.txt](https://wpsigner.com/llms.txt) · Docs index: [/llms.txt](/llms.txt) · Lite pack: [/md/packs/lite.md](/md/packs/lite.md)
---
# Quick Start Guide
> Create and send your first document for signature in under 5 minutes.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/getting-started/quick-start/
Markdown: https://docs.wpsigner.com/md/getting-started/quick-start.md
This guide walks you through creating and sending your first document for signature. By the end, you'll have a fully signed PDF with a complete audit trail.
> **Lite limits**
**Lite** accepts **PDF only** and a maximum of **two** invited signers, with email OTP and local timestamps. Prefer the dedicated **[First Document on Lite](/getting-started/first-document-lite/)** guide if you installed from WordPress.org. **Pro** removes those limits — see [Lite vs Pro](/getting-started/lite-vs-pro/).
## What You'll Create
In this tutorial, you'll:
- Upload a PDF document
- Add a signer
- Place signature fields
- Send the document
- View the signed result
**Time required**: ~5 minutes
---
## Step 1: Access the Document Wizard
1. Log in to your WordPress admin dashboard
2. Click **WPsigner** in the left sidebar
3. Click **New Document** (or the "+" button)
You'll see the 4-step document creation wizard.
---
## Step 2: Upload Your Document
**Supported formats**: PDF, PNG, JPG
### Option A: Drag & Drop
1. Drag your PDF file into the upload area
2. Wait for the upload to complete
### Option B: Click to Browse
1. Click the upload area
2. Select your file from your computer
3. Click **Open**
After upload, you'll see a preview of your document.
> **tip**
For best results, use PDF files. They maintain formatting across devices and support multiple pages.
**Click "Next"** to continue.
---
## Step 3: Add Signers
Now add the people who need to sign this document.
### Add Your First Signer
1. Enter the signer's **Name** (e.g., "John Smith")
2. Enter their **Email** address
3. (Optional) Enter their **Phone** number for SMS notifications
### Multiple Signers
To add more signers:
1. Click **Add Signer**
2. Fill in their details
3. Repeat for each signer
### Signing Order
Choose how signers will receive the document:
| Mode | Description | Best For |
|------|-------------|----------|
| **Parallel** | All signers receive emails at the same time | Quick signatures, co-signers |
| **Sequential** | Signers receive emails in order (1st, then 2nd, etc.) | Approval chains, contracts |
> **tip**
For contracts that need to be signed in a specific order (e.g., employee → manager → HR), use **Sequential** mode. The first person you add is Signer #1 (their signature fields).
On **Pro 3.2.0+** you can type two characters to pick a WordPress user, check **Add me as signer #1**, or require a matching WordPress login on a row. Details: [Creating Documents](/core-features/creating-documents/#wordpress-users).
**Click "Next"** to continue.
---
## Step 4: Place Signature Fields
This is where you tell WPsigner where signers should sign.
### The Field Toolbar
On the left side, you'll see available fields:
| Field | Icon | Purpose |
|-------|------|---------|
| **Signature** | ✍️ | Full signature capture |
| **Initials** | AB | Smaller initial signature |
| **Date** | 📅 | Current date (auto-filled) |
| **Text** | Aa | Free-form text input |
| **Checkbox** | ☑️ | Yes/no options |
| **Dropdown** | ▼ | Select from options |
### Placing Fields
1. **Click** on a field type in the toolbar
2. **Click** on the document where you want to place it
3. **Drag** the field to adjust its position
4. **Resize** using the corner handles
### Assigning Fields to Signers
When you have multiple signers:
1. Click on a placed field
2. Select which signer should complete it
3. Each signer has a unique color for easy identification
### Multi-Page Documents
- Use the page navigation at the bottom
- Place fields on any page
- Scroll through pages using the arrows
**Click "Next"** to continue.
---
## Step 5: Review & Send
Before sending, review your document setup:
### Review Checklist
- ✅ Document uploaded correctly
- ✅ All signers added with valid emails
- ✅ Signature fields placed in the right locations
- ✅ Fields assigned to the correct signers
### Add a Personal Message (Optional)
1. Enter a custom message for your signers
2. This appears in the signing request email
### Send the Document
1. Click **Send Document**
2. Confirm the action
3. Emails are sent immediately to signers
---
## What Happens Next
### For You (Document Owner)
1. You'll see the document in your dashboard
2. Status shows as "Sent" or "Pending"
3. You can track who has viewed/signed
### For Signers
1. They receive an email with a secure signing link
2. They click the link (no account needed)
3. They complete their assigned fields
4. They submit their signature
### When Complete
1. All parties receive a copy of the signed document
2. A Certificate of Completion is appended to the PDF
3. The document is digitally sealed
---
## Viewing Your Signed Document
After all signers complete their signatures:
1. Go to **WPsigner → Documents**
2. Find your document (status: "Completed")
3. Click to open the document
4. Click **Download** to get the signed PDF
### What's Included
The completed PDF contains:
- All original content
- Rendered signatures in place
- Certificate of Completion page with:
- Document ID and hash
- All signer details
- Timestamps and IP addresses
- QR code for verification
---
## Example Walkthrough
Let's create a simple NDA:
### Scenario
You need "Jane Doe" (jane@example.com) to sign a Non-Disclosure Agreement.
### Steps
1. **Upload**: Drag your NDA.pdf into WPsigner
2. **Signer**: Add "Jane Doe" with email jane@example.com
3. **Fields**:
- Place a **Signature** field on the signature line
- Place a **Date** field next to it
4. **Send**: Click "Send Document"
Jane receives an email, clicks the link, signs, and you both get the completed NDA automatically!
---
## Common Questions
### Do signers need an account?
No. Signers receive a secure one-time link. No login required.
### Can I edit a document after sending?
No. Once sent, documents are locked to ensure legal validity.
### What if a signer doesn't receive the email?
1. Check their spam folder
2. Use the **Resend** option in your dashboard
3. Verify the email address is correct
### How do I cancel a sent document?
1. Open the document
2. Click **Actions → Void Document**
3. All signers are notified
---
## Next Steps
Now that you've sent your first document:
- **[Signer Workflows](/core-features/signer-workflows/)** - Sequential vs parallel signing
- **[Field Types](/core-features/form-fields/)** - All available field options
- **[Email Templates](/customization/email-templates/)** - Customize signing emails
- **[Appearance](/customization/appearance/)** - Logo, signing buttons, and portal
- **[Bulk Send](/core-features/bulk-send/)** - Same template, many emails from a CSV
- **[Branding](/customization/whitelabeling/)** - Add your company logo
---
# System Requirements
> Complete server requirements and PHP extensions for WPsigner.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/getting-started/requirements/
Markdown: https://docs.wpsigner.com/md/getting-started/requirements.md
Before installing WPsigner, ensure your server meets these requirements for optimal performance and full feature support.
## Minimum Requirements
| Component | Minimum | Recommended |
|-----------|---------|-------------|
| **WordPress** | 5.8+ | 6.4+ |
| **PHP** | 7.4+ | 8.1+ |
| **MySQL** | 5.7+ | 8.0+ |
| **MariaDB** | 10.3+ | 10.6+ |
| **Memory Limit** | 128MB | 256MB+ |
| **Max Upload Size** | 10MB | 64MB+ |
| **Max Execution Time** | 30s | 120s+ |
---
## Required PHP Extensions
These extensions are essential for WPsigner to function properly:
| Extension | Purpose | Check Command |
|-----------|---------|---------------|
| **openssl** | Digital signatures, PDF sealing, certificate management | `php -m \| grep openssl` |
| **gd** OR **imagick** | Image processing, signature rendering | `php -m \| grep -E "gd\|imagick"` |
| **mbstring** | Multi-byte string handling for international characters | `php -m \| grep mbstring` |
| **curl** | Webhook delivery, external API calls | `php -m \| grep curl` |
| **json** | API responses, data storage | `php -m \| grep json` |
| **zip** | Document packaging and export | `php -m \| grep zip` |
### Optional But Recommended
| Extension | Purpose |
|-----------|---------|
| **intl** | Better date/time formatting for international users |
| **exif** | Image orientation handling for uploaded signatures |
| **fileinfo** | MIME type detection for secure file uploads |
---
## Server Configuration
### PHP Settings (php.ini)
For optimal performance with large documents, adjust these settings:
```ini
; Recommended PHP settings for WPsigner
memory_limit = 256M
upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 120
max_input_vars = 3000
```
### OpenSSL Requirements
WPsigner uses OpenSSL for:
- Digital certificate generation (self-signed)
- PDF digital signatures
- Secure webhook signatures (HMAC-SHA256)
**Minimum OpenSSL Version**: 1.0.2
**Recommended**: 1.1.1 or higher
To check your OpenSSL version:
```bash
openssl version
```
### File Permissions
WPsigner needs write access to these directories:
| Directory | Permission | Purpose |
|-----------|------------|---------|
| `wp-content/uploads/` | 755 | Document storage |
| `wp-content/wpsigner-secure/` | 750 | Signed PDFs, certificates |
---
## WordPress Configuration
### Recommended Settings
| Setting | Recommended Value | Why |
|---------|-------------------|-----|
| **Permalinks** | Post name (`/%postname%/`) | Required for signing URLs |
| **WP Cron** | Enabled | Auto-reminders, webhook delivery |
| **SSL Certificate** | Required | Secure signing experience |
### HTTPS Requirement
> **important**
WPsigner requires HTTPS for production use. All signing URLs must be served over SSL to protect signing sessions and data in transit.
---
## Hosting Compatibility
WPsigner runs on standard WordPress hosting — including small shared-hosting sites — when the requirements above are met.
For recommended providers, shared hosting tips, WAF notes, and a go-live checklist, see **[Hosting Compatibility](/getting-started/hosting-compatibility/)**.
---
## Checking Your Server
### Quick Compatibility Check
After installing WordPress, you can check your server's compatibility:
1. Go to **Tools → Site Health**
2. Click **Info** tab
3. Expand **Server** section
4. Verify PHP version, extensions, and limits
### Manual PHP Info Check
Create a temporary file `phpinfo.php` in your WordPress root:
```php
```
Visit `yourdomain.com/phpinfo.php` to view all PHP settings.
> **caution**
Delete this file immediately after checking. It exposes sensitive server information.
---
## Troubleshooting Common Issues
### "OpenSSL extension not found"
Contact your hosting provider to enable OpenSSL, or for VPS:
```bash
sudo apt-get install php-openssl
sudo systemctl restart apache2
```
### "Memory limit exhausted"
Add to `wp-config.php`:
```php
define('WP_MEMORY_LIMIT', '256M');
```
### "Upload file size too large"
For Apache, add to `.htaccess`:
```apache
php_value upload_max_filesize 64M
php_value post_max_size 64M
```
For Nginx, add to server block:
```nginx
client_max_body_size 64M;
```
---
## Next Steps
Once your server meets all requirements:
1. **[Hosting Compatibility](/getting-started/hosting-compatibility/)** - Confirm your host is a good fit
2. **[Download WPsigner](https://wpsigner.com/download/)** - Get the latest version
3. **[Installation Guide](/getting-started/installation/)** - Step-by-step setup
4. **[Quick Start](/getting-started/quick-start/)** - Create your first document
---
# System Status, Storage & Retention
> Diagnose WPsigner requirements, cron, email, PDF, database, and storage health; configure retention and understand destructive cleanup actions.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/getting-started/system-status-and-storage/
Markdown: https://docs.wpsigner.com/md/getting-started/system-status-and-storage.md
WPsigner provides two operational screens:
- **WPsigner → More → System Status** — diagnostics, health checks, and repair actions.
- **WPsigner → More → Storage & Retention** — storage usage, cloud backup status, retention, purge, and full deletion.
Both screens currently require a WordPress Administrator with `manage_options`.
## System Status
System Status checks:
- WordPress, PHP, and extension requirements
- Plugin compatibility
- Secure storage path, permissions, and size
- WP-Cron configuration and scheduled WPsigner jobs
- Email/SMTP delivery
- Timezone
- PDF engine and the active **Signed PDF fonts** pack (if installed)
- Database tables
- Webhooks and REST API
- Security-related configuration
Use **Copy Debug Info** when contacting support. Review the copied text before sharing it because environment reports can include domain, plugin, and server details.
## Scheduled jobs
WPsigner relies on WP-Cron for background work:
| Hook | Schedule | Purpose |
|------|----------|---------|
| `wps_send_automatic_reminders` | Hourly | Send due signing reminders |
| `wps_check_expirations` | Hourly | Expire documents whose due date passed |
| `wps_auto_purge_storage` | Daily when configured | Remove eligible local completed PDFs |
| `wps_ots_check_pending` | When OpenTimestamps is enabled | Check pending timestamp proofs |
| `wps_api_logs_purge` | Daily | Purge old API request logs |
### Repair missing jobs
Click **Fix Cron Jobs** in System Status. WPsigner recreates the schedules appropriate for the enabled features.
If `DISABLE_WP_CRON` is enabled, configure a real server cron to call `wp-cron.php`. Repairing the schedule does not make WordPress cron execute when the hosting environment never triggers it.
## Secure storage
System Status displays the active secure-storage directory and whether it is writable. WPsigner normally stores files below the WordPress uploads area using protected folders and secure-storage controls.
Do not make the storage folder publicly browsable. Back up both:
1. The WordPress database, which contains document, signer, field, audit, and configuration records.
2. The WPsigner file storage, which contains document files.
A file-only or database-only backup is not a complete WPsigner recovery plan.
## Retention settings
Open **Storage & Retention** to configure:
| Setting | Options |
|---------|---------|
| **Automatic purge** | On / Off |
| **Retention period** | Forever, 30, 60, 90, 180, or 365 days |
Automatic purge removes only local PDFs for **completed** documents older than the selected period and only when WPsigner has recorded a cloud backup for that document. Audit records, signatures, and document database records remain.
> **important**
Choosing a retention period does not guarantee deletion of every document file. Files without a confirmed cloud backup are skipped to prevent accidental loss.
## Storage actions
### Purge Completed PDFs
- Requires typing `DELETE`.
- Removes eligible local completed PDFs that have a cloud backup.
- Keeps document records, audit data, and cloud copies.
### Delete Drafts & Cancelled
- Requires typing `DELETE`.
- Removes draft/cancelled records and their local files.
- Use only after confirming those documents are no longer needed.
### Push to Cloud
Scans completed PDFs that lack a recorded cloud backup and uploads them through the configured provider. Check the result before enabling automatic purge.
### Delete Everything
> **danger**
**Delete Everything** is a destructive reset. It removes WPsigner's operational database records and local files. It cannot be undone from WPsigner.
The action requires:
1. An acknowledgement checkbox.
2. The exact phrase `DELETE ALL`.
3. Keeping the browser tab open while chunked file deletion finishes.
It removes documents, signers, fields, audits, templates, campaigns, payments, and related operational records. It preserves WPsigner options and license data. Remote files already stored with a cloud provider are not deleted automatically.
Create and test a full backup before using it. If the browser closes or a timeout interrupts the process, reopen the screen and run the cleanup again after verifying what remains.
## Operational checklist
### Weekly
- Review System Status for new warnings.
- Check failed emails, webhook deliveries, and cron events.
- Confirm available disk space.
### Monthly
- Test a document from upload through final PDF.
- Verify a recent database and file backup can be restored.
- Review API keys, webhook endpoints, and inactive integrations.
- Confirm cloud backup counts before purging local PDFs.
### Before an upgrade
1. Back up database and WPsigner files.
2. Record the current System Status report.
3. Update in staging when possible.
4. Test PDF generation, signing, email, cron, and integrations.
## Troubleshooting
### Cron jobs are missing
Use **Fix Cron Jobs**. If they disappear again, check object caching, cron-management plugins, `DISABLE_WP_CRON`, and the hosting control panel's scheduled task.
### Automatic purge does not remove files
Confirm automatic purge is on, the period is not **Forever**, the document is completed and old enough, and a cloud backup is recorded.
### Storage is not writable
Check the exact path shown in System Status, filesystem ownership, hosting quotas, and security rules. Avoid setting globally writable permissions.
### Emails fail
Use the System Status email test, verify SMTP credentials and DNS, and inspect the mail provider's logs.
### Wordfence blocks WPsigner actions
Use the compatibility information in System Status to allowlist the reported WPsigner AJAX actions, then retest. Do not disable the firewall globally.
### Delete Everything stops partway
Keep the tab open and retry the action. Check PHP execution limits and server logs. Cloud backups remain at the provider until removed there.
## Related guides
- [Hosting Compatibility](/getting-started/hosting-compatibility/)
- [Security & Compliance](/core-features/security-compliance/)
- [Audit Trails](/digital-identity/audit-trails/)
- [Troubleshooting](/support/troubleshooting/)
---
# WPsigner Glossary
> Definitions of envelope, TSA, OTP, campaign, audit trail, and other WPsigner terms — with Lite vs Pro notes for SEO and AI assistants.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/glossary/
Markdown: https://docs.wpsigner.com/md/glossary.md
This glossary defines WPsigner terms used in the docs, admin UI, and AI exports. Each entry notes whether it applies to **Lite**, **Pro**, or **both**. Compare editions: [Lite vs Pro](/getting-started/lite-vs-pro/). Product pricing: [wpsigner.com/pricing](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=glossary&utm_campaign=lite-vs-pro).
For AI assistants: prefer these definitions over generic e-signature jargon. Do not treat Pro-only terms as available in Lite.
---
## Editions and licensing
### Lite
Free edition published for WordPress.org. PDF only, maximum two invited signers, email OTP, local timestamp, audit trail. Not a time-limited trial. See [Lite vs Pro](/getting-started/lite-vs-pro/) and [First Document on Lite](/getting-started/first-document-lite/).
### Pro
Paid edition from the [Account Portal](https://app.wpsigner.com/). Removes Lite limits and adds campaigns, templates, addons, integrations, client portal, REST API, webhooks, external TSA, and full white-label. Pricing: [wpsigner.com/pricing](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=glossary&utm_campaign=pro).
### License
Pro activation key from the Account Portal. Lite does not use a paid license key. License screens and renewals are Pro.
### Upgrade
Installing Pro beside an existing Lite site. Same `wps_*` tables and secure storage; documents stay. Do not keep both plugins active — Pro takes over.
### Account Portal
Customer site at [app.wpsigner.com](https://app.wpsigner.com/) for Pro downloads, licenses, and official addons.
---
## Documents and signing
### Envelope
SaaS vendors often charge per “envelope” (one sending package). **WPsigner does not meter envelopes.** The working unit is a **document** (or a **campaign** submission in Pro). Hosting and Pro license terms still apply.
### Document
A file prepared for signature: upload, signers, fields, send, complete. Lite accepts **PDF only**. Pro also accepts PNG and JPG. Guide: [Creating Documents](/core-features/creating-documents/).
### Signer
A person invited by name and email to sign. Lite: maximum **two** invited signers per document. Pro: unlimited.
### Sequential signing
Signers are notified in order. The next person is invited after the previous one finishes. Available in Lite and Pro. Guide: [Signer Workflows](/core-features/signer-workflows/).
### Parallel signing
All invited signers receive the request at the same time. Available in Lite and Pro.
### Field
A placed control on the PDF (signature, initials, date, text, checkbox, and others). Each field is assigned to a signer slot. Signer #1 is the first row on Add Signers. Reference: [Form Fields](/core-features/form-fields/).
### Add me as signer #1
**Pro 3.2.0+.** Checkbox that fills the first signer row with the current WordPress account. It does not turn on the login gate. Guide: [Creating Documents](/core-features/creating-documents/#wordpress-users).
### Require WordPress login
**Pro 3.2.0+.** Per-signer option. The visitor must be logged in with the WordPress account whose email matches that signer. Off by default. The email must already be a WordPress user. Not used on campaign or Bulk Send CSV invitations. Guide: [Security & Compliance](/core-features/security-compliance/#wordpress-login-per-signer).
### Mapping name
Optional machine name on a field for Zapier, forms, or the REST API. Empty mapping falls back to a slug of the field name. API/forms mapping is **Pro**.
### Template
A reusable document layout you can send again. **Pro.** Lite has no document templates.
### Bulk Send
**Pro.** Invite many people from a CSV using one template. You name the send; that name becomes a tag on every document so you can filter the batch in Documents. Not available in Lite. Guide: [Bulk Send](/core-features/bulk-send/).
### Appearance
**Pro.** Admin page with three tabs: Brand, Signing Page, and Client Portal. Open **WPsigner → Appearance**. Guide: [Appearance](/customization/appearance/).
### Signed PDF fonts
**Pro 3.2.0+.** Optional Noto packs under **WPsigner → Languages → Signed PDF fonts**. They keep Vietnamese and other scripts on flattened signed PDFs. They do not translate the WPsigner screens. Guide: [Languages](/customization/languages/#signed-pdf-fonts).
### Reminder
Automatic email follow-up for pending signers. Available in the shared document flow; treat advanced automation as Pro when it depends on integrations.
### Expiration
A deadline after which the document can no longer be signed. Available in the document wizard (Lite and Pro).
### Document status
Typical states: **Draft**, **Sent**, **Viewed**, **Completed**, **Declined**, **Expired**.
### Certificate of Completion
Summary page or PDF section that records who signed and related evidence. Paired with the [audit trail](#audit-trail).
---
## Security and evidence
### Audit trail
Chronological evidence log (sent, opened, signed, IP, user agent, timestamps). **Lite and Pro.** Guide: [Audit Trails](/digital-identity/audit-trails/).
### OTP (one-time password)
A short code the signer must enter before signing. **Lite: email only.** Pro can add other channels (for example SMS via Twilio). Guide: [Security & Compliance](/core-features/security-compliance/).
### Access code
Optional PIN or shared secret required to open the signing page. Lite and Pro.
### TSA (Timestamp Authority)
A trusted third party that issues an **RFC 3161** token over a document hash — independent time evidence. **External TSA is Pro.** Lite stores a **local** completion timestamp on your server. Guide: [Timestamping](/digital-identity/timestamping/).
### Local timestamp
Time recorded by your WordPress server when the document completes. This is the Lite timestamp mode. It is not an external TSA token.
### Digital ID
A `.p12` / `.pfx` certificate used to apply a PKI signature to the completed PDF. Settings exist in Lite and Pro. Guide: [Digital ID](/digital-identity/digital-id/).
### PKI
Public Key Infrastructure — certificate + private key used to cryptographically sign the PDF.
### SHA-256 hash
Fingerprint of the file used to detect tampering. Used in audit and integrity checks.
### Encryption
Protecting stored files and secrets at rest (for example AES-256). Guide: [Document Encryption](/digital-identity/encryption/).
### KYC
Know Your Customer identity checks (ID document, selfie, liveness) before signing. **Pro** (for example [Didit](/integrations/didit/)).
### Retention
How long signed files and records are kept, plus cleanup tools. See [System Status & Storage](/getting-started/system-status-and-storage/).
### Secure storage
Plugin-managed file location on the WordPress server (not the public uploads folder for signed PDFs). Shared by Lite and Pro so upgrades keep files.
---
## Pro workflows and automation
### Campaign
**Pro.** A public URL that creates a new signed copy for each visitor (waivers, event forms). Not individual email invitations. Different from [Bulk Send](/core-features/bulk-send/) (CSV + email). Guide: [Campaigns](/core-features/campaigns/).
### Client portal
**Pro.** Front-end dashboards via shortcodes for your team and external signers. Guide: [Client Portal](/core-features/client-portal/).
### Shortcode
A WordPress tag such as `[insigner_client_portal]` or `[insigner_admin_portal]`. Portal shortcodes are **Pro**.
### Team roles
**Pro.** Sender, Viewer, Manager, Admin (plus No Access) on top of WordPress users. Guide: [Team Roles](/core-features/team-roles/).
### Webhook
**Pro.** HTTP callback when a document event happens (signed, completed, and others). Guide: [Webhooks](/api/webhooks/).
### REST API
**Pro.** Per-site API at `https://your-site.com/wp-json/insigner/v1/`. There is no global API on wpsigner.com. Guide: [REST API](/api/).
### API key
**Pro.** Credential created in the site admin for HMAC-authenticated API calls.
### Addon
**Pro.** Official extra plugin (Document Builder, Smart Signing Forms, MainWP, Uncanny Automator, ApproveMe Importer). Guide: [Addons](/addons/overview/).
### Uncanny Automator
**Pro addon.** WordPress automation plugin. **WPsigner for Uncanny Automator** registers a native WPsigner integration (triggers, actions, tokens) on the same site — not a Zapier-style cloud connection. Guide: [WPsigner for Uncanny Automator](/addons/uncanny-automator/).
### Integration
**Pro.** Connection to forms, CRM, storage, messaging, payments, or automation. Overview: [Integrations](/integrations/).
### White-label
**Pro.** Replace the product name, logo, and branding throughout the UI. Lite can edit email/on-screen texts and optionally show a credit line. Guide: [Whitelabeling](/customization/whitelabeling/).
---
## Legal and compliance (plain language)
### ESIGN / UETA
United States frameworks that recognize electronic records and signatures when consent, intent, attribution, and retention are met. See [Legal Compliance](/compliance/).
### eIDAS
EU regulation for electronic identification and trust services. WPsigner supports SES-oriented workflows; AdES/QES need extra technical and provider conditions.
### SES / AdES / QES
Simple, Advanced, and Qualified electronic signatures under eIDAS. Higher levels need specific certificates and qualified trust service providers — not implied by installing Lite or Pro.
### Evidence
The combination of signed PDF, audit trail, hashes, optional OTP/KYC, and optional TSA that can support a compliance argument. Enforceability always depends on the transaction and local law.
---
## Quick Lite vs Pro cheat sheet
| Term | Lite | Pro |
|------|------|-----|
| Envelope fees | None (self-hosted document) | None (self-hosted document) |
| Audit trail | Yes | Yes |
| OTP | Email | Email + extra channels |
| TSA | Local timestamp only | Local + external TSA |
| Campaign | No | Yes |
| Templates, addons, integrations, API, portal | No | Yes |
Need the full matrix? [Lite vs Pro](/getting-started/lite-vs-pro/). Need prices? [wpsigner.com/pricing](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=glossary&utm_campaign=cheat-sheet). Product LLM summary: [wpsigner.com/llms.txt](https://wpsigner.com/llms.txt). Docs LLM index: [docs.wpsigner.com/llms.txt](https://docs.wpsigner.com/llms.txt).
---
# WPsigner Documentation
> Official documentation for WPsigner Lite and Pro — self-hosted e-signatures for WordPress, feature guides, and upgrade path.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/
Markdown: https://docs.wpsigner.com/md/index.md
# WPsigner Documentation
## Explore the Documentation
See what is free on WordPress.org and what requires Pro — plus how upgrades keep your documents. [Compare →](/getting-started/lite-vs-pro/)
Install Lite or Pro and create your first document in minutes. [Start here →](/getting-started/introduction/)
Documents, campaigns, portal, team roles, signer security, workflows, and fields. [Learn more →](/core-features/)
Digital IDs, timestamping, encryption, and audit trails for legal compliance. [Configure →](/digital-identity/)
Full REST API with webhooks for developers (Pro). [API Reference →](/api/)
White label branding and email templates. [Customize →](/customization/)
30+ integrations: Forms, CRM, Cloud Storage, Messaging, Stripe, Automation, and more (Pro). [View all →](/integrations/)
Document Builder, Smart Signing Forms, MainWP, Uncanny Automator, import tools, and official extensions (Pro). [Addons guide →](/addons/overview/)
---
## Full Documentation Sitemap
### Getting Started
| Page | Description |
|------|-------------|
| [Overview](/getting-started/) | Getting started with WPsigner |
| [Introduction](/getting-started/introduction/) | Product overview and Lite vs Pro |
| [Lite vs Pro](/getting-started/lite-vs-pro/) | Feature matrix, limits, and upgrade path |
| [System Requirements](/getting-started/requirements/) | Server and WordPress requirements |
| [Hosting Compatibility](/getting-started/hosting-compatibility/) | Recommended hosts and shared hosting guidance |
| [Installation](/getting-started/installation/) | Step-by-step installation guide |
| [First Document (Lite)](/getting-started/first-document-lite/) | WordPress.org path: PDF → two signers → send |
| [Quick Start Guide](/getting-started/quick-start/) | Create and send your first document |
| [System Status, Storage & Retention](/getting-started/system-status-and-storage/) | Diagnose cron, email, PDF, database, storage, backup, and retention |
### Core Features
| Page | Description |
|------|-------------|
| [Overview](/core-features/) | All core features at a glance |
| [Creating Documents](/core-features/creating-documents/) | Wizard, WordPress user picker, signer #1, and optional WordPress login |
| [Campaigns (Public Links)](/core-features/campaigns/) | Reusable public signing links |
| [Client Portal](/core-features/client-portal/) | Admin and signer dashboards on your site |
| [Team Roles & Permissions](/core-features/team-roles/) | Sender, Viewer, Manager, and Admin access matrix |
| [Security & Compliance](/core-features/security-compliance/) | OTP, KYC, access codes, WordPress login, evidence, certificates, and timestamps |
| [Signer Workflows](/core-features/signer-workflows/) | Signer order, parallel vs sequential, per-signer WordPress login |
| [Form Fields](/core-features/form-fields/) | All field types: signature, text, date, checkbox, etc. |
### Addons
| Page | Description |
|------|-------------|
| [Overview](/addons/overview/) | Install and manage official WPsigner addons |
| [Smart Signing Forms](/addons/smart-signing-forms/) | Drag-and-drop signing forms with payments and OTP |
| [Document Builder](/addons/document-builder/) | Write documents and generate signing-ready PDFs |
| [ApproveMe Importer](/addons/approveme-importer/) | Import completed documents from ApproveMe / WP E-Signature |
| [WPSigner for MainWP](/addons/mainwp/) | Agency contracts from the MainWP Dashboard |
| [WPsigner for Uncanny Automator](/addons/uncanny-automator/) | Native Automator recipes for signing events and document actions |
| [Account Portal](/addons/account-portal/) | Licenses, downloads, and addons at app.wpsigner.com |
### Digital Identity & Security
| Page | Description |
|------|-------------|
| [Overview](/digital-identity/) | Security and digital identity features |
| [Digital ID (.p12)](/digital-identity/digital-id/) | PKI certificate configuration |
| [Timestamping (TSA)](/digital-identity/timestamping/) | RFC 3161 timestamp authority setup |
| [Audit Trails](/digital-identity/audit-trails/) | Immutable audit logging and certificates |
| [Document Encryption](/digital-identity/encryption/) | AES-256 encryption at rest |
### Customization
| Page | Description |
|------|-------------|
| [Overview](/customization/) | Customization options |
| [White Label Branding](/customization/whitelabeling/) | Logo, colors, and brand identity |
| [Email Templates](/customization/email-templates/) | Customize notification emails |
| [Languages & Translations](/customization/languages/) | Language packs and Signed PDF fonts (Vietnamese and other scripts) |
### Integrations
| Page | Description |
|------|-------------|
| [All Integrations](/integrations/) | Complete integrations overview |
**Community**
| Page | Description |
|------|-------------|
| [Fluent Community](/integrations/fluent-community/) | Member profile and header access to signing documents |
**Payments**
| Page | Description |
|------|-------------|
| [Stripe](/integrations/stripe/) | Stripe payments for documents and Smart Forms |
**Identity Verification (KYC)**
| Page | Description |
|------|-------------|
| [Didit.me](/integrations/didit/) | KYC identity verification for signers |
**Forms**
| Page | Description |
|------|-------------|
| [Fluent Forms](/integrations/fluent-forms/) | Form-to-signature automation |
| [WPForms](/integrations/wpforms/) | WPForms integration |
| [Gravity Forms](/integrations/gravity-forms/) | Gravity Forms integration |
| [Elementor Forms](/integrations/elementor-forms/) | Elementor Forms integration |
| [Contact Form 7](/integrations/contact-form-7/) | Inline signing, OTP, merge tags, and template feeds |
**Messaging**
| Page | Description |
|------|-------------|
| [WhatsApp Business](/integrations/whatsapp/) | WhatsApp signing notifications |
| [Telegram](/integrations/telegram/) | Telegram bot notifications |
| [Slack](/integrations/slack/) | Slack workspace notifications |
| [Twilio SMS](/integrations/twilio/) | SMS notifications via Twilio |
| [Microsoft Teams](/integrations/teams/) | Teams channel notifications |
**CRM**
| Page | Description |
|------|-------------|
| [HubSpot](/integrations/hubspot/) | HubSpot CRM sync |
| [Pipedrive](/integrations/pipedrive/) | Pipedrive deal integration |
| [FluentCRM](/integrations/fluentcrm/) | FluentCRM contact sync |
**Cloud Storage**
| Page | Description |
|------|-------------|
| [Google Drive](/integrations/google-drive/) | Auto-upload to Google Drive |
| [Dropbox](/integrations/dropbox/) | Auto-upload to Dropbox |
| [OneDrive](/integrations/onedrive/) | Auto-upload to OneDrive |
| [Amazon S3](/integrations/amazon-s3/) | Store documents in S3 |
| [Wasabi](/integrations/wasabi/) | Store documents in Wasabi |
| [Cloudflare R2](/integrations/cloudflare-r2/) | Store documents in R2 |
**Automation**
| Page | Description |
|------|-------------|
| [n8n & Make Guide](/integrations/automation/) | Getting started with automation |
| [Zapier](/integrations/zapier/) | Zapier zap integration |
| [Make](/integrations/make/) | Make scenario integration |
| [n8n](/integrations/n8n/) | n8n workflow integration |
| [Pabbly Connect](/integrations/pabbly/) | Pabbly Connect integration |
| [WPsigner for Uncanny Automator](/addons/uncanny-automator/) | Native WordPress recipes (official addon) |
**E-Commerce & LMS**
| Page | Description |
|------|-------------|
| [WooCommerce](/integrations/woocommerce/) | Post-purchase signing agreements |
| [LearnDash](/integrations/learndash/) | Course enrollment agreements |
### REST API
| Page | Description |
|------|-------------|
| [API Overview](/api/) | Authentication and getting started |
| [Documents API](/api/documents/) | Create, read, update, delete documents |
| [Templates API](/api/templates/) | Create documents from reusable templates and mapped variables |
| [Signers API](/api/signers/) | Manage document signers |
| [Fields API](/api/fields/) | Manage signature fields |
| [Statistics API](/api/statistics/) | Retrieve signing statistics |
| [Webhooks](/api/webhooks/) | Real-time event notifications |
| [Code Examples](/api/examples/) | PHP, JavaScript, and Python examples |
### Support
| Page | Description |
|------|-------------|
| [Overview](/support/) | Support resources |
| [Use Docs with AI](/support/use-with-ai/) | Copy Markdown pages and topic packs into ChatGPT, Claude, Cursor |
| [Troubleshooting](/support/troubleshooting/) | Common issues and solutions |
| [FAQ](/support/faq/) | Frequently asked questions |
| [Report a Security Issue](/support/security/) | Vulnerability disclosure program |
### Reference
| Page | Description |
|------|-------------|
| [Glossary](/glossary/) | Envelope, TSA, OTP, campaign, audit trail, and Lite vs Pro terms |
| [Legal Compliance](/compliance/) | ESIGN, UETA, eIDAS, and industry regulations |
| [Changelog](/changelog/) | Version history and release notes |
---
# Support
> Find solutions to common issues, answers to frequently asked questions, and ways to get help with WPsigner.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/support/
Markdown: https://docs.wpsigner.com/md/support.md
Having trouble with WPsigner? This section covers the most common issues and questions. If you can't find what you're looking for here, reach out to the support team directly.
---
## Support Resources
| Resource | Description |
|----------|-------------|
| [Use Docs with AI](/support/use-with-ai/) | Copy per-page Markdown or topic packs into ChatGPT, Claude, Cursor, or any assistant |
| [Troubleshooting](/support/troubleshooting/) | Step-by-step solutions for installation issues, email delivery problems, signing errors, and integration failures |
| [FAQ](/support/faq/) | Answers about Lite vs Pro, licensing, MainWP, Uncanny Automator, and security |
| [Lite vs Pro](/getting-started/lite-vs-pro/) | Feature matrix and upgrade path without losing documents |
| [Glossary](/glossary/) | Envelope, TSA, OTP, campaign, audit trail, and other terms |
| [Report a Security Issue](/support/security/) | Responsible disclosure for vulnerabilities in WPsigner |
---
## Common Issues
### Installation & Activation
- Plugin won't activate → Check PHP version (7.4+ required) and missing extensions
- Setup wizard errors → Verify `openssl` and `gd`/`imagick` extensions are enabled
- Database errors → Ensure MySQL 5.7+ and `CREATE TABLE` permissions
### Email Delivery
- Signers not receiving emails → Check SMTP configuration or install a mail plugin (WP Mail SMTP, FluentSMTP)
- Emails going to spam → Configure SPF, DKIM, and DMARC records for your domain
### Signing Page
- PDF not loading → Check server memory limit (256MB+ recommended)
- Signature not saving → Verify JavaScript errors in the browser console
- Mobile display issues → Clear browser cache and ensure responsive mode is active
- Vietnamese or accented names missing on the signed PDF → **WPsigner → Languages → Signed PDF fonts** → install **Accented Latin**
- Signer asked to log in to WordPress → that row has **Require WordPress login** on; they must use the matching account email
For detailed solutions, see the [Troubleshooting Guide](/support/troubleshooting/).
---
## Contact Support
If the documentation doesn't resolve your issue:
- **Support Portal**: [wpsigner.com/contact](https://wpsigner.com/contact/)
- **Security issues**: [Report a vulnerability](/support/security/) (Patchstack VDP)
- **Response Time**: Typically within 24 hours on business days
When contacting support, include:
1. Your WPsigner version (found in **WPsigner → Settings → General**)
2. Your WordPress and PHP versions
3. A description of the issue and steps to reproduce it
4. Any error messages from `wp-content/debug.log`
> **tip**
Enable debug logging before contacting support — it helps resolve issues faster:
```php
// In wp-config.php
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
```
Then check `wp-content/debug.log` for entries starting with `[WPsigner]`.
---
# Frequently Asked Questions
> Answers to common questions about WPsigner electronic signatures, legal compliance, security, and features.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/support/faq/
Markdown: https://docs.wpsigner.com/md/support/faq.md
Find answers to the most common questions about WPsigner electronic signatures.
## Lite vs Pro
### What is the difference between Lite and Pro?
**Lite** is free (WordPress.org): PDF only, max two signers, email OTP, local timestamp, audit trail. **Pro** adds unlimited signers, campaigns, templates, addons, integrations, client portal, REST API/webhooks, external TSA, and full white-label. Full matrix: [Lite vs Pro](/getting-started/lite-vs-pro/).
### Can I upgrade from Lite to Pro without losing documents?
Yes. Pro uses the same `wps_*` database tables and secure storage. When Pro is active, Lite does not load. Your documents and audit logs remain.
### Is Lite a time-limited trial?
No. Lite is a complete free edition with published limits. Pro is a separate paid plugin.
### Where do I buy or upgrade to Pro?
Use [wpsigner.com/pricing](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=upgrade&utm_campaign=faq) or the **Upgrade to Pro** button on Pro-only docs pages.
### I installed Lite from WordPress.org. Where do I start?
Follow **[First Document on Lite](/getting-started/first-document-lite/)** (PDF → up to two signers → send). For the full product path, see [Quick Start](/getting-started/quick-start/). Definitions of OTP, TSA, campaign, and audit trail: [Glossary](/glossary/).
## Legal & Compliance
### Are electronic signatures legally valid?
Electronic signatures are legally recognized in many countries, but validity for a particular transaction depends on consent, intent, identity evidence, retention, document type, and local exceptions:
| Region | Law | Status |
|--------|-----|--------|
| **United States** | ESIGN Act, UETA | ✅ Legal since 2000 |
| **European Union** | eIDAS Regulation | ✅ Legal since 2016 |
| **United Kingdom** | UK eIDAS/ECA 2000 | ✅ Legal |
| **Canada** | PIPEDA, Provincial laws | ✅ Legal |
| **Australia** | Electronic Transactions Act | ✅ Legal |
Electronic records generally cannot be rejected solely because they are electronic, but this does not make every workflow or document automatically enforceable.
### What documents can I sign electronically?
**Most documents** can be signed electronically:
| ✅ **Can Sign Electronically** | ❌ **May Require Wet Signature** |
|-------------------------------|----------------------------------|
| Contracts | Wills and testaments |
| Employment agreements | Court documents |
| NDAs | Some real estate deeds |
| Service agreements | Notarized documents |
| Purchase orders | Powers of attorney (varies) |
| HR documents | Some government forms |
| Client proposals | |
Check your local requirements for specific document types.
### Is WPsigner HIPAA compliant?
WPsigner can be used in a HIPAA-compliant manner when:
1. **You host on HIPAA-compliant infrastructure** (WPsigner is self-hosted)
2. **You configure appropriate security settings:**
- Enable OTP verification
- Use Digital ID signing
- Configure audit trails
3. **Your hosting provider has a BAA** (Business Associate Agreement)
4. **You implement proper access controls**
WPsigner provides the tools; you ensure compliance through proper configuration.
### Does WPsigner meet eIDAS requirements?
WPsigner provides controls that can contribute to different eIDAS-oriented workflows:
| Level | WPsigner role | Additional requirements |
|-------|---------------|-------------------------|
| **Simple Electronic Signature (SES)** | Captures a signature and audit evidence | Transaction-specific consent and retention |
| **Advanced Electronic Signature (AdES)** | OTP, KYC, audit, certificate, and timestamp controls can contribute | Must satisfy all eIDAS AdES criteria, not just enable a preset |
| **Qualified Electronic Signature (QES)** | Can retain related evidence | Requires a qualified certificate, qualified signature-creation device/process, and QTSP |
The Security & Compliance score is guidance only and does not certify a workflow as AdES or QES.
---
## Security & Privacy
### Where is my data stored?
**On your own WordPress server.** WPsigner is completely self-hosted.
| Data Type | Storage Location |
|-----------|-----------------|
| Documents | `/wp-content/uploads/wpsigner/` |
| Signatures | Your WordPress database |
| User data | Your WordPress database |
| Audit logs | Your WordPress database |
WPsigner does **not** send data to external servers (except TSA timestamps if enabled).
### Is my data encrypted?
| Layer | Encryption |
|-------|------------|
| **In transit** | HTTPS (SSL/TLS) - you configure |
| **At rest** | Server-level - you configure |
| **Signed PDFs** | Digitally signed, tamper-evident |
You control encryption through your server and WordPress configuration.
### Can WPsigner access my documents?
**No.** WPsigner is a self-hosted plugin. The developers have no access to:
- Your documents
- Your signatures
- Your user data
- Your server
Everything stays on your infrastructure.
### How are signatures protected?
Signatures are protected through:
1. **Unique signing links** - Cryptographically secure tokens
2. **Link expiration** - Configurable expiry
3. **Optional PIN protection** - Extra access layer
4. **Optional OTP verification** - Email-based MFA
5. **Audit trail** - Complete activity logging
6. **Digital signature** - Cryptographic integrity
### What happens to documents after signing?
| Stage | What Happens |
|-------|--------------|
| Signing complete | PDF locked with digital signature |
| Audit trail appended | Certificate of Completion added |
| Notifications sent | All parties receive copy |
| Original stored | Remains on your server |
Documents remain on your server indefinitely until you delete them.
---
## Features & Functionality
### What file formats are supported?
| Format | Upload | Output |
|--------|--------|--------|
| **PDF** | ✅ Yes | ✅ Yes |
| **PNG** | ✅ Yes | ✅ Converted to PDF |
| **JPG/JPEG** | ✅ Yes | ✅ Converted to PDF |
| **Word (.docx)** | ❌ No | ❌ No |
| **Excel** | ❌ No | ❌ No |
Upload PDFs for best results. Images are converted to PDF automatically.
### How many signers can sign a document?
There's **no hard limit** on the number of signers. Practical limits depend on:
- Document layout (space for signatures)
- Workflow complexity
- Performance (server resources)
Most common use cases: 1-10 signers per document.
### Can I have multiple signature fields per signer?
**Yes.** Each signer can have multiple fields:
- Multiple signature fields
- Initials on each page
- Date fields
- Text fields
- Any combination of field types
### What's the difference between parallel and sequential signing?
| Parallel | Sequential |
|----------|------------|
| All signers receive invite simultaneously | Signers receive invite one at a time |
| Any order of completion | Must complete in specified order |
| Faster for independent signers | Required for approval chains |
| All can sign at once | Next signer waits for previous |
### Can signers decline to sign?
**Yes**, if you enable declining:
1. Signer clicks "Decline" button
2. Optional reason prompt appears
3. Document owner is notified immediately
4. Document status changes to "Declined"
You can disable declining in Settings if not desired.
### Can I customize the signing page?
**Yes.** Open **WPsigner → Appearance** ([Appearance guide](/customization/appearance/)):
- **Brand** — company logo, name, and primary color
- **Signing Page** — button color, size, corners, style, and light/dark theme
- **Client Portal** — portal look if you use the front-end dashboards
Full white-label renaming is in [Whitelabeling](/customization/whitelabeling/). Button labels (Finish, Decline) stay in Custom Texts.
### How do I send the same template to many people?
Open **Documents → Bulk Send**. Download the sample CSV, add name and email, choose a template, **name the send** (that name becomes a tag), and start. Guide: [Bulk Send](/core-features/bulk-send/). For a public link instead of a list, use [Campaigns](/core-features/campaigns/).
### How do I keep Vietnamese (or other accented) text on the signed PDF?
Install a **Signed PDF font**, not a language pack. Go to **WPsigner → Languages → Signed PDF fonts**, install **Accented Latin** for Vietnamese, then click **Use for signed PDFs**. That does not translate the admin screens. Guide: [Languages](/customization/languages/#signed-pdf-fonts).
### Can I pick signers from WordPress users?
**Yes (Pro 3.2.0+).** On Add Signers or Use Template, type at least two characters in the name or email field and choose the user. Check **Add me as signer #1** to fill the first row with your account. Guide: [Creating Documents](/core-features/creating-documents/#wordpress-users).
### Who is Signer #1 for signature fields?
The first person you add (the top row). The second person is Signer #2, and so on. Drag rows to change the order. **Add me as signer #1** only fills that first slot. Guide: [Signer order](/core-features/signer-workflows/#signer-order).
### Can I require a WordPress login before someone signs?
**Yes, per signer (Pro 3.2.0+).** Check **Require WordPress login with this email**. The email must already be a WordPress user. The signing link is not enough — they must be logged in with that same email. Leave it off for guests. It does not apply to campaigns or Bulk Send CSV rows. Guide: [Security & Compliance](/core-features/security-compliance/#wordpress-login-per-signer).
---
## Technical Questions
### What are the system requirements?
| Requirement | Minimum |
|-------------|---------|
| WordPress | 5.0+ |
| PHP | 7.4+ |
| Memory | 128MB (256MB recommended) |
| Extensions | OpenSSL, GD or Imagick, mbstring |
| SSL | Required for signing pages |
See [Requirements](/getting-started/requirements/) for details. For recommended hosts and shared hosting tips, see [Hosting Compatibility](/getting-started/hosting-compatibility/).
### Does WPsigner work on small / shared hosting sites?
**Yes.** WPsigner is tested on small WordPress sites and runs well for typical signing workloads when the [system requirements](/getting-started/requirements/) are met. See [Hosting Compatibility](/getting-started/hosting-compatibility/) for limits, checklists, and when to upgrade.
### Does WPsigner work with multisite?
**Yes**, WPsigner works with WordPress multisite:
- Network activate for all sites
- Per-site activation supported
- Separate settings per site
### Does WPsigner slow down my website?
**Minimal impact.** WPsigner:
- Only loads on WPsigner admin pages
- Signing pages are standalone
- No scripts on frontend pages
- Optimized database queries
### Can I use WPsigner on localhost?
**Yes**, for testing. However:
- Emails may not send (need SMTP)
- SSL recommended but optional locally
- TSA timestamps require internet access
- Some features need public URLs
### What happens if I deactivate the plugin?
| Action | Data Preserved |
|--------|----------------|
| Deactivate | ✅ Yes, all data kept |
| Reactivate | ✅ Returns to previous state |
| Delete plugin | ⚠️ Database tables remain (by design) |
Data is never automatically deleted for safety.
---
## Signing Experience
### How do signers sign?
Signers have multiple options:
| Method | Description |
|--------|-------------|
| **Draw** | Draw signature with mouse/finger/stylus |
| **Type** | Type name, select font style |
| **Upload** | Upload image of signature |
All methods are legally equivalent.
### Do signers need an account?
**No.** Signers:
- Click the unique link in their email
- Review the document
- Sign using any method
- Done!
No registration, no login, no account needed.
### Can signers access documents on mobile?
**Yes.** The signing experience is fully responsive:
- Works on smartphones
- Tablet-optimized
- Touch-friendly signature pad
- Pinch-to-zoom document viewing
### What if a signer loses their link?
Options:
1. **Check email** - Search for subject line
2. **Check spam** - May be filtered
3. **Request resend** - Contact document owner
4. **Owner resends** - From document actions menu
### Can signers download the signed document?
**Yes.** After completion:
- All signers receive email with signed document
- Download link in completion email
- Link remains active
---
## Documents & Storage
### Is there a document size limit?
| Limit Type | Default | Adjustable |
|------------|---------|------------|
| File size | Server limit | Yes, in php.ini |
| Page count | No limit | N/A |
| Field count | No limit | N/A |
Large documents may process slower.
### How long are documents stored?
**Until you delete them.** WPsigner doesn't auto-delete.
Recommendations:
- Keep completed documents per your retention policy
- Archive to external storage as needed
- Delete when no longer required
### Can I export/backup my documents?
**Yes**, multiple methods:
| Method | How |
|--------|-----|
| Download individual | From document view |
| Bulk download | Select multiple, download |
| Server backup | Backup `/wp-content/uploads/wpsigner/` |
| Database export | Standard WordPress backup includes data |
### Can I integrate with cloud storage?
Manual upload to:
- Google Drive
- Dropbox
- OneDrive
- Any cloud storage
Use [Webhooks](/api/webhooks/) for automation.
---
## Campaigns (Public Links)
### What's the difference between documents and campaigns?
| Documents | Campaigns |
|-----------|-----------|
| Send to specific people | Anyone with link can sign |
| Known recipients | Anonymous or known |
| One-time use links | Reusable link |
| Track individual signers | Track by campaign |
### Who can access campaign links?
Anyone with the link. Use campaigns for:
- Website forms
- QR codes
- Social media
- Mass distribution
Every new access creates a unique signing session.
### Can I limit campaign responses?
**Yes**, you can configure:
- Maximum submissions
- Expiration date
- Active/inactive status
---
## Integrations
### Can I integrate with my CRM?
**Yes**, through:
- [REST API](/api/) - Full programmatic access
- [Webhooks](/api/webhooks/) - Event notifications
- Zapier (via webhooks) - No-code automation
### Does WPsigner work with WooCommerce?
Manual integration via:
- Webhooks for order events
- API for document creation
- Custom development
### Can I trigger signatures from forms?
**Yes**, integrate with:
- Gravity Forms (via API/webhooks)
- WPForms (via API/webhooks)
- Contact Form 7 (via hooks)
- Any form plugin (via REST API)
---
## Pricing & Licensing
### How is WPsigner licensed?
WPsigner uses a **per-site license**:
- One license = one WordPress installation
- Development/staging sites typically free
- Volume discounts available
### Are there document limits?
License determines:
- Features available
- Support level
- Update access
No per-document fees or usage limits.
### What's included in support?
Support includes:
- Email assistance
- Bug fixes
- Compatibility updates
- Documentation access
---
## Getting Started
### How do I get started?
1. [Install the plugin](/getting-started/installation/)
2. Configure [settings](/customization/whitelabeling/)
3. Create your [first document](/getting-started/quick-start/)
4. Send for signature!
### Is there a demo?
Visit [wpsigner.com](https://wpsigner.com) for:
- Live demos
- Video tutorials
- Feature previews
### Where can I get help?
| Resource | For |
|----------|-----|
| [Documentation](https://docs.wpsigner.com) | Self-help guides |
| [Troubleshooting](/support/troubleshooting/) | Common issues |
| [Contact Support](https://wpsigner.com/contact) | Direct assistance |
---
## MainWP Addon
### Does WPSigner integrate with MainWP?
**Yes.** The official **[WPSigner for MainWP](/addons/mainwp/)** addon runs on your MainWP **Dashboard** (alongside WPSigner). You link contracts to MainWP Clients and Sites, then create, send, and remind from MainWP. WPSigner is **not** installed on child sites for this workflow.
### Can I enable OTP or KYC from MainWP?
When WPSigner Security is set to **Choose per document**, Create and Quick create can turn OTP/KYC on for that contract. MainWP does **not** change global WPSigner security options (addon **1.5.8+**). See [MainWP Security](/addons/mainwp-security/).
### Why are signing links hidden in MainWP?
Only WordPress admins (`manage_options`) or WPSigner users with full manage rights see raw signing URLs. Other team members can still manage contracts and view PDFs when allowed. Details: [MainWP Security](/addons/mainwp-security/).
### Where is MainWP troubleshooting?
See the dedicated guide: [MainWP Troubleshooting](/addons/mainwp-troubleshooting/).
---
## Uncanny Automator Addon
### Does WPsigner work with Uncanny Automator?
**Yes.** The official **[WPsigner for Uncanny Automator](/addons/uncanny-automator/)** addon registers a WPsigner integration inside Automator on the same WordPress site. There is no remote Automator app connection.
### Do I need Automator Pro?
No for triggers and actions. **Uncanny Automator Pro** is required only for WPsigner conditions and signer token loops.
### Are signing links stored in Automator logs?
If a recipe uses the Signing URL token, Automator may store it. Turn the token off under **Automator → WPsigner**. Details: [Settings](/addons/uncanny-automator-settings/) and [Security](/addons/uncanny-automator-security/).
### Where is Uncanny Automator troubleshooting?
See [Uncanny Automator Troubleshooting](/addons/uncanny-automator-troubleshooting/).
---
## More Questions?
Can't find your answer?
- Check [Troubleshooting](/support/troubleshooting/)
- Contact [support](https://wpsigner.com/contact/)
- Ask in the community
---
# Report a Security Issue
> How to responsibly report security vulnerabilities in the WPsigner WordPress plugin.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/support/security/
Markdown: https://docs.wpsigner.com/md/support/security.md
If you believe you have found a security issue in WPsigner, please report it through our managed disclosure program. Do not post it publicly until we have had a chance to fix it.
WPsigner works with [Patchstack](https://patchstack.com/for-plugins/) to review reports, coordinate patches, and protect customers.
## Report a vulnerability
[Open the reporting form in a new tab →](https://patchstack.com/database/vdp/wpsigner)
## What to include
- WPsigner version, plus WordPress and PHP versions
- Steps to reproduce the issue
- What an attacker could do if the issue were exploited
- Screenshots or a proof-of-concept, if you have one
## What happens next
1. Patchstack validates the report.
2. If it is confirmed, we receive the details and prepare a fix.
3. We release an update and coordinate disclosure when appropriate.
## Scope
This program covers the **WPsigner plugin** only. General product support is on the [support overview](/support/) page or [wpsigner.com/contact](https://wpsigner.com/contact/).
For the same policy on our main site, see [wpsigner.com/security](https://wpsigner.com/security/).
---
# Troubleshooting
> Solutions to common issues with WPsigner installation, configuration, signing, and document processing.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/support/troubleshooting/
Markdown: https://docs.wpsigner.com/md/support/troubleshooting.md
This guide covers the most common issues you might encounter with WPsigner and provides step-by-step solutions.
## Quick Diagnostics
Before troubleshooting specific issues, check the System Status:
1. Go to **WPsigner → More → System Status**
2. Review all health checks
3. Address any items marked with ⚠️ or ❌
---
## Installation Issues
### "Plugin could not be activated"
**Symptoms:**
- Error message on activation
- White screen after activation
- Plugin immediately deactivates
**Causes & Solutions:**
| Cause | Solution |
|-------|----------|
| **PHP version too low** | Upgrade to PHP 7.4 or higher |
| **Missing OpenSSL** | Enable OpenSSL extension |
| **Memory limit** | Increase to 128MB minimum |
| **Plugin conflict** | Deactivate other plugins to identify conflict |
**How to check PHP version:**
```bash
php -v
```
**How to enable debug mode:**
Add to `wp-config.php`:
```php
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
```
Then check `/wp-content/debug.log` for specific errors.
### "Upload failed - file size exceeds limit"
**Symptoms:**
- Cannot upload plugin zip file
- Error during upload process
**Solutions:**
1. **Increase PHP upload limits** in `php.ini`:
```ini
upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 300
```
2. **Or use FTP upload method:**
- Extract the zip file locally
- Upload via FTP to `/wp-content/plugins/`
- Activate in WordPress admin
### Fatal error on activation
**Full error message check:**
1. Enable debug mode (see above)
2. Try activating again
3. Check `/wp-content/debug.log`
4. Search for the specific error
**Common fatal errors:**
| Error | Solution |
|-------|----------|
| `Cannot redeclare function` | Plugin conflict - identify and deactivate |
| `Class not found` | Missing dependency - reinstall plugin |
| `Memory exhausted` | Increase `WP_MEMORY_LIMIT` |
---
## Form integrations (Fluent Forms / WPForms)
### OTP says verified, but submit fails
**Symptoms:**
- OTP modal shows **Identity verified**
- Form then shows “Please verify your identity…” (or similar)
- No signed document is created
**Solution:**
1. Update **WPsigner to 3.1.1+**
2. Hard-refresh the form page (Ctrl+F5 / Cmd+Shift+R)
3. Submit again and complete OTP once
This mainly affects **content signing** forms with many fields + OTP. See [Fluent Forms](/integrations/fluent-forms/) and [WPForms](/integrations/wpforms/).
### Cannot save a content-signing feed
**Symptoms:**
- Feed Name and Form are filled
- Save shows “Please fill in Feed Name and Form”
- You are not using a PDF template (inline Signing field)
**Solution:** Update to **3.1.1+**. Content-signing feeds do not require a template — only Feed Name and Form.
### Wrong signer name on the document
Map a real **Name** / **Names** field. Do not map a field labeled only **Username**.
### Field labels missing in feed mapping
In the PDF editor, **double-click** each field and set a **Field name**. Details: [Form fields](/core-features/form-fields/#field-name-mapping-name-and-placeholder).
---
## Email Issues
### Emails not sending
This is the most common issue. Emails may not send for several reasons.
**Step 1: Verify email configuration**
1. Go to **WPsigner → Settings → Email Settings**
2. Verify "From Name" and "From Email" are set
3. Ensure email address is valid
**Step 2: Send a test email**
1. Go to **WPsigner → More → Email Templates**
2. Click **Send Test**
3. Enter your email address
4. Check if received
**Step 3: Configure SMTP**
WordPress's default `wp_mail()` function often fails. Install an SMTP plugin:
| Plugin | Recommendation |
|--------|----------------|
| **WP Mail SMTP** | Most popular, easy setup |
| **FluentSMTP** | Free, full-featured |
| **Post SMTP** | Good logging |
**Step 4: Check SMTP logs**
Most SMTP plugins have logging. Check for:
- Connection errors
- Authentication failures
- Rejected recipients
### Emails going to spam
**Causes:**
- No SPF/DKIM records
- Using @gmail.com as sender
- Poor sender reputation
- Missing authentication
**Solutions:**
1. **Use your own domain** for "From Email" (not @gmail.com)
2. **Set up email authentication:**
- Add SPF record to DNS
- Configure DKIM signing
- Set up DMARC policy
3. **Check content:**
- Avoid spam trigger words
- Don't use all caps
- Include clear unsubscribe option (if applicable)
### Signer claims they didn't receive email
**Checklist:**
1. ✅ Verify email address is correct (check for typos)
2. ✅ Check spam/junk folder
3. ✅ Check "Promotions" tab (Gmail)
4. ✅ Ask if email was blocked by corporate filter
5. ✅ Use **Resend** option in document actions
6. ✅ Review SMTP logs for delivery status
---
## Document Issues
### Vietnamese or accented characters missing on the signed PDF
**Symptoms:**
- Names look fine on the signing page but the downloaded PDF shows boxes, `?`, or missing marks
- Certificate of Completion drops ă, ơ, ư, đ, or similar
**Solution:**
1. Go to **WPsigner → Languages**
2. Open **Signed PDF fonts**
3. Install **Accented Latin** (Vietnamese and other Latin languages with accents)
4. Click **Use for signed PDFs**
5. Send a **new** test document — already flattened PDFs are not rewritten
For Chinese, Japanese, Korean, Arabic, Hebrew, or Thai, install that pack instead. Guide: [Signed PDF fonts](/customization/languages/#signed-pdf-fonts).
### Require WordPress login will not stay checked
The signer email is not a WordPress user, or the document has an active public campaign. Create the user first, pause the campaign, or leave the option off. Guide: [WordPress login](/core-features/security-compliance/#wordpress-login-per-signer).
### PDF generation failed
**Symptoms:**
- Error when finalizing document
- Certificate of Completion not appending
- Blank or corrupted PDF output
**Required extensions:**
| Extension | Purpose | Check Command |
|-----------|---------|---------------|
| **GD** | Image processing | `php -m | grep gd` |
| **Imagick** | Advanced image/PDF | `php -m | grep imagick` |
| **mbstring** | String handling | `php -m | grep mbstring` |
**Solutions:**
1. **Enable GD extension:**
```bash
# Ubuntu/Debian
sudo apt-get install php-gd
sudo service apache2 restart
```
2. **Check file permissions:**
```bash
# The uploads directory must be writable
chmod 755 wp-content/uploads
chmod 755 wp-content/uploads/wpsigner
```
3. **Increase memory limit:**
Add to `wp-config.php`:
```php
define('WP_MEMORY_LIMIT', '256M');
```
### Document upload fails
**Common causes:**
| Issue | Solution |
|-------|----------|
| File too large | Increase `upload_max_filesize` |
| Wrong format | Use PDF, PNG, or JPG only |
| Timeout | Increase `max_execution_time` |
| Permissions | Check `/wp-content/uploads/` is writable |
**Check upload limits:**
1. Go to **WPsigner → More → System Status**
2. Review "Upload Size" value
3. Increase if needed in `php.ini`
### Document appears blank or corrupted
**Possible causes:**
- PDF was created with unsupported features
- PDF is password-protected
- File was corrupted during upload
**Solutions:**
1. Try re-uploading the document
2. Use a simpler PDF (avoid complex layers/fonts)
3. Convert to PDF/A format
4. Remove password protection before uploading
---
## Signing Issues
### Signing page not loading
**Symptoms:**
- White screen when signer clicks link
- 404 error on signing page
- Redirect loop
**Solutions:**
1. **Flush permalinks:**
- Go to **Settings → Permalinks**
- Click **Save Changes** (without changing anything)
2. **Check permalink structure:**
- WPsigner requires "pretty" permalinks
- Select any option except "Plain"
3. **Check for conflicts:**
- Disable caching plugins temporarily
- Try a default theme
- Deactivate security plugins for testing
### Signature pad not working
**Symptoms:**
- Cannot draw on signature pad
- Signature not appearing
- Pad is unresponsive
**Causes & Solutions:**
| Cause | Solution |
|-------|----------|
| JavaScript error | Check browser console for errors |
| Cache | Clear browser cache, disable caching plugin |
| Plugin conflict | Test in incognito mode |
| Touch issues | Update browser, try different device |
**Browser compatibility:**
- Chrome 80+ ✅
- Firefox 75+ ✅
- Safari 13+ ✅
- Edge 80+ ✅
- Internet Explorer ❌ (not supported)
### "Access denied" or "Invalid link"
**Causes:**
- Link has expired
- Document was voided
- Link was already used (for single-use links)
- Wrong link/typo
**Solutions:**
1. Check document status (expired? voided?)
2. Use **Resend** to generate fresh email
3. Verify the complete URL was clicked
---
## Digital Signature Issues
### "Certificate not found" error
**Symptoms:**
- Error when signing document
- Digital signature not applying
- Adobe shows "Signature is invalid"
**Solutions:**
1. **Configure Digital ID:**
- Go to **WPsigner → More → Digital ID**
- Generate or upload a certificate
- Verify it shows as "Active"
2. **Certificate expired:**
- Check certificate validity dates
- Generate new or upload renewed certificate
### Adobe shows "Unknown Signer"
**This is expected for self-signed certificates.**
For self-signed certificates, recipients must manually trust:
1. Click on the signature in Adobe
2. Click "Validate Signature"
3. Choose "Trust this certificate"
**For globally trusted signatures:**
Purchase a certificate from an AATL member (DigiCert, GlobalSign, etc.)
### Timestamp not appearing
**Causes:**
- TSA not enabled
- TSA server unreachable
- Firewall blocking requests
**Solutions:**
1. **Enable TSA:**
- Go to **WPsigner → Settings → Legal & Privacy**
- Check "Enable certified timestamp (TSA)"
- Save settings
2. **Test TSA connection:**
```bash
curl -I https://freetsa.org/tsr
```
3. **Try different TSA:**
- FreeTSA.org
- DigiCert timestamp server
- Sectigo timestamp server
---
## Performance Issues
### Plugin is slow
**Optimization steps:**
1. **Enable caching** (but configure WPsigner exclusions)
2. **Optimize database:**
- Delete old/completed documents you no longer need
- Use a database optimization plugin
3. **Upgrade hosting:**
- Move from shared to VPS
- Ensure adequate PHP memory
4. **CDN for static assets:**
- Won't help with signing pages
- Does help general WordPress performance
### Signing page loads slowly
**Causes:**
- Large PDF files
- Slow server
- Multiple large images in document
**Solutions:**
1. Optimize PDF size before uploading
2. Use compression for images
3. Upgrade hosting resources
4. Move to geographically closer hosting for your signers
---
## API Issues
### API returns 401 Unauthorized
**Causes:**
- Invalid API key
- Invalid API secret
- Key revoked
- Missing headers
**Checklist:**
1. Verify API key is active (not revoked)
2. Check both key AND secret are correct
3. Ensure headers are set correctly:
```
X-WPS-API-KEY: your_key_here
X-WPS-API-SECRET: your_secret_here
```
### API returns 403 Forbidden
**Causes:**
- Key has read-only permissions for write endpoint
- User doesn't have required WordPress capabilities
**Solutions:**
1. Check key permissions (read vs read_write)
2. Create new key with appropriate permissions
### Rate limit exceeded
**Default limits:**
- 60 requests per minute per key
**Solutions:**
1. Implement request throttling in your code
2. Use bulk endpoints where available
3. Cache responses to reduce calls
---
## WordPress Conflicts
### Conflict with caching plugins
**Symptoms:**
- Signing page shows cached content
- Changes not appearing
- Session issues
**Solution - Add exclusions:**
| Caching Plugin | Exclusion Pattern |
|----------------|-------------------|
| WP Rocket | Add `/sign/*` to never cache URLs |
| W3 Total Cache | Add to page cache exceptions |
| LiteSpeed | Add to Do Not Cache URIs |
| WP Super Cache | Add to rejected pages |
### Conflict with security plugins
**Common conflicts:**
- Wordfence blocking signing requests
- iThemes Security blocking API
- Sucuri WAF filtering uploads
**Solutions:**
1. Whitelist WPsigner paths (`/sign/*`, `/wp-json/wpsigner/*`)
2. Add WPsigner to trusted plugins
3. Review security logs for blocks
### Theme compatibility issues
**Symptoms:**
- Signing page has theme elements
- Broken layout on signing page
- Missing styles
**Solutions:**
1. WPsigner signing pages should be standalone
2. If theme is interfering, check for forced templates
3. Report to support with theme name
---
## Database Issues
### Missing database tables
**Symptoms:**
- "Table doesn't exist" errors
- Plugin functions not working
- Data not saving
**Solution:**
1. Deactivate and reactivate plugin (triggers table creation)
2. If that fails, manually run table creation:
- Access your database via phpMyAdmin
- Check if `wp_wps_*` tables exist
- If missing, try reinstalling plugin
### Data migration issues
**When upgrading:**
1. Always backup before upgrading
2. Check that database updates run successfully
3. Review changelog for migration notes
---
## Getting More Help
### Information to gather before contacting support
Collect this information for faster resolution:
| Information | How to Get It |
|-------------|---------------|
| WordPress version | Dashboard → At a Glance |
| PHP version | System Status page |
| WPsigner version | Plugins page |
| Error messages | Debug log, browser console |
| Steps to reproduce | Write down exact steps |
| Screenshots | Capture error screens |
### Enable debug mode
For detailed error information:
```php
// Add to wp-config.php (before "That's all, stop editing!")
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
```
Errors are logged to `/wp-content/debug.log`
### Contact support
If you've tried the troubleshooting steps:
1. Visit [wpsigner.com/contact](https://wpsigner.com/contact/)
2. Include all gathered information
3. Attach debug logs and screenshots
4. Describe expected vs actual behavior
---
## Next Steps
- [System Requirements](/getting-started/requirements/) - Verify compatibility
- [Installation](/getting-started/installation/) - Reinstallation steps
- [FAQ](/support/faq/) - Common questions
- [MainWP Troubleshooting](/addons/mainwp-troubleshooting/) - Dashboard / Clients / Sites contract issues
- [Uncanny Automator Troubleshooting](/addons/uncanny-automator-troubleshooting/) - Recipes, tokens, prefill, and messaging
---
# Use Documentation with AI
> Copy WPsigner documentation into ChatGPT, Claude, Cursor, or any AI assistant using per-page Markdown, topic packs, and the full corpus.
edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/support/use-with-ai/
Markdown: https://docs.wpsigner.com/md/support/use-with-ai.md
Every WPsigner docs page has a matching **Markdown** twin built for AI assistants. Use it when Ask AI is unavailable, when you work in Cursor/ChatGPT/Claude, or when you want a portable offline reference.
## Fastest path
1. Open any documentation page.
2. Click **Copy for AI** under the title.
3. Paste into your assistant with a prompt like:
```text
You are helping me configure and use WPsigner, a self-hosted electronic-signature plugin for WordPress.
Use ONLY the documentation I paste as your source of truth.
If something is not covered, say so clearly.
Prefer exact admin menu paths, shortcodes, endpoints, and settings names from the docs.
```
You can also click **View Markdown** to open the `.md` file in the browser and copy it manually.
---
## What we publish for AI
| Resource | URL | Best for |
|----------|-----|----------|
| **Per-page Markdown** | `/md/{slug}.md` | One feature or integration |
| **Lite pack** | [`/md/packs/lite.md`](/md/packs/lite.md) | Lite-safe pages only (`edition: both` + Lite hubs) |
| **Topic packs** | [`/md/README.md`](/md/README.md) (packs listed there) | Setup, security, API, integrations, addons |
| **Complete pack** | [`/md/packs/complete.md`](/md/packs/complete.md) | Full docs in one file |
| **Markdown index** | [`/md/README.md`](/md/README.md) | Catalog of every page + pack |
| **LLM sitemap** | [`/llms.txt`](/llms.txt) | Crawlers and agent discovery |
| **Full corpus text** | [`/llms-full.txt`](/llms-full.txt) | Large-context models |
HTML and Markdown are generated from the **same** source files. If a page exists in the docs, it has a Markdown twin. Every `/md/{slug}.md` file starts with `edition: lite`, `edition: pro`, or `edition: both` so assistants do not invent Pro features for Lite users.
---
## Recommended packs
| Pack | Use when |
|------|----------|
| [Lite](/md/packs/lite.md) | WordPress.org / Lite questions — excludes Pro-only pages |
| [Setup](/md/packs/setup.md) | Installing, hosting, first document, system status |
| [Security](/md/packs/security.md) | Roles, OTP/KYC, Digital ID, TSA, audit, storage |
| [Core features](/md/packs/core-features.md) | Documents, campaigns, portal, workflows, fields |
| [API](/md/packs/api.md) | REST endpoints, auth, webhooks, examples |
| [Integrations](/md/packs/integrations.md) | Forms, Fluent Community, CRM, storage, automation |
| [Addons](/md/packs/addons.md) | Document Builder, Smart Forms, MainWP, Uncanny Automator, importers |
| [Customization](/md/packs/customization.md) | Branding, emails, languages |
| [Support](/md/packs/support.md) | Troubleshooting, FAQ, security disclosure |
| [Complete](/md/packs/complete.md) | Everything (large — use only if the model allows) |
> **tip**
Start with the smallest pack that covers your question. Large packs can overflow model context windows and reduce answer quality.
---
## Example URLs
| HTML page | Markdown twin |
|-----------|---------------|
| [/getting-started/installation/](/getting-started/installation/) | [/md/getting-started/installation.md](/md/getting-started/installation.md) |
| [/core-features/team-roles/](/core-features/team-roles/) | [/md/core-features/team-roles.md](/md/core-features/team-roles.md) |
| [/integrations/fluent-community/](/integrations/fluent-community/) | [/md/integrations/fluent-community.md](/md/integrations/fluent-community.md) |
| [/api/documents/](/api/documents/) | [/md/api/documents.md](/md/api/documents.md) |
| [/addons/document-builder/](/addons/document-builder/) | [/md/addons/document-builder.md](/md/addons/document-builder.md) |
| [/addons/uncanny-automator/](/addons/uncanny-automator/) | [/md/addons/uncanny-automator.md](/md/addons/uncanny-automator.md) |
| [/glossary/](/glossary/) | [/md/glossary.md](/md/glossary.md) |
| [/getting-started/lite-vs-pro/](/getting-started/lite-vs-pro/) | [/md/getting-started/lite-vs-pro.md](/md/getting-started/lite-vs-pro.md) |
Machine-readable map: [`/md/manifest.json`](/md/manifest.json)
---
## Prompt recipes
### Configure a feature
```text
I am setting up WPsigner on my WordPress site.
Using only the Markdown below, give me a numbered checklist with exact admin paths and settings.
Ask me for any missing site-specific details (domain, SMTP, plugins already installed).
```
### Debug an error
```text
WPsigner shows this error:
Using only the documentation below, list the most likely causes and the exact checks to run.
Do not invent menu names or endpoints that are not in the docs.
```
### Build an integration
```text
I need to connect WPsigner to .
Using only the documentation below, outline prerequisites, configuration steps, webhooks/events, and test plan.
```
---
## Completeness guarantees
On every production build we verify:
1. Every docs source file is exported to `/md/` and the Ask AI corpus.
2. The **complete** pack includes every page (no omissions).
3. Named packs only reference slugs that exist.
4. `llms.txt` and `llms-full.txt` are regenerated from the same source set.
If a Markdown twin is missing for a page, treat it as a docs build bug and report it.
---
## Related resources
- [Troubleshooting](/support/troubleshooting/)
- [FAQ](/support/faq/)
- [Glossary](/glossary/)
- [Lite vs Pro](/getting-started/lite-vs-pro/)
- [REST API Overview](/api/)
- Docs LLM index: [docs.wpsigner.com/llms.txt](https://docs.wpsigner.com/llms.txt)
- Product LLM summary + pricing: [wpsigner.com/llms.txt](https://wpsigner.com/llms.txt) · [Pricing](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=ai&utm_campaign=use-with-ai)