Skip to main content

KolBo Operator Dashboard

KolBo Filter Platform

Groups

Named bundles of website addresses. Each group has a purpose (allow, block, or curated pick). Tiers pull from these groups to compose what a customer's filter actually enforces.

What this page does

A group is a labeled collection of websites. We compose groups into tiers ("Shomer Eynayim", "Bayis Ne'eman", etc) instead of editing every site for every customer one-by-one.

Why it matters: When KolBo Master curates one canonical "Shidduch Sites" group, every tier that references it inherits the latest curation automatically. When a reseller (yeshiva, school) needs an override, they create their own group instead of mutating the canonical one.

Related pages: Tier Templates · Master Catalog · Category Taxonomy

Supabase: mock-fallbacksrc: mock-fallbackEnv vars NEXT_PUBLIC_SUPABASE_URL / SUPABASE_SERVICE_ROLE_KEY not populated — showing canonical seed mock.

How operators use Groups (workflow)

  1. Add a domain to an existing group— open the group's detail page → add entry inline. Best for routine curation (e.g., new frum-press site joins “KolBo Frum Approved Core”).
  2. Create a new group— only when an existing group doesn't cover the use case. Most curation should extend existing groups, not multiply them. Adjacent: Category Taxonomy (broader scope) vs. new group (narrower bundle).
  3. Customer-specific override— DO NOT edit a group for a single customer. Open the customer's detail page → add a per-customer Rulebook entry instead. Keeps canonical groups clean.
  4. Reseller-specific override— yeshiva or school org creates THEIR own group instead of mutating KolBo Master's. The reseller-owned group attaches to their tier composition.

Decision guidance — when to use what

ScenarioRight tool
One specific frum-mom needs one specific site allowedCustomer Rulebook override (not a group edit)
All Bayis Neeman customers need a new approved frum siteAdd to KolBo Frum Approved Core group
Yeshiva onboarding with custom allowlist requirementsReseller creates their own org + group (not edit KolBo Master)
All-tier change to a category (e.g., shidduch policy refinement)Edit Tier Template, not the underlying group
Schema source · public.groups · 0003_creator_pattern_primitives.sql
Active groups
5
Total entries (approx)
15
Tiers covered
4

KolBo Frum Approved Core

Curator PickActive3 entries
View / Edit →

Core KolBo Approved™ sites — Torah, banking, government, kosher business directory. Always allowed across all tiers.

Tiers eligible:shomer_eynayimbayis_neemankavod_habayismosdos
Source: KolBo Master curators
Impact estimate: Used by 4 tiers · ~3 entries · Editing affects every customer on those tiers. Live impact counts (families/devices/audit-events) pending Supabase deployment per Stream 3A Phase 2.

NetFree Whitelist Anchor

AllowlistActive3 entries
View / Edit →

Anchor list from NetFree-pattern community-vetted frum-friendly sites. Subject to KolBo Master curator review per piece.

Tiers eligible:shomer_eynayimbayis_neemanmosdos
Source: NetFree community pattern (Stream 3B sources)
Impact estimate: Used by 3 tiers · ~3 entries · Editing affects every customer on those tiers. Live impact counts (families/devices/audit-events) pending Supabase deployment per Stream 3A Phase 2.

Etrog Allowlist Anchor

AllowlistActive3 entries
View / Edit →

Anchor list from Etrog-pattern community-vetted frum-friendly sites. Subject to KolBo Master curator review per piece.

Tiers eligible:shomer_eynayimbayis_neemankavod_habayismosdos
Source: Etrog community pattern (Stream 3B sources)
Impact estimate: Used by 4 tiers · ~3 entries · Editing affects every customer on those tiers. Live impact counts (families/devices/audit-events) pending Supabase deployment per Stream 3A Phase 2.

Shidduch Sites

Category BundleActive3 entries
View / Edit →

Shidduch matching / dating sites bundle. Blocked in Shomer Eynayim + Bayis Ne'eman; permitted with parental approval in Kavod HaBayis.

Tiers eligible:kavod_habayis
Source: kolbo_categories.shidduch_sites
Impact estimate: Used by 1 tier · ~3 entries · Editing affects every customer on those tiers. Live impact counts (families/devices/audit-events) pending Supabase deployment per Stream 3A Phase 2.

KolBo-curated frum-specific blocklist additions beyond OISD/EasyList. Goyish-cultural sites, secular entertainment, mixed-content news.

Tiers eligible:shomer_eynayimmosdos
Source: KolBo Master curators
Impact estimate: Used by 2 tiers · ~3 entries · Editing affects every customer on those tiers. Live impact counts (families/devices/audit-events) pending Supabase deployment per Stream 3A Phase 2.

Stream 3A status — honest scope

Schema shipped to repo: kolbofilter-api/supabase/migrations/0003_creator_pattern_primitives.sql

Server-side reader: src/lib/data/groups-query.ts — queries public.groups + public.group_entries with mock-fallback when env unpopulated.

Render gates (1 + 3): firing — list + detail surfaces shaped per schema contract.

Mutation gates (2 + 4 + 5): still blocked — live add/remove + events emission deferred to a Phase 2 vessel rep per Cardinal #84 honest scope.