People and households

People and household basics

People and households should stay clear, canonical, and reviewable so churches do not build messy record habits during launch.

Who this is for: Admins and staff trying to understand the basic people model.

Last reviewed 2026-04-28 · Source of truth: launch shell · Languages: en, es

Article metadata

Product area: people and households

Owner: People data model

Parity reviewer: Bilingual launch review

Retrieval-ready: Yes

What to expect next

Use migration guidance before making assumptions about how exports will map.
Escalate when household cleanup or merge consequences feel uncertain.

Canonical model

Transparent planning treats people records and households as governed product structures, not loose labels that can drift by team habit.

The launch help surface should explain the basics clearly before deeper workspace features exist.

Why this matters early

Migration and cleanup work become harder if people and households are understood loosely from the start.

When household relationships or duplicate-record concerns feel unclear, review guidance should stay visible instead of being improvised in support chat.

Escalation path

If record cleanup or household interpretation could affect real people data, escalate instead of relying on a guessed workflow.

Related next steps

Prepare for migration review Ask grounded support Open Spanish version Back to help center