Configure Your QCDS Workspace Settings

Set organization/account name, time zone, default frontend language, unsigned-request reminder interval, and default expiration for the sender's private workspace.

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

Open QCDS from the published frontend Workspace Dashboard menu item and confirm you are signed in as the intended Joomla user.
Remember that Contacts and sender settings are workspace-scoped; changing one sender’s workspace should not be treated as a site-global edit.
For language-sensitive work, distinguish the Contact Preferred Language from the sender/workspace and administrator fallback languages.

Step-by-Step Workflow

Open QCDS > Settings in the sender workspace.
Set the organization/account name and the sender’s time zone.
Choose the Default frontend language used when a Contact has no Preferred Language.
Set the unsigned-request reminder interval and default Request expiration.
Save, then start a test Request and confirm the defaults seed the new transaction as expected.

Set organization/account name

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 Configure Your QCDS Workspace Settings, 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.

Time zone

Default frontend language

Unsigned-request reminder interval

And default expiration for the sender's private workspace

How This Fits into the QCDS Workflow

The sender workspace is deliberately private. Contacts, Templates, Requests, Email Template overrides, and sender defaults belong to that workspace so one Joomla user does not accidentally operate another sender’s transaction history.

The workspace model also explains why one user’s Contacts or Email Template override should not be used as global data for another sender. Site-global policy belongs in Administrator settings; sender defaults belong in the sender workspace.

Verify the Result

Request Details shows the expected lifecycle, participant, Timeline, and delivery state after the action.
Joomla Scheduled Tasks shows the relevant canonical QCDS task enabled with a sensible next execution time.
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.

Troubleshooting

If due work is late, confirm the canonical task is enabled and being triggered; a correctly defined task on a quiet Joomla site can still remain overdue without a reliable wake-up mechanism.
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.