Services & Blocking Rules

The Services screen turns scan findings into a reviewable inventory. It shows what the site loads, where it was found, its category, and whether effective blocking rules cover it.

Review the inventory

1. Run a scan.
2. Use search, filters, and pagination to find entries needing a decision.
3. Open the page-location details when you need to understand where a service appears.
4. Check the recognition confidence: exact, probable, custom, or unknown.
5. Review the category against the service's actual purpose on your site.

Existing classifications are retained when later scans find the same service. A detected service is not automatically approved or blocked.

Known and unknown services

For a recognized service, review its category in the row before applying rules. A category suggestion is a starting point for your review.

For an unknown external service, choose Name and block. Enter a useful name, choose the consent category, and select the detected host. Save to continue to the block confirmation. Unsupported findings explain why they cannot be blocked through that action.

You can also Ignore a finding with a reason and an optional expiry. Ignoring records your review decision; it does not add a blocking rule. Stop ignoring returns it to review without removing existing consent rules.

Apply blocking rules

1. Select the reviewed services.
2. Choose Block until consent.
3. Read the preview: services, categories, pattern changes, newly visible visitor choices, and any conflicts.
4. Confirm with Block when the changes are correct.
5. Check the result, then test the affected pages before and after granting consent.

The preview also shows declared cookies where catalogue information is available. See consent panel details.

Applying rules updates the consent engine's saved configuration. Existing manual rules and patterns needed by other managed services are preserved.

Manual edits and conflicts

If the plugin's patterns changed by hand since your previous review, Pro stops the normal apply flow and shows the difference. Review the technical details before choosing Apply anyway, or cancel and review again against the current settings.

Do not confirm an old preview after another administrator changes the rules. Refresh the review so your decision reflects the configuration actually installed.

History and recovery

• History records what changed, when, and who applied it.
• Undo reverses the newest publication using the stored history. Check the confirmation and any intervening manual edits.
• Stop blocking selected services previews removal of their managed rules. Shared and manual rules remain, so a resource may still be blocked by another rule.
• Stop blocking all removes all Pro-managed rules, including those outside the current selection. Manual rules remain.

Removing a managed rule can allow a service to load without waiting for consent when no other rule covers it. Review that effect before confirming a removal.

The consent engine's Joomla page cache is cleared after rule publication. If the result says cache clearing failed, check cache status before testing. External caches and CDNs still need your own consent-aware cache configuration.

Viewing history and the undo/removal safety actions remain available when license access lapses, subject to Joomla permissions. New publications require usable license access.