Church Connect

Overview

A multi-tenant church management platform built around a no-code Organisation Builder: an admin models their own governance hierarchy — District, Area, Region, National, International, or whatever they call those layers — and every module scopes itself to that structure.

The problem

The established church platforms all assume a flat, single-church tenant. A denomination with districts, regions and a national office has to either flatten itself to fit the software or run a separate account per assembly and reconcile by spreadsheet. Neither of those is what the organisation actually looks like, and the mismatch shows up in every report it tries to produce.

The approach

1. Built the Organisation Builder first rather than last. Hierarchy depth is unlimited and drag-and-drop, and each tenant renames the layers in its own vocabulary — Diocese, Circuit, Parish, Shepherd Group — so the software speaks the denomination's language instead of imposing one.
2. Scoped role-based access to the hierarchy rather than to individual churches. A role granted at Region automatically covers every church beneath it, so appointing an overseer is one assignment instead of forty manual grants.
3. Modelled all twenty modules in the schema up front and sequenced the build, so Phase 1 ships tenancy, membership, families and roles without the later modules forcing a migration.
4. Shipped denomination templates in the setup wizard — pick a preset structure and role set, or start blank — because the blank-canvas version of a configurable product is unusable on day one.
5. Kept the independent single-church case first-class: one org unit, no hierarchy to configure, none of the multi-level overhead.