QCDS Production Go-Live Checklist

Before sending production signature Requests, verify the installation as a complete workflow—not just that the component opens. A reliable QCDS launch includes entitlement, frontend access, mail, protected storage, Scheduled Tasks, PDF preparation, signer completion, and completed-document delivery.

1. Confirm the Installed Product and Entitlement

  • Open Joomla Administrator → QC Digital Signature → Status and confirm the intended QCDS version is installed.
  • Confirm the current Base tier, Effective tier, Authorized Domain, and entitlement status.
  • Use Refresh Entitlement if the domain/plan was just changed.
  • Resolve any Entitlement Automation Integrity warning before relying on paid features.

2. Verify Frontend Access and Workspace Provisioning

  • Publish at least one Joomla site menu item for QC Digital Signature and give the intended users access to that menu item's Joomla access level.
  • Sign in as a representative sender and open the QCDS frontend through that menu item.
  • In Private / Organization Mode, confirm the user reaches the shared organization workspace with the intended role.
  • In White-Label SaaS Mode, confirm Plans & Entitlements group mappings are configured and the test user's Joomla groups resolve to the expected workspace/plan.

3. Verify Mail and Sender Identity

Under QCDS Settings, confirm the effective sender name/email. Blank QCDS sender fields intentionally fall back to Joomla's configured mail identity. Use a personal Email Template Send Test and confirm real Joomla mail reaches the signed-in test account.

4. Verify Protected Storage and Document Safety

  • Confirm Managed Private Storage is healthy and outside the Joomla webroot.
  • Review the latest Storage Health result for missing files, size/hash mismatches, unsafe links, duplicate keys, or capacity warnings.
  • Confirm the Document Safety Engine reports a usable state.
  • Upload a small representative PDF and let the bundled PDF.js page preparation finish.

5. Verify the Four Canonical Scheduled Tasks

Confirm exactly one enabled canonical task for each function:

  • QC Digital Signature Automatic Reminders — fresh-install default 60 minutes.
  • QC Digital Signature Request Timing and Deadlines — fresh-install default 5 minutes.
  • QC Digital Signature Final PDF and Completion Delivery — fresh-install default 5 minutes.
  • QC Digital Signature Entitlement Revalidation — required at least hourly.

A healthy task definition still needs Joomla's scheduler runner to execute. On a quiet site, configure a reliable Joomla-native scheduler wake-up strategy rather than assuming normal traffic will trigger tasks often enough.

6. Run One End-to-End Signing Test

Create a test Contact and Template, publish the Template, prepare a Request, exercise the routing mode you plan to use, and include representative required fields. Send to an address you control. Verify invitation delivery, signer viewing, required-field validation, submission, completion, Completed PDF/Audit Trail, and completion email delivery.

If you use Document Attachments, test both PDF presentation and Completed Package download. If you use Level 2 Identity Verification, test the selected Didit/Shufti profile and complete a safe test-mode identity flow before production.

7. Record the Healthy Baseline

Record the installed QCDS version, effective plan, scheduler health, storage-health result, mail identity, operating mode, and any provider configuration owners. That baseline makes later troubleshooting substantially faster without exposing signer links, API keys, or private evidence.

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.