Use Contacts and the Sender Identity When Assigning Template and Request Fields

QCDS lets you connect signing fields to real people instead of leaving generic roles unresolved. Saved Contacts can be searched and assigned during reusable Template preparation, while an actual Request can resolve signer roles to Contacts, workspace members, the sender, or an external email.

Assign Saved Contacts in the Template Builder

Open a Template in the visual builder and use Field Assignment. The saved-Contact search accepts the person's name, linked Joomla username, email address, or company. Choose the Contact, then use Assign all, Assign selected, or Assign unassigned as appropriate.

The Template can carry reusable Contact defaults such as the Contact identity, primary email, additional emails, phone, address, company, title, and time zone. These defaults make later Request preparation faster; they do not turn the Template itself into a sent transaction.

Template Publication Does Not Require Every Person to Be Finalized

QCDS validates the PDF and field configuration when publishing a Template. Contact assignments can still be completed or changed when creating the actual Request. This is useful when the same Template is reused with different signers.

Resolve People in the Actual Request

The Request participant-mapping workflow is broader than the reusable Template's saved-Contact picker. Current QCDS can resolve signer roles to:

  • a saved Contact;
  • a workspace member;
  • the current sender;
  • or an external email address.

One person can own multiple signer roles. Every field that requires a signer must ultimately resolve to one concrete assignee before the Request can be sent. Linked fields, such as an automatic date tied to a signature or initials field, inherit the appropriate assignment relationship.

Understand the Sender Identity

Choosing the sender as a signer is not the same as choosing an arbitrary saved Contact. QCDS represents the sender as a concrete Request assignee tied to the current sender/workspace identity. This is useful when the person preparing the Request must also sign fields in the document.

What Is Frozen into the Request

When the Request is sent, QCDS freezes participant and assignment information into the transaction. Later edits to the reusable Contact or Template do not silently rewrite the already-sent Request.

Verify Before Sending

  • Use the assignment summary to confirm how many fields are assigned and whether any remain unassigned.
  • Review each signer role and confirm it resolves to the intended Contact, member, sender, or external address.
  • Check linked signature/date relationships when those fields are used.
  • Do not send until every signer-controlled field has the correct concrete assignee.

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.