How QCDS User Group Limit Inheritance and Multiple Groups Work

Explain inherited authorized Joomla groups, highest-applicable allowance, Unlimited precedence, Super User behavior, and the effect of leaving an applicable group without a positive configured 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

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

Inherited authorized Joomla groups

Max / All Access can apply optional local monthly request limits by Joomla user group. These account/user limits are separate from QuantaCade’s plan-level Basic/Pro domain allowance. When a user belongs to multiple applicable groups, QCDS evaluates the configured group policy, with Unlimited taking precedence over numeric caps and the highest applicable allowance preventing an accidentally lower secondary group from reducing access.

For How QCDS User Group Limit Inheritance and Multiple Groups Work, 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.

Highest-applicable allowance

Unlimited precedence

Super User behavior

And the effect of leaving an applicable group without a positive configured

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

The owning QCDS screen reflects the intended saved state after reload.
A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

Changing several unrelated settings before recording the original QCDS state.
Using old walkthrough behavior when it conflicts with the current 2.0.7 interface/source.

Troubleshooting

If the result differs from this guide, capture the current QCDS version, Status message, owning object ID/reference, and exact reproducible action before opening a support request.

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.