Tier Templates
Four canonical KolBo tiers, each tuned to a frum-life-stage. Tiers compose Groups + DNS defaults + Hebrew/English labels. Every customer is on exactly one tier; per-member overrides layer on top.
▸What this page does
A tier is a named bundle of DNS defaults + Group attachments + KolBo customization, tuned to a frum-life-stage (yeshiva bachur vs working professional vs institutional mosad). Customers are assigned to exactly one tier at onboarding.
Why it matters: Tiers solve the per-customer-explosion problem: 1,000 customers don't need 1,000 custom rulebooks. They need to fit one of four canonical tiers, with per-member overrides handling the exceptions. KolBo's frum-curated tier set (Shomer Eynayim / Bayis Ne'eman / Kavod HaBayis / Mosdos) is the moat — competitors offer generic "strict/medium/loose" tiers; KolBo names tiers in frum-life-stage language and tunes each to real frum-family-segment needs.
Related pages: Groups (compose into tiers) · Customer roster (assign tier) · Master Catalog (Library)
How operators use Tier Templates (workflow)
- Assign tier at customer onboarding— every new customer picks one of the 4 tiers based on their frum-life-stage. Most common: Bayis Ne'eman default for standard frum families.
- Adjust tier composition (rare)— open the tier's detail page → add/remove Groups. Rare because tier-level changes affect EVERY customer on that tier. Cardinal #61: confirm-modal required.
- Per-customer override (most common) — for one-off customer needs, edit their Customer Rulebook instead of mutating the tier. Tier stays clean.
- Reseller overlay (Mosdos tier only)— yeshivas, schools, shuls with the Mosdos tier can create their own tier-overlay rows without mutating KolBo Master's canonical Mosdos tier.
Decision guidance — when to use what
| Scenario | Right tool |
|---|---|
| One customer needs a specific site allowed | Customer Rulebook override (not tier edit) |
| Every Bayis Ne'eman customer should now block a new category | Edit Bayis Ne'eman tier (add Group) — confirm-modal fires per Cardinal #61 |
| Yeshiva onboarding wants custom Mosdos tier composition | Reseller overlay (Mosdos tier; their org gets own tier_groups rows) |
| New life-stage tier needed (e.g., “Newlywed-couple tier”) | Founder strategic decision — adding tiers is platform-level + tier inventory locked at 4 canonical; surface to operator first |
Shomer Eynayim
Strictest tier — full blocklist + NSFW + KolBo Frum Block additions. For yeshiva bachurim, kollel families, max protection.
Typical audience: Yeshiva bachurim, kollel families, anyone wanting maximum protection
Bayis Neeman
Standard frum household tier — full blocklist + NSFW. Balanced strictness for working families.
Typical audience: Standard frum families with working parents + kids at home
Kavod HaBayis
Lighter tier — adult-content blocking + malware, fewer category restrictions. For working professionals needing business-website access.
Typical audience: Working professionals (accountants, lawyers, real-estate) needing general-business access
Mosdos
Institutional tier for yeshivas / schools / shuls — strictest + reseller-policy overlay capability.
Typical audience: Yeshivas, schools, shuls — institutions with reseller-org override authority
Phase 2+: edit tier defaults · per-tier app curation defaults (Epoch 2 reservation) · per-tier content filtering defaults (Epoch 3 reservation) per Nuance 9 cross-epoch design.