Explore Visibility & Gating

Purpose: Describe how blur/gating applies on the Explore page (/explore) for filters, search and sort by subscription plan. Audience: Product, Developer Prerequisites: blurred_fields configuration in the database.

Overview

• Explore capabilities are configurable via keys in blurred_fields:
  • explore_filters, explore_search, explore_sort, explore_categories, explore_listings (optional)
• These keys control UI elements (they do not map to listings columns), so the gating is applied at UI-level.
• For listing data, server-side blur is enforced by the listing_view_secure view.

Behavior by plan

• Unauthenticated / Free: marked components can be blurred/disabled
• Starter: components become accessible (if starter flags are false)
• Pro: extended access
• Admin: full bypass

Configuration

• Admin UI → Subscription Plans → Blurred Fields Manager
  • Add/edit explore_* keys
  • Toggle by plan (unauth/free/starter/pro)
• DB RPC (alternative):

select public.admin_toggle_blurred_field('FIELD_UUID','free',true);

QA Checklist

• Unauth:
  • Filters/Sort/Search appear blurred if corresponding explore_* keys are enabled for unauth
• Free vs Starter/Pro:
  • Components are unlocked after authentication/subscription
• Listing data:
  • Sensitive fields remain governed by listing_view_secure

Related

• docs/architecture/blur-policy.md
• docs/operations/blur-playbook.md
• docs/features/listings.md (Search & Filters)