Create a Personal QCDS Email Template Override

Edit/save a sender-specific override, Published Yes/No behavior, built-in fallback, source language, and why one source set is maintained rather than one editable copy per destination language.

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

Verify Joomla itself can send mail before troubleshooting QCDS message templates.
Keep supported template tokens intact; QCDS protects/restores tokens during rendering and translation.
Remember that QCDS maintains one authoritative creator-authored source rather than asking you to maintain a separate editable copy for every language.

Step-by-Step Workflow

Open QCDS > Email Templates and edit the template you want to override.
Edit Subject and Plain text, and choose Built-in HTML from Plain Text or Custom HTML as appropriate.
Set Published to Yes to use the personal override, or choose the built-in fallback when you want QCDS defaults.
Insert supported tokens from the Useful token controls and keep them intact.
Preview HTML, save the template, and use Send Test before relying on it in production.

Edit/save a sender-specific override

Participant language is resolved at use time in this order: Contact Preferred Language, sender/workspace Default frontend language, administrator Default frontend language, then English (en-GB). QCDS can translate creator-authored participant communication when needed, while protecting tokens, URLs, and HTML. If safe translation is unavailable, it falls back to the complete frozen source message rather than sending a partially translated mixture.

For Create a Personal QCDS Email Template Override, 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.

Published Yes/No behavior

Built-in fallback

Source language

And why one source set is maintained rather than one editable copy per

How This Fits into the QCDS Workflow

QCDS resolves participant language at use time and can translate frozen creator-authored communication when needed. Historical deliveries keep their original evidence while later reminders or signer-page loads can use a Contact’s newly selected Preferred Language.

Treat translated communication as delivery-time presentation of a frozen creator source. That protects historical meaning and makes fallbacks deterministic if a translation provider cannot safely translate one message.

Verify the Result

A real test message leaves Joomla and arrives at the intended mailbox with the correct sender identity and format.
The Template validates and a new test Request renders the expected field/content behavior without changing older Requests.
A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

Publishing before running Validate and resolving actual configuration problems.
Assuming a later Template edit will update a Request that was already sent.
Troubleshooting QCDS message content before confirming Joomla itself can send mail.
Editing the characters inside a supported token or translating the token name.

Troubleshooting

If the email does not arrive, test Joomla mail, check QCDS delivery history, then distinguish authentication/connection problems from a rejected recipient address.
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.

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.