MrClever
commented
4 years ago ChurchCRM has a concept of a single congregation associated with a single church in one location. Each congregation (church) would need a separate database and application. One solution might be to have a single domain, eg regionalchurch.example. Then create a separate application and database instance for each congregation under subdomains such as church1.regionalchurch.example, church2.regionalchurch.example.
However, as each congregation (church) has a completely separate database and application, there would be no automation between instances to share usernames etc. To implement something like that would be an exercise for the administrator, and would be non-trivial.
At this point in time ChurchCRM does not have any development plans to implement a multi-church/congregation model.
pabasa
github-actions[bot]
If you have the ChurchCRM software running, please file an issue using the Report an issue in the help menu.
On what page in the application did you find this issue?
On what type of server is this running? Dedicated / Shared hosting? Linux / Windows? Windows
What browser (and version) are you running? Version 80.0.3987.132 (Official Build) (64-bit)
What version of PHP is the server running? 7.1.1
What version of SQL Server are you running? 10.1.21-MariaDB
What version of ChurchCRM are you running? 4.0
So it is actually not a problem with the software but some challenges i am encountering. In my church we have multiple branches so we want user to login to the system through one software but different databases. for instance if the user is trying to login, the based on his branch we switch to the appropriate database. Any help will be greatly appreciated. thank You.