Native e-signature component for MokoSuite CRM #197

New Issue

2026-06-06T17:14:17Z

jmiller commented

2026-06-06 17:14:17 +00:00

Summary

Build a Joomla-native e-signature system for MokoWaaS CRM, based on the feature set of MokoDoliSign (Dolibarr module ID 185050). This is a self-contained signature solution — no third-party e-signature service dependency.

Parent issue: #192

Features (from MokoDoliSign blueprint)

Signature Request Workflow

Full lifecycle: Draft → Pending → InProgress → Completed / Declined / Expired / Cancelled
Multi-signer support with independent secure tokens (no Joomla login required for signers)
Configurable expiry with automated cron-based expiration
Batch operations: send to multiple signers simultaneously

Document Management

WYSIWYG editor for inline agreement creation
PDF, DOC, DOCX file uploads
Auto-generate PDF from description text (TCPDF or Joomla PDF library)
Secure document storage under Joomla media directory

Signature Capture

HTML5 Canvas with responsive drawing
Touch-friendly (mobile, tablet, stylus, finger)
Real-time signature preview
Multiple types: draw, upload, text-based

Identity Verification (Configurable per request)

Selfie capture via device camera
Government ID photo capture
GPS geolocation (latitude, longitude, accuracy)
IP address and user agent tracking

Audit Trail

Complete event log: CREATED, SENT, VIEWED, SIGNED, DECLINED, EXPIRED, CANCELLED, REMINDED
Public verification page (no auth required)
Timestamped with IP, user agent, geolocation

Email Integration

Automated signing link emails with secure tokens
Completion, decline, expiry, reminder notifications
Decline reason capture

Self-Service Portal

Signer enters email → sees all pending requests
No Joomla login required — token-based access

Database Tables

`#__mokowaas_crm_esign_requests`

id, ref (auto: SIG-000001), title, description
document_path, status (draft/pending/inprogress/completed/declined/expired/cancelled)
require_selfie, require_id, require_otp
date_creation, date_sent, date_expiry, date_signature
created_by, contact_id (FK to Joomla contact)

`#__mokowaas_crm_esign_signers`

id, request_id (FK), role, email, firstname, lastname
token (128-char unique), status (pending/viewed/signed/declined)
signature_data (base64 PNG), signature_type
selfie_path, id_path, ip_address, user_agent
geo_lat, geo_lon, geo_country, geo_city
date_sent, date_viewed, date_signed

`#__mokowaas_crm_esign_events`

id, request_id (FK), signer_id (FK, nullable)
code (CREATED/SENT/VIEWED/SIGNED/etc.), label, description
ip, user_agent, created

Implementation

New plugin or extend plg_system_mokowaas_crm
Public signing pages (no auth): /component/mokowaas/?view=sign&token=xxx
Public verification: /component/mokowaas/?view=verify&id=xxx
REST API endpoints for CRUD operations
Scheduled tasks: expire, remind, purge (via plg_task_mokowaas_esign)

Compliance

eIDAS (EU), ESIGN Act (US) compliant audit trail
GDPR: explicit/implicit consent modes
Complete chain of custody: who, when, where, how

## Summary Build a Joomla-native e-signature system for MokoWaaS CRM, based on the feature set of MokoDoliSign (Dolibarr module ID 185050). This is a self-contained signature solution — no third-party e-signature service dependency. **Parent issue:** #192 ## Features (from MokoDoliSign blueprint) ### Signature Request Workflow - Full lifecycle: Draft → Pending → InProgress → Completed / Declined / Expired / Cancelled - Multi-signer support with independent secure tokens (no Joomla login required for signers) - Configurable expiry with automated cron-based expiration - Batch operations: send to multiple signers simultaneously ### Document Management - WYSIWYG editor for inline agreement creation - PDF, DOC, DOCX file uploads - Auto-generate PDF from description text (TCPDF or Joomla PDF library) - Secure document storage under Joomla media directory ### Signature Capture - HTML5 Canvas with responsive drawing - Touch-friendly (mobile, tablet, stylus, finger) - Real-time signature preview - Multiple types: draw, upload, text-based ### Identity Verification (Configurable per request) - Selfie capture via device camera - Government ID photo capture - GPS geolocation (latitude, longitude, accuracy) - IP address and user agent tracking ### Audit Trail - Complete event log: CREATED, SENT, VIEWED, SIGNED, DECLINED, EXPIRED, CANCELLED, REMINDED - Public verification page (no auth required) - Timestamped with IP, user agent, geolocation ### Email Integration - Automated signing link emails with secure tokens - Completion, decline, expiry, reminder notifications - Decline reason capture ### Self-Service Portal - Signer enters email → sees all pending requests - No Joomla login required — token-based access ## Database Tables ### `#__mokowaas_crm_esign_requests` - `id`, `ref` (auto: SIG-000001), `title`, `description` - `document_path`, `status` (draft/pending/inprogress/completed/declined/expired/cancelled) - `require_selfie`, `require_id`, `require_otp` - `date_creation`, `date_sent`, `date_expiry`, `date_signature` - `created_by`, `contact_id` (FK to Joomla contact) ### `#__mokowaas_crm_esign_signers` - `id`, `request_id` (FK), `role`, `email`, `firstname`, `lastname` - `token` (128-char unique), `status` (pending/viewed/signed/declined) - `signature_data` (base64 PNG), `signature_type` - `selfie_path`, `id_path`, `ip_address`, `user_agent` - `geo_lat`, `geo_lon`, `geo_country`, `geo_city` - `date_sent`, `date_viewed`, `date_signed` ### `#__mokowaas_crm_esign_events` - `id`, `request_id` (FK), `signer_id` (FK, nullable) - `code` (CREATED/SENT/VIEWED/SIGNED/etc.), `label`, `description` - `ip`, `user_agent`, `created` ## Implementation - New plugin or extend `plg_system_mokowaas_crm` - Public signing pages (no auth): `/component/mokowaas/?view=sign&token=xxx` - Public verification: `/component/mokowaas/?view=verify&id=xxx` - REST API endpoints for CRUD operations - Scheduled tasks: expire, remind, purge (via `plg_task_mokowaas_esign`) ## Compliance - eIDAS (EU), ESIGN Act (US) compliant audit trail - GDPR: explicit/implicit consent modes - Complete chain of custody: who, when, where, how

jmiller referenced this issue

2026-06-06 17:15:12 +00:00

Expand MokoWaaS+ERP into full ERP offering — Joomla-native CMS + ERP platform #192

jmiller commented

2026-06-06 17:59:34 +00:00

DocuSign-Competitive Feature Parity

To compete with DocuSign, the e-signature system needs these features beyond what's already planned:

Document Preparation & Field Placement

Drag-and-drop field placement on PDF pages (signature, initials, date, text, checkbox, dropdown)
Template library — reusable document templates with pre-placed fields
Bulk send — send same template to many recipients at once
Multiple documents per envelope — group related docs in one signing session
Initials required per page (configurable per request)
Custom form fields — text input, checkbox, radio, dropdown that signers fill in

Signing Experience

Sequential or parallel signing — enforce signing order or allow simultaneous
In-person signing mode — hand device to signer, they sign in front of you
Mobile-optimized signing interface (responsive, touch-friendly)
Signer comments/questions — signers can ask questions without declining
Delegated signing — signer can delegate to someone else
Custom branding — tenant logo, colors, custom email templates on signing pages

Identity Verification (tiered, configurable)

Email verification (default — click link)
SMS/OTP verification (already planned: smart/always/never)
Selfie + ID photo (already in schema — encrypted at rest)
Knowledge-based authentication (future: security questions)
GPS geolocation capture (already in schema)

Lifecycle Management

Void — cancel a sent request, notify all signers
Correct and resend — fix a mistake without creating new request
Auto-reminders — configurable intervals (1 day, 3 days, 7 days)
Expiry warnings — email X days before expiry
Download signed PDF with signatures embedded on the document
Certificate of Completion — separate PDF with full audit trail

PDF Generation

Merge signatures onto PDF — embed signature images at placed coordinates
Flatten PDF — produce final non-editable signed document
Certificate page appended to signed document (who, when, where, IP, geolocation)
QR code on certificate linking to public verification page

Payment at Signing

Collect payment during signing — Stripe/PayPal integration at checkout step
Links to ERP invoicing — auto-generate invoice on signature completion

Reporting & Analytics

Completion rates (% of requests fully signed)
Average time to sign
Signer activity dashboard
Declined/expired trends

API & Embedding

Full REST API for programmatic request creation (already built)
Embeddable signing — iframe/JS widget for embedding in external sites
Webhook notifications on status changes (signed, declined, expired)

New Database Tables Needed

#__mokowaas_erp_esign_templates — Reusable document templates

id, title, description, document_path, fields (JSON), 
require_selfie, require_id, require_otp,
created_by, created, modified

#__mokowaas_erp_esign_fields — Placed fields on document pages

id, request_id, signer_id, page, type (signature/initials/date/text/checkbox/dropdown),
x, y, width, height, required, label, options (JSON for dropdown),
value, completed

#__mokowaas_erp_esign_comments — Signer questions/comments

id, request_id, signer_id, body, created

Competitive Positioning vs DocuSign

Feature	DocuSign	MokoWaaS+ERP
Pricing	$10-65/user/month	Included in ERP license
Self-hosted	No (cloud only)	Yes — full data ownership
ERP integration	Via Zapier/API	Native (same database)
Custom branding	Enterprise plan only	All tiers
ID verification	Add-on cost	Built-in
Payment collection	Via integration	Native Stripe/PayPal
API access	Developer plan	All tiers
Data sovereignty	US/EU cloud regions	Your server, your data

## DocuSign-Competitive Feature Parity To compete with DocuSign, the e-signature system needs these features beyond what's already planned: ### Document Preparation & Field Placement - [ ] **Drag-and-drop field placement** on PDF pages (signature, initials, date, text, checkbox, dropdown) - [ ] **Template library** — reusable document templates with pre-placed fields - [ ] **Bulk send** — send same template to many recipients at once - [ ] **Multiple documents per envelope** — group related docs in one signing session - [ ] **Initials required per page** (configurable per request) - [ ] **Custom form fields** — text input, checkbox, radio, dropdown that signers fill in ### Signing Experience - [ ] **Sequential or parallel signing** — enforce signing order or allow simultaneous - [ ] **In-person signing mode** — hand device to signer, they sign in front of you - [ ] **Mobile-optimized** signing interface (responsive, touch-friendly) - [ ] **Signer comments/questions** — signers can ask questions without declining - [ ] **Delegated signing** — signer can delegate to someone else - [ ] **Custom branding** — tenant logo, colors, custom email templates on signing pages ### Identity Verification (tiered, configurable) - [ ] **Email verification** (default — click link) - [ ] **SMS/OTP verification** (already planned: smart/always/never) - [ ] **Selfie + ID photo** (already in schema — encrypted at rest) - [ ] **Knowledge-based authentication** (future: security questions) - [ ] **GPS geolocation capture** (already in schema) ### Lifecycle Management - [ ] **Void** — cancel a sent request, notify all signers - [ ] **Correct and resend** — fix a mistake without creating new request - [ ] **Auto-reminders** — configurable intervals (1 day, 3 days, 7 days) - [ ] **Expiry warnings** — email X days before expiry - [ ] **Download signed PDF** with signatures embedded on the document - [ ] **Certificate of Completion** — separate PDF with full audit trail ### PDF Generation - [ ] **Merge signatures onto PDF** — embed signature images at placed coordinates - [ ] **Flatten PDF** — produce final non-editable signed document - [ ] **Certificate page** appended to signed document (who, when, where, IP, geolocation) - [ ] **QR code** on certificate linking to public verification page ### Payment at Signing - [ ] **Collect payment during signing** — Stripe/PayPal integration at checkout step - [ ] Links to ERP invoicing — auto-generate invoice on signature completion ### Reporting & Analytics - [ ] Completion rates (% of requests fully signed) - [ ] Average time to sign - [ ] Signer activity dashboard - [ ] Declined/expired trends ### API & Embedding - [ ] Full REST API for programmatic request creation (already built) - [ ] **Embeddable signing** — iframe/JS widget for embedding in external sites - [ ] Webhook notifications on status changes (signed, declined, expired) ### New Database Tables Needed **`#__mokowaas_erp_esign_templates`** — Reusable document templates ``` id, title, description, document_path, fields (JSON), require_selfie, require_id, require_otp, created_by, created, modified ``` **`#__mokowaas_erp_esign_fields`** — Placed fields on document pages ``` id, request_id, signer_id, page, type (signature/initials/date/text/checkbox/dropdown), x, y, width, height, required, label, options (JSON for dropdown), value, completed ``` **`#__mokowaas_erp_esign_comments`** — Signer questions/comments ``` id, request_id, signer_id, body, created ``` ### Competitive Positioning vs DocuSign | Feature | DocuSign | MokoWaaS+ERP | |---------|----------|-------------| | Pricing | $10-65/user/month | Included in ERP license | | Self-hosted | No (cloud only) | Yes — full data ownership | | ERP integration | Via Zapier/API | Native (same database) | | Custom branding | Enterprise plan only | All tiers | | ID verification | Add-on cost | Built-in | | Payment collection | Via integration | Native Stripe/PayPal | | API access | Developer plan | All tiers | | Data sovereignty | US/EU cloud regions | Your server, your data |

jmiller referenced this issue from a commit

2026-06-06 19:05:20 +00:00

feat: add e-signature, products, orders, invoicing tables and API (#192, #197)

jmiller referenced this issue from a commit

2026-06-06 19:05:20 +00:00

feat: DocuSign-competitive e-signature with consent, verification, encryption (#197)

jmiller referenced this issue from a commit

2026-06-06 19:51:57 +00:00

feat: Sprint 3 — E-Signature, Inventory, Labels, Email, Import admin views (#192, #197, #198, #196, #204)

jmiller changed title from ~~Native e-signature component for MokoWaaS CRM~~ to Native e-signature component for MokoSuite CRM

2026-06-07 15:15:20 +00:00

Sign in to join this conversation.