Require Identity Verification for All or Selected Signers

Use the all-signers Identity Verification control and supported signer-specific requirement state, understand plan/provider prerequisites, and know what happens when verification is unavailable.

This guide applies to Pro / Max / All Access; 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

Use a published Template and confirm the required Contacts are present before opening the Request workflow.
Finish unsent work in the current browser session. The streamlined flow does not present ordinary new Requests as persistent server-side drafts before Send Now.
Confirm Joomla mail and the current request allowance before production sending so a delivery or entitlement issue is found early.

Step-by-Step Workflow

Start from the correct published Template and complete Request Details.
Open Prepare & Send and make the Request-specific assignment/routing/content change.
Use Check to validate all interactive fields and participants.
Review allowance/entitlement, expiration, invitation content, and Identity Verification requirements.
Use Send Now only after the preflight is clean, then confirm initial delivery history.

The all-signers Identity Verification control and supported signer-specific

Level 2 Identity Verification is additional provider-backed assurance, available with eligible Pro/Max/All Access entitlement. Current QCDS 2.0.7 supports Didit and Shufti. Site-global settings can provide an installation-wide provider profile; sender/account settings can provide an account-level profile where the global configuration is not overriding it. Ordinary secure-link signing remains separate, so a provider outage affects signers who were specifically required to verify rather than making every QCDS transaction provider-dependent.

For Require Identity Verification for All or Selected Signers, 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.

Plan/provider prerequisites

And know what happens when verification is unavailable

How This Fits into the QCDS Workflow

The Request editor is the boundary between reusable preparation and an immutable transaction. QCDS lets you make Request-specific choices before sending, then freezes the final participants, fields, routing, message source, and other transaction context when Send Now succeeds.

Because Send Now is the transaction boundary, review the entire transaction immediately before sending: people, assignments, routing, expiration, invitation source, verification requirement, and request allowance.

Verify the Result

Request Details shows the expected lifecycle, participant, Timeline, and delivery state after the action.
Provider Test Connection succeeds and a representative Level 2 test follows the expected provider flow.
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.
Treating provider-backed Identity Verification as required for every ordinary secure-link signing workflow.
Posting provider credentials, webhook secrets, or identity evidence in public diagnostics.

Troubleshooting

If Level 2 verification fails, use the provider Test Connection and inspect provider/profile/callback configuration; ordinary Level 1 signing and historical evidence should not be reset.

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.