Add or Edit a QCDS Contact

Create and maintain a Contact, choose the primary identity information used during request preparation, and understand which values are reusable versus transaction-frozen.

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

  1. Open QCDS > Contacts and click Add Contact, or open an existing Contact for editing.
  2. Enter the person’s name information and at least one valid email address.
  3. Optionally add company, title, phone, consolidated address, Preferred Language, and private Notes.
  4. Separate multiple email addresses with a comma or semicolon when using the compact email entry.
  5. Save the Contact, then confirm it can be found from Template/Request assignment search.

Create and maintain a Contact

A QCDS Contact is reusable workspace data for a real participant. It can hold name information, company, title, phone, consolidated address, one or more email addresses, a Preferred Language, and private Notes. The Contact is not the historical Request itself: when a Request is sent, QCDS freezes participant data into the transaction so later Contact edits do not rewrite prior evidence. Signer-correctable profile fields can update the saved Contact after successful signing where the current field behavior allows it.

For Add or Edit a QCDS Contact, 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.

Choose the primary identity information used during request preparation

A QCDS Contact is reusable workspace data for a real participant. It can hold name information, company, title, phone, consolidated address, one or more email addresses, a Preferred Language, and private Notes. The Contact is not the historical Request itself: when a Request is sent, QCDS freezes participant data into the transaction so later Contact edits do not rewrite prior evidence. Signer-correctable profile fields can update the saved Contact after successful signing where the current field behavior allows it.

For Add or Edit a QCDS Contact, 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 understand which values are reusable versus transaction-frozen

A QCDS Contact is reusable workspace data for a real participant. It can hold name information, company, title, phone, consolidated address, one or more email addresses, a Preferred Language, and private Notes. The Contact is not the historical Request itself: when a Request is sent, QCDS freezes participant data into the transaction so later Contact edits do not rewrite prior evidence. Signer-correctable profile fields can update the saved Contact after successful signing where the current field behavior allows it.

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.
  • 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 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.