You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Document-Processing/PDF/PDF-Viewer/react/annotation/signature-annotation.md
-70Lines changed: 0 additions & 70 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -555,76 +555,6 @@ root.render(<App />);
555
555
556
556
N> When `enableHandwrittenSignature` is set to `false`, the handwritten signature toolbar and related UI are disabled; existing handwritten signature annotations remain in the document unless removed. The `canSave` option in annotation examples controls whether a signature can be saved for reuse; when `canSave` is `false`, signatures are not persisted in the signature collection for later reuse.
557
557
558
-
## Signature Workflow Best Practices
559
-
560
-
Designing a well‑structured [signature](#add-signature-annotation) workflow is essential for ensuring clarity, security, and efficiency when working with PDF documents. Signature workflows typically involve multiple participants—reviewers and approvers each interacting with the document at different stages. The Syncfusion React PDF Viewer provides annotation, commenting, and flattening capabilities that support these multi‑stage signature processes.
561
-
562
-
### Why structured signature workflows matter
563
-
564
-
A clear signature workflow prevents improper edits, guarantees document authenticity, and reduces bottlenecks during review cycles. When multiple stakeholders sign or comment on a document, maintaining order is crucial for compliance, traceability, and preventing accidental overwrites.
565
-
566
-
### Choosing the appropriate signature type
567
-
568
-
Different business scenarios require different signature types. Consider the purpose, regulatory requirements, and level of trust demanded by the workflow.
569
-
-**Handwritten image signature** – Best for informal approvals, acknowledgment of reading, and internal confirmation flows.
-**Typed signature** – Provides a polished, consistent appearance suitable for branded communications or standardized approval templates.
573
-

574
-
575
-
-**Image-based signature** – Allows users to upload a scanned signature image, ideal for customer-facing assets or when a handwritten look is required.
576
-

577
-
578
-
-**Digital certificate signature** – Essential for legally binding contracts, regulatory documents, and workflows that require tamper detection and verified signer identity. For more details on certified signatures, refer to the [Certified Signature documentation](https://helpstaging.syncfusion.com/document-processing/pdf/pdf-library/javascript/digitalsignature#certified-signature).
579
-
580
-
N> You can explore and try out live demos for [Invisible Signature](https://document.syncfusion.com/demos/pdf-viewer/react/#/bootstrap5/pdfviewer/invisible-digital-signature) and [Visible Signature](https://document.syncfusion.com/demos/pdf-viewer/react/#/bootstrap5/pdfviewer/visible-digital-signature) in our Sample Browser.
581
-
582
-
### Pre‑signing validation checklist
583
-
584
-
To ensure accuracy and prevent rework, [validate](../forms/form-validation) the document before signatures are added. This step is especially important in finance, HR, procurement, or contract review pipelines.
585
-
586
-
- Confirm all **required form fields** are completed—names, dates, IDs, totals, etc.
587
-
- Re‑validate key values like **financial totals**, **tax calculations**, or **contract amounts**.
588
-
- Lock or restrict editing during review to prevent unauthorized modifications between the review and signing stages.
589
-
- Use [annotations](../annotation/overview) and [comments](../annotation/comments) to flag issues before signatures are placed.
590
-
591
-
### Role-based authorization flow
592
-
593
-
A well-structured signature workflow assigns specific responsibilities to each role:
594
-
595
-
-**Reviewer** – Reviews the document, adds [comments](../annotation/comments), [highlights](../annotation/annotation-types/highlight-annotation), and other markups to suggest changes or request clarifications. Reviewers should avoid placing [signatures](#add-signature-annotation) until all issues are resolved.
596
-

597
-
598
-
-**Approver** – Examines the feedback, ensures all comments are addressed, and applies their signature once the document is finalized. Approvers may use handwritten, typed, or image-based signatures as per policy.
-**Final Approver** – Verifies that all approval requirements are met, then applies [flattening](../document-handling/preprocess-pdf#flatten-form-fields--annotations) to make annotations and signatures permanent. The final approver may also lock the document or export annotations for record-keeping.
602
-
603
-
N> For more details on flattening PDF documents and making annotations permanent, see [Flatten Annotations and Form Fields](https://helpstaging.syncfusion.com/document-processing/pdf/pdf-library/javascript/pdf-document#flatten-annotations-and-form-fields).
604
-
605
-
### Multi‑signer patterns and iterative approvals
606
-
607
-
In practice, documents often require several rounds of review and signatures from multiple stakeholders. Syncfusion’s support for annotation exchange formats (XFDF/JSON) and the integrated comments panel makes it easy to manage these collaborative workflows.
608
-
609
-
- Route the document through a defined sequence of signers to ensure proper order.
610
-
- Use [comments and replies](../annotation/comments#add-comments-and-replies) to communicate feedback and clarifications without altering the original document content.
611
-
- For external participants, share only the annotation data using [XFDF/JSON](../annotation/export-import/export-annotation) rather than distributing the entire PDF file.
612
-
- Once all signers have completed their actions, use **flattening** to finalize and lock the signatures within the document.
613
-
614
-
N> To explore advanced e-signature workflows and see a live demo, visit the [eSigning Form Designer sample](https://document.syncfusion.com/demos/pdf-viewer/react/#/bootstrap5/pdfviewer/esigning-form-designer).
615
-
616
-
### Security, deployment, and audit considerations
617
-
618
-
When managing sensitive or confidential documents (such as legal, financial, medical, or HR records), it’s important to implement robust security and compliance measures throughout the signature workflow.
619
-
620
-
-**Restrict document access:** Ensure only authorized users can view or sign documents by enforcing authentication and role-based permissions.
621
-
-**Secure endpoints:** Protect PDF endpoints with token-based access, expiration controls, and authorization checks to prevent unauthorized access.
622
-
-**Audit and traceability:** Log all signature placements, edits, and finalization events for compliance and audit purposes. This helps track who signed, when, and what changes were made.
623
-
-**Data protection:** Avoid storing confidential or high-value documents directly on client devices. Use secure storage and transmission practices.
624
-
-**Finalize documents:** After all signatures are collected, apply flattening or locking to make annotations and signatures permanent, preventing further edits.
625
-
626
-
N> Always follow your organization’s data protection and compliance policies when handling sensitive documents. For more details on flattening and securing signed PDFs, see [Flatten Annotations and Form Fields](https://helpstaging.syncfusion.com/document-processing/pdf/pdf-library/javascript/pdf-document#flatten-annotations-and-form-fields).
0 commit comments