Multi-branch churches have a specific, structural problem: leadership wants one view across every location, while each branch wants to run its own week without waiting on head office. Most software picks one of those needs and gets the other wrong.
We built TheRehoboth's multi-branch support around a simple rule — data rolls up, control doesn't. Attendance, giving and events aggregate automatically so leadership can see the whole church at a glance, but each branch manages its own members, its own service schedule and its own team, without needing permission from a central admin for every decision.
The harder engineering problem wasn't the aggregation — that's a query. It was making sure a branch pastor never has to think about the other four branches to do their own job, while a senior pastor never has to open five separate accounts to see how the church as a whole is doing.
That translated into concrete data-model decisions early on. Members belong to a branch, not to the church as an abstract whole, so a branch administrator's list of "my members" is genuinely scoped and fast, not filtered out of a much larger shared table on every screen. Giving records carry a branch tag that rolls up for the finance view at the top, but a branch's own giving report never has to load or reason about transactions from a location three cities away. Small decisions like that compound — the difference between a dashboard that feels instant and one that feels like it's straining under five branches' worth of data.
Permissions were the other place this showed up. A branch pastor can invite their own volunteers and assign roles within their branch without a support ticket to head office, but they can't see or edit another branch's member list, even by accident — the boundary is enforced at the data layer, not just hidden by the interface. That matters more than it sounds: a UI restriction can be worked around by a curious user poking at the network tab; a data-layer boundary can't.
Getting that balance right is why multi-branch churches can adopt TheRehoboth without a structural fight about who owns the data — because, in a real sense, nobody has to give up ownership to get visibility. Head office gets the whole-church picture it needs for planning and reporting. Every branch keeps running its own week exactly the way it always has, just without the spreadsheet.
