Why might a church elect not to synchronize Churchteams with their central database?
Some churches have chosen not to synchronize databases. They use Churchteams as a distinct tool for managing small groups and require each member in the church to login and create a Churchteams profile. This is especially useful for maximizing the placement features Churchteams offers. It definitely maximizes the use of the tool within the church. It’s easy for anyone to do, but it does require a well thought through plan for ongoing promotion.
Related Questions
- SQL Examiner detects that two tables are different after the database comparison and offers me to synchronize them though I changed only the order of columns. How can I avoid it?
- Why might a church elect not to synchronize GroupFinder with their central database?
- How does Churchteams interact with our church’s database?