Add Smart E-Signature Web Pro to your Bubble page and configure the signer and document properties.
Set signer_name, signer_email, and signer_identifier using your application's data. For authenticated applications, these values can come from the Current User.

Provide the original PDF through document_url. For example, you can use the URL generated by a Bubble File Uploader or a document URL already stored in your database.

Set generate_document_hash to yes to generate a SHA-256 fingerprint of the original PDF.

Set enable_pdf_signing to yes to enable PDF preview, visual signature placement, drag-and-drop positioning, resizing, page selection, and final signed PDF generation.

Set app_base_url to your Bubble application's base URL so the plugin can upload generated signature images and signed PDF files.

Use default_signature_width to define the initial size of the signature when it is placed on the PDF. The signer can resize it afterward.

The signer can click ✍️ Signature Pad to open the signature area, draw a signature, accept the electronic consent, and click ✍️ Sign.

After capturing the signature, the signer can choose:

📄 This page only — applies the signature to the current PDF page.

📑 Selected pages — applies the signature to specific pages.

📚 All pages — applies the same signature throughout the document.

The signature can then be dragged and resized directly over the PDF. Use ✅ Confirm Position to confirm its placement.

When all signature positions are ready, use 📄 Generate Signed PDF or the Generate Signed PDF plugin Action.

The plugin generates a new PDF containing the visible signature, uploads it to Bubble, calculates its SHA-256 hash, and publishes signed_document_url and signed_document_hash.

The original PDF remains unchanged.

Saving the signed document

For a database workflow where a record should only be created after successful PDF generation, use:

When Smart E-Signature Web Pro's Signed PDF Generated → Create a new Document

You can then store:

Document URL → signed_document_url
Document Hash → signed_document_hash
Original Document URL → document_url
Signature Image URL → signature_image_url
Signature ID → signature_id
Signed At → signed_at
Consent Accepted → consent_accepted
Audit JSON → audit_json

This ensures that your database record is created only after the signed PDF has been successfully generated.

Consent & Languages

When consent_text is left empty, the plugin uses its built-in consent message according to the selected language.

If consent_text is provided, the custom text overrides the built-in consent message. This allows developers to provide application-specific or jurisdiction-specific consent wording.

The language selector can be enabled so the signer can choose the preferred language directly inside the plugin.

Important Security Note

SHA-256 hashes can be used to detect document changes: modifying the underlying PDF results in a different document fingerprint. Smart E-Signature Web Pro also keeps the original-document hash separate from the final signed-document hash, providing evidence for both stages of the signing workflow.

The audit_json consolidates the technical evidence generated during the signing process and can be stored in your Bubble database for auditing, verification, or integration with external systems.

Smart E-Signature Web Pro provides technical tools for electronic-signature workflows and audit evidence. Legal validity, regulatory compliance, identity assurance, and enforceability depend on your application's implementation and the laws and requirements applicable to your use case.