Households, children included
A family shares one household card. Adults sign in on their own; children are name-only entries with no email or login.
People & groups
Know everyone in your church, not only the volunteers.
Profiles and households for the whole congregation, small groups that leaders run themselves, newcomer follow-up, and pastoral care that stays private.
Highlights
A gentle membership journey
Visitor, Regular attender, Member, or Inactive. Only an admin sets the status; nobody changes their own.
Pastoral notes kept private
Admins keep a timeline of visits and seasons of care. Ministry leaders never see these notes.
Small groups leaders run
Public or private groups, join requests a group admin approves, and recurring meetings placed on the calendar automatically.
Attendance without homework
After a tracked meeting, group admins get an emailed checklist. Tick who came and save.
Bring your list with you
Import people and households from CSV with a preview first, and reuse saved column mappings when migrating from another system.
A newcomer queue that does not lose anyone
A bilingual, consent-first “New here?” card feeds a scoped staff queue. Staff assign cards, schedule follow-ups, and add notes. Linking to People is allowed only for an exact contact match.
Group attendance from an email link
Turn on attendance tracking for a routine event. When the meeting ends, every group admin receives a link to that meeting’s checklist, valid for three days.
Your data stays portable
Export people and households as canonical CSV in numbered parts. Pastoral notes, roles, permissions, and security fields are excluded from the export.
Several campuses, one installation
Run campuses on one backend with isolated data, settings, features, and campus-local roles. Only the master admin sees every campus.
Prayer care on a simple board
Requests arrive from the public prayer form and move through New, Praying, Long-term, Waiting on God, Answered, and Closed. Every action is logged.
Good to know
- One CSV upload is limited to 256 KiB, 200 data rows, and 100 households.
- Group events with open sign-ups or payment use Registration, which needs the Supabase backend. On D1 that section does not appear.
- Duplicate people are never merged by name alone. Ambiguous matches go to a review queue.
- Attendance and follow-up emails need an email setup when deployed.
Read the full feature guide
Keep exploring
See it with your own eyes.
Open the demo church in your browser, then read the setup guide when you are ready.