Include the Sender as a Signer in a QCDS Request

The current QCDS Request builder automatically makes the signed-in Joomla user available as a signer choice labeled with the user’s name and (Sender). Assign at least one signer-controlled field to that sender role when the sender must also sign the Request.

Assign Fields to the Sender

  1. Open Prepare & Send.
  2. In Field Assignment or an individual field’s signer search, choose the entry for the current Joomla user marked (Sender).
  3. Assign the Signature, Initials, signer information, or other interactive fields the sender must complete.
  4. Confirm the sender appears in the signer strip and highlights only the intended fields.

QCDS builds the sender choice from the current authenticated Joomla user ID, name, and email address. It also tags that role internally as sender-as-signer so the server can freeze the correct participant identity at Send Now.

The Sender Becomes a Participant Only When Used

The streamlined Request is synchronized from the signer roles actually used by signer-controlled fields. Merely having a Sender choice available does not add an extra participant. Once one or more fields resolve to the Sender role, QCDS includes the current user as a required signer participant in the frozen Request.

Place the Sender Correctly in Routing

With Everyone at once, the sender and the other signers are activated together. With Sign in order, the sender follows the position shown in the signer strip. If the sender should sign first, last, or between two external signers, select Sign in order and reorder the signer strip before sending.

Do not confuse this with a reusable Template owner or email sender identity. Sender-as-signer is a participant role in this specific Request.

How the Sender Completes Their Fields

After Send Now, the sender participant follows the same protected signer lifecycle as other participants: the applicable routing stage must activate, QCDS queues the participant invitation/access, and required assigned fields must be completed before that participant is finished. The resulting values and signing evidence become part of the immutable Request history.

Verify Before Send Now

  • The sender appears in the signer strip only when the sender actually owns signer-controlled fields.
  • The sender’s fields are highlighted under the Sender participant.
  • The sender is in the intended sequential position if using Sign in order.
  • No field was accidentally assigned to the sender just to clear an Unassigned warning.

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.