Require Identity Verification for All or Selected Signers

QCDS can require provider-backed Identity Verification for every active signer or only selected signers. The requirement is chosen while preparing the Request and becomes part of the immutable participant evidence when Send Now succeeds.

Confirm Identity Verification Is Available

Identity Verification is available with an effective Pro, Max, or All Access entitlement. QCDS also needs an enabled provider profile whose saved connection has been tested and is ready for new Requests. QCDS 2.0.7 supports Didit and Shufti.

A site-level Global profile takes precedence when it is enabled. If that Global profile is enabled but not ready, QCDS does not silently fall back to the sender's account-level profile. The Prepare & Send controls remain unavailable until the active profile is usable.

Require Verification for Every Signer

  1. Open the published Template with Use Template and go to Prepare & Send.
  2. Assign the signer-controlled fields so the signer strip contains the people who will act on the Request.
  3. Select Require ID Verification for all signers.
  4. Review each signer pill. QCDS marks every current actionable signer role as requiring Identity Verification.
  5. Run Check, then use Send Now only when the Request is ready.

If you later add another signer by assigning fields to a new role, review the Identity Verification settings again before sending.

Require Verification for Selected Signers

Each signer in the signer strip also has its own Require ID Verification checkbox. Clear the all-signers choice, then enable the requirement only for the signer or signers that need the additional verification step. CC and completion-recipient roles are not treated as identity-verification signing participants.

What Send Now Rechecks

The browser setting is not the final authority. During Send Now, QCDS revalidates that Identity Verification is available for this sender and Request. QuantaCade request authorization must also authorize Identity Verification when any participant requires it. If either check fails, QCDS blocks the send before creating the immutable Request.

When Send Now succeeds, QCDS binds each required participant to the provider profile resolved at send time and records the requirement in the Request history. The signer cannot sign until that participant's verification reaches Verified.

If Verification Becomes Unavailable

Before Send Now, an unavailable provider prevents a new Request from being sent with Identity Verification required. After Send Now, the requirement is already part of the immutable participant state. If the provider profile later loses usable credentials or becomes unavailable, the affected signer is blocked from signing until verification can succeed; the existing Request and its evidence should be preserved rather than recreated.

A Trial/Test provider profile can be used for end-to-end sandbox testing when QCDS reports it ready. Treat that result as test evidence, not production identity evidence.

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.