Understand the QCDS Dashboard Request Usage Card

Explain what the signed-in account's monthly request count represents and why it is not the same thing as the Basic/Pro server-authoritative domain allowance checked at Send Now.

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

  • Open QCDS from the published frontend Workspace Dashboard menu item and confirm you are signed in as the intended Joomla user.
  • Remember that Contacts and sender settings are workspace-scoped; changing one sender’s workspace should not be treated as a site-global edit.
  • For language-sensitive work, distinguish the Contact Preferred Language from the sender/workspace and administrator fallback languages.

Step-by-Step Workflow

  1. Open the QCDS screen or record that owns the topic so you are reading the current state rather than an old screenshot or memory.
  2. Compare the visible state with the current 2.0.7 rules described in this guide.
  3. Identify whether the value belongs to global installation settings, one sender workspace, a reusable Template, or one immutable/sent Request.
  4. Make changes only at the layer that owns the behavior.
  5. Verify the result with a safe test and preserve historical Requests/evidence.

What the signed-in account's monthly request count represents and why it is

Check is the preflight step for the Request. It catches unassigned/invalid interactive fields, broken required configuration, missing signer information, and related send blockers. Send Now then performs the current plan/allowance authorization before the transaction becomes sent and attempts the initial invitations immediately. Automatic Reminders is for later reminder work; it is not the initial-send mechanism.

For Understand the QCDS Dashboard Request Usage Card, 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.

The current QCDS workflow preserves the intended result

Check is the preflight step for the Request. It catches unassigned/invalid interactive fields, broken required configuration, missing signer information, and related send blockers. Send Now then performs the current plan/allowance authorization before the transaction becomes sent and attempts the initial invitations immediately. Automatic Reminders is for later reminder work; it is not the initial-send mechanism.

For Understand the QCDS Dashboard Request Usage Card, 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.

To verify before relying on this behavior in production

Check is the preflight step for the Request. It catches unassigned/invalid interactive fields, broken required configuration, missing signer information, and related send blockers. Send Now then performs the current plan/allowance authorization before the transaction becomes sent and attempts the initial invitations immediately. Automatic Reminders is for later reminder work; it is not the initial-send mechanism.

How This Fits into the QCDS Workflow

The sender workspace is deliberately private. Contacts, Templates, Requests, Email Template overrides, and sender defaults belong to that workspace so one Joomla user does not accidentally operate another sender’s transaction history.

The workspace model also explains why one user’s Contacts or Email Template override should not be used as global data for another sender. Site-global policy belongs in Administrator settings; sender defaults belong in the sender workspace.

Verify the Result

  • Request Details shows the expected lifecycle, participant, Timeline, and delivery state after the action.
  • 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.

Troubleshooting

  • If the Request is partly successful, preserve it and repair the failed participant/delivery step. Successful links and recorded history should remain usable.

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.