Family Wall — "join / invite"
Status: ✅ BUILT v1 (2026-07-18). See INDEX.md → Family members.
Bring another person into the Family Wall. The sender picks the role; full access is the default. No new backend — reuses existing infra.
Roles (chosen by the sender)
| Role | What it does | Mechanism |
|---|---|---|
| Can help manage (default) | Sees & edits everything — routines, shopping, meals, notes — and appears on the wall | Create a family_members row for them → send the family account-link invite (migration 452, JQ Bridge connection_type:'family' + family_member_id). On accept, resolveFamilyLink links their account and household reads resolve via resolveFamilyOwnerId. |
| Can just view | Watch the wall, no account | Share the wall's token URL (/family/wall/<token>) — inherently read-only (the token IS the capability). |
Little ones (no email)
Young kids have no email, so we never email a child. Their screen is a Personal (bedroom) wall — the parent opens the token URL on the in-room device (no login). If a kid should have their own check-in identity later, the parent provisions it on their behalf (device-scoped / parent-set credential), not an email round-trip.
UI
InviteToFamilyModal (components/family/InviteToFamilyModal.tsx),
opened from "📨 Invite someone to the wall" on /dashboard/family.
Role toggle (full default) → name+email (full) or copy-a-wall-link (view). A footnote
routes little ones to Personal-wall setup.
Future (not built)
- A view-only account scope (a real "guest" role with its own login but read-only household) — today view-only = the unauthenticated wall link, which is enough for v1.
- Owner-adjustable access after accept (downgrade a co-manager to view-only, etc.).
Related: [[project_family_self_member]], [[project_family_frame]], migration 452.