Grant QCDR Preview and Discovery Permissions Safely

Test Rules and Run Discovery permissions, signed frontend sessions, current-user checks, why entitlement alone does not grant permission, and recommended trusted roles.

This guide follows the accepted QC Dynamic Replacer 1.1.05 implementation and applies to Pro/Max; Joomla ACL administrator. Where older manuals or walkthrough wording differs from the current source or the accepted keyless-entitlement behavior, the current implementation takes precedence.

Before You Begin

Plan least-privilege groups before assigning specialized QCDR actions.
Remember that entitlement and Joomla permission are separate gates.
Test with a non-Super-User account after ACL changes.

Step-by-Step Workflow

Save the Rule first, even if it remains Draft or Disabled.
Confirm your Joomla account has Test Rules and the current tier includes private Preview.
Enter a same-site frontend URL that represents the intended Rule target.
Launch Preview from the Rule editor and inspect the private transformed page.
Read Rule Health for state/tier, target, audience, schedule, dependency, match, and protected-region gates.
Correct the Rule and relaunch Preview rather than enabling it just to test.
After successful private testing, enable the Rule only if ordinary runtime behavior is desired.

Discovery Tool Reference

Tool	Purpose
Click It, Change It	Select rendered output privately and inspect evidence before creating a Draft Rule.
Page Scan	Bounded inventory of notable text/headings, links/buttons, media, forms, Token regions, component/module markers, and Rule effects.
Explain This Output	Move a Page Scan result into the standard evidence/fingerprint inspector.
Site Impact Scan	Check the current page, published menu routes, and supplied same-site URLs; current limit is 40 de-duplicated pages.
Dynamic DOM Watch	Observe late browser-side DOM mutation for up to 60 seconds or 600 mutation records; timing is evidence, not JavaScript call-stack attribution.

QCDR Joomla Permission Reference

Action	What it controls
core.manage / core.admin	Baseline Administrator component access/inheritance.
Manage Settings	Change installation-wide QCDR settings.
Manage License	Use entitlement/license-management actions.
Manage Rules	Create and maintain Rules.
Manage Tokens	Create and maintain non-PHP Tokens.
Manage PHP Tokens	Independently author/modify PHP Tokens; required in addition to Max/All Access.
Test Rules	Launch authorized private Preview and Rule Health.
Run Discovery	Launch private Discovery / Click It, Change It sessions and Draft Rule handoff.
Use Workspace	Open the frontend Dynamic Replacer Workspace readiness dashboard.

Test Rules and Run Discovery permissions

QCDR 1.1.05 uses the current keyless Authorized-Domain entitlement model. Basic remains the fallback feature set, while paid Pro/Max and All Access are resolved from the normalized Authorized Domain rather than a customer-entered current license key. The one-time 30-Day Max Preview starts only when an authorized administrator explicitly selects Start 30-Day Max Preview; installation, navigation, Refresh Entitlement, frontend requests, and the Scheduled Task do not consume an untouched preview. Base tier and Effective tier remain separate so All Access or Preview can temporarily elevate capability without rewriting the underlying product state. Upgraded sites can still show a Legacy License Key, but clearing it is a compatibility cleanup action and must preserve Rules, Tokens, settings, preview history, and current Authorized-Domain state.

For Grant QCDR Preview and Discovery Permissions Safely, evaluate this against the exact frontend request that matters. A saved QCDR item can be valid in Administrator yet remain inactive because a different eligibility gate, dependency, permission, cache layer, or runtime safety boundary correctly prevents transformation. Keeping those concerns separate makes both testing and later support much easier.

Signed frontend sessions

Current-user checks

Entitlement alone does not grant permission

And recommended trusted roles

How This Fits into QCDR

The frontend Workspace is a readiness/status surface. Rule and Token editing remains an Administrator workflow.

The safest operating pattern is to keep configuration narrow, use QCDR’s private diagnostics before broad activation when your tier permits them, and preserve Joomla Administrator as the recovery surface. Because QCDR changes the rendered response rather than source files, a correctly disabled or bypassed runtime path should expose the underlying Joomla output again without requiring a source-file rollback.

Verify the Result

Status shows the expected Base and Effective tiers for the normalized domain.
Entitlement Revalidation is healthy and hourly unless the article is specifically diagnosing that task.
The Rule state and drag order are exactly what you intended.
A page that should match changes as expected, and a page outside scope remains unchanged.
The Discovery session remains private/same-site and no Rule was silently enabled or retargeted.
Any Draft Rule created from evidence was manually reviewed before use.
Reload the real frontend request instead of relying only on the saved Administrator form.

Common Mistakes to Avoid

Enabling a broad Rule for ordinary visitors merely to test something private Preview can validate safely.
Treating LIKELY/LOW/MEDIUM evidence as automatic authority to retarget or enable a Rule.
Changing several gates at once during troubleshooting, which makes the actual cause difficult to identify.
Testing only while signed in as Super User when ordinary users/guests are the intended audience.
Skipping a recovery plan before enabling a site-wide HTML, JavaScript, protected-area, or PHP-backed change.

Troubleshooting

If nothing changes, confirm the package-owned System plugin is enabled, the relevant Live Processing switch is on, and the item is eligible for the current Effective tier.
If targeting appears wrong, inspect page/menu/URL, extension, audience, schedule, IP, technical conditions, and protected-region behavior as separate gates.
If a Token-backed Rule preserves the original match, troubleshoot the Token dependency/readiness before changing the Find value.
If behavior differs between browsers/users, clear or bypass relevant Joomla/full-page/CDN caches and compare request context.
If private Preview/Discovery fails, start a fresh authorized same-site session and confirm the Joomla ACL action as well as the product tier.

Operational Best Practice

Make runtime changes deliberately: use a narrow scope first, keep broad Rules Draft or Disabled until tested, preserve the independent Rule/Token emergency switches, and record the QCDR version plus the exact Rule/Token and affected URL when handing a problem to another administrator. For high-impact HTML, protected-region, JavaScript, dynamic-data, or PHP work, test representative anonymous and authenticated requests and review caching before expanding scope.

Community Discussion

Want to compare workflows, share practical examples, or discuss how other administrators use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.