Events and RSVPs
Publish upcoming events once and let members respond from the member app.
Church software for the week between Sundays
Help staff publish what is happening—and give members one place to respond, serve, connect, and request care. Members use the app free; churches fund the subscription.
For pastors, administrators, and operations leaders evaluating church software.
Capabilities
ChurchHearth connects Church Admin publishing with a member experience for participation—not an open social network or a giving processor.
Publish upcoming events once and let members respond from the member app.
Help people find their group and stay connected beyond Sunday—without an open social feed.
Share opportunities, fill open roles, and make it easier for members to step in.
A private path for prayer or practical support requests to authorized church staff—not emergency response.
Keep staff-published church updates easy to find throughout the week.
Daily and formation surfaces help members engage Scripture and church-set rhythms.
Who it serves
One product relationship: Church Admin for leaders, the member experience for the congregation.
Church staff
Church members
Core workflow
A practical rhythm for how information moves from staff to members during the week.
Step 1
Leaders use Church Admin for events, announcements, groups, serving, and care workflows.
Step 2
People open the member experience to see what matters for their church.
Step 3
RSVP, serve, stay with a group, follow updates, or request care through the church.
Step 4
Leaders see responses and care activity with role-appropriate access.
Trust and privacy
We describe live controls factually and do not invent certifications, uptime SLAs, or completed legal effectiveness.
Each church’s people, events, groups, care requests, and communications belong to that church’s protected space.
Permissions are enforced on the server for records—not only in the interface.
Prayer and pastoral care information uses tighter access than ordinary community content.
Published Terms and Privacy pages exist for the pilot framing; commercial effectiveness and enforcement flags remain subject to counsel review.
Implementation
Churches start with identity setup, staff roles, and publishing the week—not a claim that every legacy system is replaced overnight.
Typical first steps: confirm church identity, invite staff, publish a small set of events and groups, and invite members. Migration scope and timelines are agreed during implementation planning.
Packages
Working package names differentiate capacity, campuses, onboarding effort, and support—not artificial withholding of core pastoral features.
Package details and public pricing remain provisional.
Package details and public pricing remain provisional.
Package details and public pricing remain provisional.
Package details and public pricing remain provisional.
FAQ
A short set of questions buyers ask first. More detail lives on the FAQ page.
Request a walkthrough of Church Admin and the member experience. Availability, package fit, and next steps are discussed directly—no automatic checkout.
Already part of a church on ChurchHearth?
Sign in