Visitors know what to do next.
The public site carries service times, forms, events, ministries, and contact details from the same setup staff uses.
How it works
Set up the church once. Use it everywhere.
My Church Group ties together the public website, browser login, staff tools, groups, signups, files, and app-safe links so the work doesn't scatter across separate systems.
Launch flow
Four pieces that make the site and app feel connected
- 1
Church record
Start with one church record.
Name, location, web address, service details, staff access, and basic settings become the source for the website and member tools.
- 2
Public website
Publish pages people actually need.
Visitors find service times, plan-a-visit forms, events, ministries, files, and contact paths without digging through stale announcements.
- 3
Staff work
Move staff work into the browser.
Staff invite leaders, review join requests, update groups, publish changes, and answer support without waiting for the mobile app.
- 4
Member access
Send links that keep working.
Church links open in the installed app when possible and fall back to the website on desktop or before someone installs the app.
What changes
Fewer scattered tools, clearer next steps
Members can use a desktop or phone.
Groups, files, signups, and church links have a browser path before the native app becomes the main habit.
Staff have fewer places to check.
Approvals, groups, website edits, billing, people, support, and files sit in one readable workspace.
Start with the first thing your church needs fixed.
If the website is stale, start there. If groups are scattered, start with member access. If you want help choosing, ask for guided onboarding.
- Self-serve setup works well when you already know the website, staff list, and first groups.
- Guided onboarding is better when you want help deciding what should go live first.
- Members can still use web links while your church rolls out the app.
- Staff can keep working from a laptop when a phone is not the right tool.