How QCDS Protects Source PDFs, Requests, Completed Files, and Attachments

Application-controlled protected delivery, non-public storage behavior, secure download authorization, file inspection/quarantine concepts relevant to users, and why sensitive artifacts should not be exposed via ordinary public URLs.

This guide applies to All plans; administrator 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

  • Capture the exact QCDS version, current Status message, Request identity, and the action that failed before changing several unrelated settings.
  • Do not include API keys, webhook signing secrets, old license keys, secure signer links, or private identity evidence in public diagnostics.
  • When possible, reproduce the problem with a small test PDF/test Contact so production data is not used as the diagnostic tool.

Step-by-Step Workflow

  1. Open Components > QC Digital Signature and the administrator tab that owns this setting or status.
  2. Record the current value/status before changing it.
  3. Apply the intended change using the current QCDS control.
  4. Save or run the provided action and read the resulting message.
  5. Verify the Status page and one representative frontend workflow before considering the change complete.

Application-controlled protected delivery

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 How QCDS Protects Source PDFs, Requests, Completed Files, and Attachments, 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.

Non-public storage behavior

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 How QCDS Protects Source PDFs, Requests, Completed Files, and Attachments, 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.

Secure download authorization

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.

File inspection/quarantine concepts relevant to users

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.

And why sensitive artifacts should not be exposed via ordinary public URLs

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

Operational troubleshooting works best when the failure domain is isolated: installation/access, Scheduled Tasks, entitlement, PDF preparation, sending/mail, signer access/Identity Verification, or completion. Fix the narrow layer rather than resetting unrelated data.

When escalation is necessary, provide enough non-secret detail to reproduce the failure without sharing secure signer URLs, provider credentials, private identity media, or other protected evidence.

Verify the Result

  • Request Details shows the expected lifecycle, participant, Timeline, and delivery state after the action.
  • 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

  • Cancelling/recreating an otherwise valid Request just to repair one failed email address.
  • Leaving transient unsent work and expecting it to appear later as a persistent draft Request.
  • 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 PDF preview or completed artifact fails, reproduce with a small known-good PDF and check QCDS Status/Scheduled Task health before changing field data.
  • If the Request is partly successful, preserve it and repair the failed participant/delivery step. Successful links and recorded history should remain usable.

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.