​

Church networks work together with clear boundaries

The new Church Network workspace connects invited churches around church plants, campaigns, care coordination, safeguarding status, pulpit supply, filings, and shared resources while preserving each church’s local ownership.

​

Practical support for church plants

Parent and plant churches can work through an editable launch checklist, bounded support reports, planter-controlled wellbeing signals, and a shared support taper ledger. Planned, actual, and variance totals make the agreement visible without introducing a new payment flow.

​

Shared ministry without shared databases

Networks can publish events and prayer campaigns, coordinate dated pulpit requests with vetted profiles and monthly limits, and collect reviewed filing submissions with source-aware roll-ups. Care transfers require member consent, share only a bounded context, and can be withdrawn before acceptance. A separately consented and permissioned discipline/restoration envelope can share only the current status from an assigned protected case; its narrative and sealed details remain at the source church. Name-blind benevolence checks return a safe coordination reference instead of revealing identity or case notes. Expiring safe-to-serve passports share current claims but never the raw background report. Passport claims are also checked against the issuing church’s current local clearance record. Network governance remains with owner, parent, and regional coordinators. Only churches designated as plants can receive plant checklists and support records, while member churches retain control of their own submissions.

​

Resources that keep their history

Churches can publish ministry resources and templates with authorship, versions, licenses, usage guidance, and review marks. Forked curricula and other teaching assets keep their source lineage, while members can read published resources and send field feedback from the mobile Church Network hub. Read the Church Networks guide for setup, daily workflows, permissions, and privacy boundaries.