Access Modes (Strict vs Override)

The module has two access modes:

Override hidden if assigned

Goal: keep your regular catalog behaviour, but allow access to assigned products even if they are not visible in catalog.

Typical use cases:

• Contract products that should be hidden for most customers, but accessible for specific accounts
• Hidden SKUs used for reorders or spare parts

Strict whitelist (assigned only)

Goal: only assigned products should be accessible and visible.

Effects:

• Product access is restricted for logged-in customers
• Listings and search results are filtered to the allowed product IDs
• Advanced search results are filtered to the allowed product IDs
• Linked product blocks (for example related, upsell, cross-sell) are filtered to the allowed product IDs

Important:

• Strict whitelist enforcement is session-based and targets logged-in customer context.

Typical use cases:

• Customer-specific assortments where each account should only see its own catalog
• Restricted B2B portals