Membership platform
Membership & Branch Management Platform
A white-label Flutter app for organisations that operate through a branch network.
- White-label
- Branch hierarchy
- Role-based permissions
One organisation, many branches, no shared system
Membership organisations that operate through a national branch network typically run each branch's records separately, on paper or in whatever spreadsheet a local officer maintains. There is no single place to see the member list for a branch, let alone the organisation, and updating a member's details means finding whoever holds that branch's copy.
One app, every branch, permissions that follow the hierarchy
We built a single Flutter application, deployable as separate white-label builds so different organisations can each run it under their own name and branding from one shared codebase. Branches form a tree, and every member and user record sits against the branch that owns it. Permissions are granted per action rather than by job title, and are resolved against a user's position in that branch hierarchy, so someone can be given authority in their own branch without it reaching upward into branches above it.
Engineering challenges
- Permission resolution across a branch tree
- A user's rights depend on where they sit relative to a branch, not just what role they hold. We built a resolver that walks the hierarchy from the branch in question back to the user's home branch, checking both branch-specific and organisation-wide rights before deciding what they can see or do.
Results
- One codebase, deployed as multiple white-label builds under separate names and branding
- Branch, member and user records unified into a single system in place of per-branch spreadsheets
- Permission checks resolve automatically against a user's position in the branch tree
Technologies
- Flutter
- Firebase
Have a system that looks something like this?
Tell us how the work happens today and we will tell you what a build like this one would take for you.
Discuss a similar project