Flock RosterConnect
Everyone findable. Nothing overshared.
Roster is your church's private member directory. Members find and reach one another, every person decides who sees each field of their profile, and children never show contact details - guaranteed by the database, not just a setting.
What it does
Members find one another
Browse, search, and reach people in your congregation. Contact goes through a relay, so a member can be reachable without their email or phone ever being shown or scraped.
Privacy, per field
Every member chooses who sees each field of their profile across six audience tiers, from public down to only me, and can preview their own profile exactly as any audience would see it.
Children, guarded by the schema
Children's records are created and managed by adults and can never carry contact details: the database itself forbids it. Not a setting someone can flip - a rule the schema enforces.
Custody-aware pickup, when you turn it on
Staff record who may collect a child, and who may not. At check-out the decision is made in the database, in the same transaction as the release, so a restriction added minutes earlier still applies. A deny is never overridable, parents see their own child's approved list, and merging two member records can never weaken a deny.
A printed book worth keeping
A designed, print-ready directory: a member edition and a watermarked staff edition, letter or half-letter booklet trims, two type themes, thumb tabs, running guide words, and a dot-leader name index. It prefills from your church's own branding.
Ask the directory in plain English
Search in ordinary language and the model writes a validated filter, never a query against member data and never SQL. Results stay redacted per viewer, so nobody sees a field they could not already see. Plain name search is never metered.
Staff tools built in
Multi-household families, duplicate detection and merge, a photo-review queue with virus scanning, freshness nudges for stale profiles, custom fields, groups and serving teams, a safeguarding dashboard for volunteer clearances, and staged imports from CSV, Planning Center, or Breeze - mapped and reviewed before anything reaches the directory.
Try it right here
This preview runs the product's real visibility resolver - pick an audience and watch each field decide.
View Ruth's profile as
- [email protected]
- Phone
- Hidden (Family)
- Address
- Hidden (Staff only)
A member sees 1 of 3 fields. Ruth chose that; the database enforces it.
The short answers.
- Who can see a member's contact details?
- Each member decides, field by field, across six audience tiers: public, members, my groups, family, staff only, or only me. The rules are enforced by the database itself, so the server never sends a field the viewer may not see.
- Is the directory safe for children?
- Yes. Children's records are created and managed by adults, and the database schema itself forbids storing contact details on a minor. A hidden child never appears in another member's view, and pickup follows the custody records your staff keep.
- Can members contact each other without sharing their info?
- Yes. Messages are relayed, so a member can be reachable without exposing a raw email address or phone number to the sender.
- How does pickup authorization work?
- When your church turns on check-in, staff record who may collect each child and who may not. The decision is made in the database as the child is released, so it reflects the records as they stand at that moment rather than when the screen was drawn. A deny is never overridable, and only an owner or admin can approve someone who simply is not on the list, with a note. To the person at the door, not on the list and denied look identical, so nobody learns another family's arrangements.
- Can we print a directory book?
- Yes. Staff can render a designed PDF book with a member edition and a watermarked staff edition, two trim sizes including a folded booklet, thumb tabs, guide words, and a name index. Members can opt out of the printed book separately from the directory itself, and a book goes stale on purpose if anyone opts out after it was rendered.
- Are pastoral care notes private?
- Care notes are encrypted field by field, every view is recorded in the audit log, and they are never sent to any AI feature or included in a privacy-request export.
- Can we import our existing member list?
- Staff can paste a CSV, or bring records across from Planning Center or Breeze. Every import is staged: duplicates are detected and proposed as merges, staff review the mapping, and nothing reaches the directory until they commit it.