Community & Support

A Community of Volunteers

ChurchCRM isn’t made by a company. It’s made by thousands of volunteers around the world who share a conviction: that every church deserves access to high-quality management tools.

Our community includes:

  • Software developers — Building features, fixing bugs, improving performance
  • Church administrators & pastors — Using ChurchCRM and contributing feedback
  • Translators — Bringing ChurchCRM to 49 languages and cultures
  • Testers & QA specialists — Finding bugs before they reach churches
  • Documentation writers — Creating guides and tutorials
  • Designers — Improving the user interface and user experience
  • Community helpers — Answering questions and supporting fellow users

You don’t need to be a professional software engineer to contribute. Every role matters. A translator adding ChurchCRM to a new language opens the door for churches that couldn’t use it before. A tester finding a bug before release saves congregations from losing data. A community helper answering a question on Discord saves someone hours of frustration.

How to Participate

For Developers

Contribute code, fix bugs, build features, or create community plugins:

For Translators

Translate ChurchCRM into your language or help maintain existing translations:

  • Join: POEditor project for ChurchCRM
  • No Git required — translate directly in the browser
  • Impact: Open ChurchCRM to churches in your language who couldn’t use it before

For Writers & Documentation Contributors

Improve guides, write tutorials, create blog posts, share church testimonials:

For Testers & QA Specialists

Test new releases, validate features, report bugs before they affect churches:

For Designers & Creative Contributors

Improve the UI/UX, create marketing graphics, design social media content:

  • Design feedback: Open issues with the design label on GitHub
  • Social graphics: Share ideas on Discord #design channel
  • Brand assets: Help maintain ChurchCRM’s visual identity

For Community Helpers

Answer questions, support other users, welcome newcomers:

For Church Users

Test features in your congregation, share feedback, report what you need:

  • Try the live demo: churchcrm.io/demo.html
  • Provide feedback: Tell the community what features would help your church
  • Report bugs: GitHub Issues
  • Share your story: Tell us how ChurchCRM helps your congregation

Where Community Happens

Discord — Real-Time Community

Our primary community space is Discord. This is where:

  • People ask questions and get real-time help
  • Developers discuss features and architecture
  • Translators coordinate language work
  • Contributors introduce themselves
  • The community celebrates wins and supports each other

Why Discord? It’s free, it’s where developers and open-source communities already gather, and it provides real-time conversation that helps people feel connected to the project.

GitHub — Code & Issues

All code, bugs, and features live on GitHub:

  • Issues: Report bugs or request features
  • Discussions: Ask questions and have detailed conversations
  • Pull Requests: Submit code contributions
  • Docs: In-depth technical documentation for contributors and administrators

Documentation Site

docs.churchcrm.io is where churches go to learn how to use ChurchCRM:

  • User guides for every feature
  • Administrator documentation
  • Troubleshooting guides
  • Tutorials for common workflows
  • Built on Markdown files in GitHub

Blog

churchcrm.io/blog shares:

  • Feature announcements
  • Release notes and updates
  • Church stories and testimonials
  • Tutorials and tips
  • Community spotlights

Email

For security concerns or private matters:

Support Ecosystem

ChurchCRM’s support ecosystem is built on the community, not on a paid support team. This is intentional — it keeps the software free and ensures that people who use ChurchCRM are the ones who understand it best.

Getting Help

I’m trying to use a feature and I’m stuck:

I found a bug:

I have a feature request:

  • Open an issue on GitHub
  • Explain the problem it solves for your congregation
  • The community will discuss whether it fits the project’s direction

I want to report a security issue:

What Support Looks Like

We provide:

  • Community-driven technical support through Discord and GitHub
  • Active issue tracking and bug fixes
  • Documentation and tutorials
  • Feature improvements based on community feedback
  • Regular releases with updates and security patches
  • A welcoming, responsive community of volunteers

We don’t provide:

  • SLA-based commercial support
  • Dedicated support contracts
  • Phone support or ticketed support queues
  • Commercial guarantees on uptime or performance
  • Paid consulting or implementation services

Why? Because ChurchCRM is built by volunteers, not by a company with a support department. The tradeoff is that you get free software with community support, not a commercial support guarantee.

This works. Churches that value the ChurchCRM mission understand that community support is part of choosing free software. They’re used to helping each other, and the community responds quickly and generously.

Code of Conduct

All members of the ChurchCRM community — whether on Discord, GitHub, or anywhere else — are expected to follow our Code of Conduct. We welcome people from all backgrounds and are committed to creating a respectful, inclusive community.

Join Us

ChurchCRM needs people like you. Whether you’re:

  • A developer who wants to build features used by churches around the world
  • A translator who wants to bring ChurchCRM to your language
  • A writer who wants to share church stories and knowledge
  • A church administrator who wants to improve the tools your congregation uses
  • Someone who simply cares about helping churches access better tools

There’s a place for you. Start here:

  1. Join Discord — say hello and introduce yourself
  2. Browse GitHub Issues — find work that matches your skills
  3. Read the Contributing Guide — understand the contribution process
  4. Try the Demo — see what ChurchCRM can do

The community is waiting to welcome you.

Leadership & Decision Making

ChurchCRM’s direction is guided by:

  • Core maintainers — A small group of long-term contributors who oversee architecture and releases
  • Contributors — Developers, translators, designers, and writers who improve the project
  • Users — Churches and individuals who use ChurchCRM and provide feedback
  • Community discussions — Major decisions are discussed openly on Discord and GitHub

This isn’t a top-down hierarchy. It’s a community working together toward a shared mission. Sometimes discussions take longer because we’re listening to everyone’s voice. But the result is software that truly serves the Church.

History & Evolution

ChurchCRM has been around in various forms since the 1990s (as ChurchInfo). It’s evolved because the community kept investing in it — fixing bugs, adding features, translating it, documenting it, and supporting fellow users.

That’s still how it works today. The project only improves because volunteers choose to make it better.

Questions? Want to get involved? Join us on Discord →

Home
Help Demo