Support
Support
How to get help with ChurchCRM: documentation, Discord, YouTube, GitHub issues, and community-driven support.
Support here is community-driven, not a paid help desk: active issue tracking, documentation, and a responsive volunteer community — not SLAs, phone support, or commercial guarantees. In practice, the community responds quickly and generously.
Where to get help
Read first
Documentation
Install guides, admin docs, and day-to-day user guides
Ask live
Discord
Real-time help from church staff and contributors who use ChurchCRM every day
See it done
YouTube
Tutorials, walkthroughs, and product updates on the official channel
Report & track
GitHub Issues
Search existing reports, then file a bug or feature request
How support works
Community-driven help, not a help desk
Stuck on a feature?
Check the documentation first, then ask on Discord or search GitHub Discussions.
Found a bug?
Check existing issues first, then file one using the Bug Reporting & Diagnostics Guide. Include your version, browser, and steps to reproduce. The in-app reporter (Support → Report an Issue) is usually the fastest path.
Have a feature request?
Open an issue explaining the problem it solves for your congregation. The community discusses whether it fits the project’s direction.
Security issue?
Email security@churchcrm.io directly — never post vulnerabilities publicly.