In all honesty, I have one client on Churchteams and I’ve been trying now and then to coax them off for a while and I think I’m getting close. I absolutely hate the way passwords and login work on the platform (all their small group leaders share a password, all the admins share another password, so on and so forth) and I think it’s a major liability in countries that have data protection laws because it doesn’t meet the unique username+password=one individual person standard. I was looking through the settings but I didn’t see anything there to enable unique login on a per-user basis the last time I was inside Churchteams. For giggles, I’ll pop into it now with that shared admin password… looking at it right now, It’s still a single password for all admins, one for all community leaders, one for all overseers, one for all cell group leaders, etc.
Now all that being said, aside from the interface being somewhat cryptic (even as an IT expert I’m not sure how to use the “communicate” function, there’s no way the 65 year old church admin will figure it out even though she’s a Mailchimp pro), it is otherwise a serviceable platform that I’m largely okay with. One area that all the ChMS’s need to get on board with is Zapier and/or Microsoft Flow integration. Churches need easy ways to integrate their data across platforms (especially for easily getting email addresses plunked down into newsletter platforms or moving donations on over into accounting suites). I’d also be interested, and this isn’t nearly as critical, in seeing a Wordpress plugin so that churches using it don’t need to fuss with iframes because I’ve seen Churchteams iframes flip out sometimes on Wordpress when there was a Redis cache.