Branch-first Architecture
How Holy Resource manages multiple locations with isolation.
The Branch is the primary organizational unit in Holy Resource. Every piece of data—from member records to financial transactions—belongs to a specific branch.
Logical Isolation
Branches provide "hard" isolation between different datasets. This is essential for churches with multiple campuses or distinct ministries that need to keep their operations separate.
Key Characteristics
- Scoped Data: If you are viewing "North Campus", you will not see members from "South Campus" unless you switch branches.
- Independent Permissions: Staff can be assigned different roles on a branch-by-branch basis.
- Sync Scope: Sync and many operational actions are executed per active branch.
Why Isolation Matters
Branch isolation helps teams:
- avoid accidental cross-branch edits
- delegate safely to local leaders
- run independent workflows without mixing records
Admin Guidance
- Assign users only to branches they actively serve.
- Keep branch permissions on least-privilege principles.
- Review branch access whenever roles or responsibilities change.
What happens on branch switch
When a user switches branch, Holy Resource refreshes active context so screens and actions run under the selected branch permissions and data scope.
The Branch Lifecycle
Creation
An administrator creates a branch and assigns it a name and location.
Population
The branch is populated with its own specific members, families, and resources.
Reporting
Reports are generated at the branch level, providing clarity for campus-specific performance and giving.
When to use Branches
- Multiple Campuses: Separate physical locations.
- Independent Ministries: Such as a community center or a preschool that shares the church's license but needs separate records.
- Test Environments: Create a "Sandbox" branch to train staff without affecting your live data.
Last updated on