Family workspace

Summary

Family is a top-level workspace switched via the avatar dropdown — a peer of the four pillars, not a Settings sub-section — sharing Expense and Portfolio across up to 6 PANs while keeping Tax and Inbox private by default. Every family member has their own Firebase login and their own DPDP consent — chitragupt has no "in-workspace person-identity" concept, meaning a single user cannot manage a spouse/parent/kid without them signing up too.

Why it matters

Indian households filter financial decisions through the household, not the individual: a parent's senior-citizen §80D is claimed under a child's return, sibling equity sales are sequenced to use the ₹1L LTCG exemption twice, and so on. But India has no joint filing — every PAN files its own ITR. The family workspace exists to surface those cross-PAN moves advisorily without ever producing a joint return. Putting it at workspace level (not Settings) signals that switching contexts is a primary action, not configuration.

Implications

• Flat structure — no "head of household". Anyone can invite, anyone can leave.
• Combined Expense + Portfolio is always on inside the workspace. Personal Tax and Inbox stay private unless explicitly shared.
• "Family Tax Stacked" view shows per-member tax position side-by-side. It is advisory, never a joint return.
• Aggregation is read-only computation at read time. The DB stores per-user data only — never duplicate rows into a "household bucket". This lines up with the user-identity-entry chain: each family member's data hangs off their own users/{uid}/identities/*.
• Dependents = own Firebase login. There is no "in-workspace person-identity" — a single user cannot create a spouse/parent/kid identity inside their own workspace. Every additional person joins via family-invite, gets their own login, gives their own DPDP consent. This is what makes Pro Family compliant.
• A persistent "Viewing as " indicator is mandatory on every authed page.
• Family workspace gating sits on tier-pro-family only; lower tiers cannot createFamily or invite.
• Settings owns only the administration of the workspace (invite, role, scope, leave, dissolve) — never the workspace surface itself.
• Cross-user family-transfer (misfiled doc → correct member) uses the collapsed pending_identity_confirmation status per 2026-07-11-user-identity-entry-model.

Related

• tier-pro-family — the only tier that unlocks the workspace
• four-pillars — Family sits at the same nav level, not as a fifth pillar
• pillar-tax — where the Family Tax Stacked view lives
• pillar-expense — combined household lens
• pillar-portfolio — combined household lens
• user-identity-entry — each family member owns their own User → Identity → Entry chain
• identity-buckets — the 12 Inbox buckets rendered per member
• 2026-06-24-family-invite-landing — invite landing decision
• 2026-07-11-user-identity-entry-model — cemented "no in-workspace person-identity" rule

Sources

• .context/wiki/concepts/* § "Family workspace"
• .context/wiki/concepts/* § "Hard rules" rules 8, 9, 15