Upload a Document Attachment While Signing

Upload the current supported PNG/JPEG image attachment, understand safe normalization and protected-original storage, and see how the attachment appears in the completed output.

This guide applies to All plans; external signer and follows the accepted QC Digital Signature 2.0.7 implementation. Where older walkthrough language differs from the current interface or source behavior, use the current QCDS state as the authority.

Before You Begin

  • Treat the signer link as personal transaction access. Do not publish, forward, or paste it into public support posts.
  • If Level 2 Identity Verification is required, confirm the applicable Didit or Shufti provider profile is configured and tests successfully before sending.
  • Test the signer experience in a normal browser/mobile context, not only while logged into Joomla as an administrator.

Step-by-Step Workflow

  1. Open the secure signer page and select the Document Attachment field.
  2. Choose one PNG or JPEG image.
  3. Review the selected file/preview and confirm it is the intended evidence.
  4. Complete the remaining required signer fields.
  5. Submit the signer fields; QCDS preserves the original attachment in protected storage and uses the configured completed-PDF presentation behavior.

Upload the current supported PNG/JPEG image attachment

A Document Attachment field accepts one PNG or JPEG image from the signer. QCDS preserves the protected original and can append a readable presentation page to the Completed PDF. When “Display attachment in completed PDF” is disabled, the attachment page remains in the evidence flow but its PDF presentation is heavily pixelated/obscured and marked privacy-protected; the original protected attachment is still retained for authorized Completed Package access.

For Upload a Document Attachment While Signing, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

Safe normalization and protected-original storage

A Document Attachment field accepts one PNG or JPEG image from the signer. QCDS preserves the protected original and can append a readable presentation page to the Completed PDF. When “Display attachment in completed PDF” is disabled, the attachment page remains in the evidence flow but its PDF presentation is heavily pixelated/obscured and marked privacy-protected; the original protected attachment is still retained for authorized Completed Package access.

For Upload a Document Attachment While Signing, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

And see how the attachment appears in the completed output

A Document Attachment field accepts one PNG or JPEG image from the signer. QCDS preserves the protected original and can append a readable presentation page to the Completed PDF. When “Display attachment in completed PDF” is disabled, the attachment page remains in the evidence flow but its PDF presentation is heavily pixelated/obscured and marked privacy-protected; the original protected attachment is still retained for authorized Completed Package access.

How This Fits into the QCDS Workflow

Ordinary QCDS signing is a secure-link workflow and does not require the signer to have a Joomla account. Identity Verification is an additional assurance layer for selected transactions; it does not replace the core signing system.

Signer usability and evidence quality are linked. Clear field placement, private secure-link handling, and explicit Identity Verification requirements make it easier for the signer to complete the intended act without ambiguous workarounds.

Verify the Result

  • The Completed PDF/Package opens, preserves the signed source and evidence, and the Audit Trail remains readable.
  • A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

  • Asking signers to sign again when only final PDF generation or completion delivery failed.
  • Replacing a prior valid artifact before a regeneration attempt has been verified.

Troubleshooting

  • If the result differs from this guide, capture the current QCDS version, Status message, owning object ID/reference, and exact reproducible action before opening a support request.

Operational Best Practice

Test meaningful changes with controlled data before relying on them in production. Keep QCDS, Joomla mail, Scheduled Tasks, and entitlement health observable; preserve successful Requests and completed evidence; and make the smallest change that solves the actual problem. For handoff or support, record the QCDS version, relevant Request/Template reference, the exact action taken, and the visible result without including secrets.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.