The structure of your church,
made operational.
Small groups, volunteer teams, leadership cohorts, recovery groups, missions teams — every ministry your church runs lives in one workspace. Members find a place to belong. Leaders manage their people without spreadsheets. Staff sees the whole organism at a glance.
The body has many parts. The software should know that.
A church isn't a list of members.
It's a network of ministries.
Every active member of a healthy church belongs to something specific. A Wednesday-night small group. The hospitality team. The men's recovery group. The student leadership cohort. The missions board. The choir. The first-impressions team. Each ministry has its own rhythm, its own leaders, its own way of communicating with the people inside it.
Most platforms treat “groups” as a single flat list and “volunteer teams” as a different flat list. That misses the truth that most ministries are both — the worship team is a volunteer team that also functions as a discipleship group, the recovery ministry has a leader cohort that meets separately from the open groups, the kids ministry has age-segmented teams that are also small groups for the workers.
Ministries is one workspace that holds the whole structure. A ministry is a first-class object with its own page, its own leadership, its own communication channels, and its own membership roster. Within each ministry, you can have groups (small groups, cohorts) and teams (volunteer schedules, roles). A person can belong to multiple ministries in multiple capacities — leading one group, serving on one team, attending one recovery cohort — and the system tracks all of it without making the staff reconcile spreadsheets.
Each ministry has its own page, its own leaders, its own rhythm.
A ministry record holds everything that ministry needs: its name and description, its assigned leaders, its meeting schedule, its public-facing page (so prospective members can find and join), its private communication channel, and its roster of current members. Open the worship ministry and see the worship team. Open the recovery ministry and see the cohorts inside it.
Leaders have scoped access to their own ministry — they can manage their members, schedule their meetings, and post to their channel without needing platform-wide admin permissions. Staff sees the full network. Members see the ministries they belong to.
- Per-ministry page with description, leaders, meeting cadence, and roster
- Scoped leader permissions — manage your ministry without platform admin access
- Joinable from the public church profile (or invite-only, per ministry)
- Built-in communication channel scoped to ministry membership
Small groups, cohorts, classes — the real units of community.
Inside a ministry, you can have any number of groups — a small group is a group, a recovery cohort is a group, a leadership class is a group, a missions team is a group. Each group has its own leader, its own meeting schedule, its own real-time chat thread, and its own roster.
When someone joins the men's ministry, they don't join “the men's ministry” — they join a specific group within it, the Tuesday-morning prayer breakfast or the Thursday-night cohort. That's how community actually forms. The ministry is the umbrella; the group is where people show up.
- Unlimited groups per ministry, each with its own leader and chat thread
- Member-facing browse and join flow, scoped to ministries that allow it
- Real-time group chat with leader moderation tools
- Per-group meeting schedule with attendance tracking
A serving slot isn't a separate database. It's a role inside a ministry.
When someone signs up to serve on the hospitality team, they're joining the hospitality ministry in a serving role. The volunteer scheduler uses the same ministry roster — assignments pull from the existing membership, conflicts surface across other ministries the person serves in, and the served-recently flag tracks burnout risk across the whole church, not just one team.
Volunteer roles can be open (anyone can sign up), invite-only (leader-curated), or background-check gated (children's, finance, pastoral care). Roles can require training before assignment, with the training tracked per person. When a member completes the training, they're eligible for the role automatically.
- Serving roles live inside the ministry the role serves
- Open / invite-only / background-check-gated role types
- Required-training prerequisites tracked per person
- Cross-ministry conflict and burnout detection out of the box
The depth that holds a real church together
Beyond the roster.
Group finder
The public-facing browse experience for prospective members. Filter by ministry, day of week, meeting style (in-person, hybrid, online), life stage, or location. Join with one tap.
Leader dashboards
Every ministry leader gets their own dashboard: attendance trends, members who haven't shown up recently, requests for follow-up, upcoming meetings, and pending volunteer slots that need filling.
Cross-ministry analytics
The executive view: how many people are in at least one ministry, how many are leading, how many ministries the average member belongs to, which ministries are growing, which are shrinking. Health metrics for the body.
Curriculum + meeting materials
Attach curriculum, lesson plans, study guides, and meeting materials to a group or a ministry. Leaders pull what they need before the meeting. Members access materials they've been granted.
Attendance tracking
Per-meeting attendance — taken by the leader in 30 seconds, surfaced as a member-engagement metric in the CRM. The Wednesday-night attender who missed three weeks in a row gets a follow-up flag.
Scoped permissions
A small-group leader can manage their group without seeing the rest of the church's data. A ministry leader can manage their ministry. The Ministry Leader and Leader / Elder system roles exist for exactly this — recognized leadership without platform-wide admin access.
What a connected church actually looks like, operationally.
A new visitor lands on the church's public profile and browses the ministries. She picks the women's ministry, finds a Thursday-morning group, and joins. The group leader gets a notification and welcomes her in the group chat by Thursday afternoon. By the third week, she's signed up to help with the meal team, which is a serving role inside the hospitality ministry. That role required a brief background acknowledgment and a fifteen-minute orientation video — both completed in the app — before she could be scheduled.
By month three, her membership profile shows two ministries, one serving role, ten weeks of group attendance, and a follow-up note from the women's ministry leader. The lead pastor never had to manage any of this directly. The women's ministry leader did her job with the tools scoped to her ministry. The volunteer coordinator scheduled the meal team without ever opening a spreadsheet.
That's a connected church running operationally — not because of one heroic admin, but because the structure is built into the tool.