Configure Monthly QCDS Request Limits by Joomla User Group

Enable optional Max/All Access group-based limits, assign allowances, use Unlimited, and understand that these local account limits are separate from QuantaCade's Basic/Pro domain-level allowance.

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

  • Work on the current QCDS 2.0.7 installation and confirm you have the Joomla permissions required for the action.
  • Read the current QCDS Status page before changing licensing, tasks, or other global settings so you preserve the original diagnostic state.
  • Use HTTPS and verify Joomla mail independently when the workflow depends on signer or completion email.

Step-by-Step Workflow

  1. Open Components > QC Digital Signature > User Group Limits while Effective Max or All Access is active.
  2. Enable monthly request limits.
  3. Assign a numeric monthly allowance to each applicable Joomla user group, or choose Unlimited for a group that should not have a local numeric cap.
  4. Save the limits.
  5. Sign in as representative users from the affected groups and verify the sender-workspace behavior before relying on the policy in production.

Enable optional Max/All Access group-based limits

QCDS keeps the underlying Base tier separate from the Effective tier that controls features now. All Access or an active Max Preview can elevate a Basic base installation to Effective Max without rewriting the purchased/base product state. This distinction matters when diagnosing a control that is visible today but could become unavailable after an entitlement or preview change.

For Configure Monthly QCDS Request Limits by Joomla User Group, 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.

Assign allowances

QCDS keeps the underlying Base tier separate from the Effective tier that controls features now. All Access or an active Max Preview can elevate a Basic base installation to Effective Max without rewriting the purchased/base product state. This distinction matters when diagnosing a control that is visible today but could become unavailable after an entitlement or preview change.

For Configure Monthly QCDS Request Limits by Joomla User Group, 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.

Unlimited

QCDS keeps the underlying Base tier separate from the Effective tier that controls features now. All Access or an active Max Preview can elevate a Basic base installation to Effective Max without rewriting the purchased/base product state. This distinction matters when diagnosing a control that is visible today but could become unavailable after an entitlement or preview change.

And understand that these local account limits are separate from

QCDS keeps the underlying Base tier separate from the Effective tier that controls features now. All Access or an active Max Preview can elevate a Basic base installation to Effective Max without rewriting the purchased/base product state. This distinction matters when diagnosing a control that is visible today but could become unavailable after an entitlement or preview change.

How This Fits into the QCDS Workflow

These settings form the installation foundation. Entitlement, Joomla access, mail, language defaults, and automation health can change which controls are available without changing the historical integrity of Requests already sent.

Keep administrator changes narrow and reversible where possible. QCDS is designed to preserve saved higher-tier settings and historical data even when access changes, so loss of current feature access is not a reason to delete configuration.

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.