Use the QCDS Support Tab and Gather Safe Diagnostic Information

Read product/version/domain/entitlement/Installation UUID information, understand what can safely be shared with support, and avoid exposing provider secrets or legacy credentials.

This guide applies to All plans; administrator 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

  • Capture the exact QCDS version, current Status message, Request identity, and the action that failed before changing several unrelated settings.
  • Do not include API keys, webhook signing secrets, old license keys, secure signer links, or private identity evidence in public diagnostics.
  • When possible, reproduce the problem with a small test PDF/test Contact so production data is not used as the diagnostic tool.

Step-by-Step Workflow

  1. Open Components > QC Digital Signature and the administrator tab that owns this setting or status.
  2. Record the current value/status before changing it.
  3. Apply the intended change using the current QCDS control.
  4. Save or run the provided action and read the resulting message.
  5. Verify the Status page and one representative frontend workflow before considering the change complete.

Read product/version/domain/entitlement/Installation UUID information

The key point for Use the QCDS Support Tab and Gather Safe Diagnostic Information is Read product/version/domain/entitlement/Installation UUID information. Work from the current QCDS 2.0.7 interface and the saved state of the specific workspace, Template, Request, or installation involved. QCDS separates reusable configuration from sent transaction evidence, so prefer the action that changes only the intended current object rather than rewriting unrelated historical records.

For Use the QCDS Support Tab and Gather Safe Diagnostic Information, 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.

What can safely be shared with support

The key point for Use the QCDS Support Tab and Gather Safe Diagnostic Information is understand what can safely be shared with support. Work from the current QCDS 2.0.7 interface and the saved state of the specific workspace, Template, Request, or installation involved. QCDS separates reusable configuration from sent transaction evidence, so prefer the action that changes only the intended current object rather than rewriting unrelated historical records.

For Use the QCDS Support Tab and Gather Safe Diagnostic Information, 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 avoid exposing provider secrets or legacy credentials

The key point for Use the QCDS Support Tab and Gather Safe Diagnostic Information is and avoid exposing provider secrets or legacy credentials. Work from the current QCDS 2.0.7 interface and the saved state of the specific workspace, Template, Request, or installation involved. QCDS separates reusable configuration from sent transaction evidence, so prefer the action that changes only the intended current object rather than rewriting unrelated historical records.

How This Fits into the QCDS Workflow

Operational troubleshooting works best when the failure domain is isolated: installation/access, Scheduled Tasks, entitlement, PDF preparation, sending/mail, signer access/Identity Verification, or completion. Fix the narrow layer rather than resetting unrelated data.

When escalation is necessary, provide enough non-secret detail to reproduce the failure without sharing secure signer URLs, provider credentials, private identity media, or other protected evidence.

Verify the Result

  • Status shows the expected Base and Effective tier and no unresolved entitlement-task integrity warning.
  • A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

  • Following old instructions that require entering a current license key instead of using Authorized Domains.
  • Starting the one-time Max Preview merely to inspect a feature before you are ready to evaluate it.

Troubleshooting

  • If a paid feature unexpectedly locks, inspect Authorized Domain resolution, Base/Effective tier, and the hourly Entitlement Revalidation task before changing saved configuration.

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.