Multi-chapter management software

Admin roles and data isolation work at three levels:

• Organization level, national or international
• Parent chapter level: region, district, state, county, province, council, or country
• Local chapter level

Parent-level admins automatically inherit admin rights over every chapter beneath them, so a state admin manages all county chapters without being granted each one separately.

Below the local chapter, your organization defines its own unit types, such as units, patrols, troops, teams, or service units. Units nest inside other units to any depth, so a chapter with several sub-units, each holding its own smaller groups, maps directly instead of being flattened.

Every structural label is text your organization controls. "Local group" becomes chapter, branch, section, council, or district, in your own language, across the whole platform.

Chapters group into regions for filtering, reporting, and delegation. An international organization runs country chapters at the parent level, with city chapters underneath, which is how a network headquartered in one country coordinates chapters across several others.

Cross-chapter projects and working groups that do not fit the geographic model exist as initiative centers alongside the location-based ones, with the same admin roles and tools.

When your members are organizations rather than individuals, each member entity manages its own people, names a primary financial contact, and pays as one entity. If that entity lapses, all its people lose access together.

Each level carries the same role catalog:

• Chapter admin, with full access inside the chapter
• HR, plus a read-only HR assistant for people who need to see profiles but not edit them
• Financial manager, for that chapter's payments and fees
• Communication manager, for moderation and newsletters
• Event manager, for that chapter's events and attendees

Role names are yours to define and map onto these permission levels, so "chapter president" or "council treasurer" behaves exactly as your governance documents describe.

A chapter operates as an organization in itself:

• Manages its own members and approves its own registration requests
• Runs its own events, free or ticketed
• Uploads and shares its own files
• Sends newsletters to its own people only
• Maintains its own contacts database
• Records cash payments and marks fees as paid
• Views its own analytics and financials

A local financial officer sees payment data for their own chapter. A regional admin sees every chapter in their region. National admins see the whole network. Nobody browses data belonging to a chapter they do not administer.

Chapters can see each other's posts, events, and member lists, or stay fully encapsulated. Your organization sets this once and changes it as the network matures.

Profiles of children and minors are visible only within their own chapter. Browsing minors across the organization is possible only for national admins.

Each chapter that has its own legal entity connects its own Stripe account. Donations, local membership fees, and event ticket revenue flow straight into that chapter's bank account. The national level grants or revokes the Stripe integration per chapter.

Organizations charging at two levels have two options:

• Two separate charges: the national fee to the national account, the local fee to the chapter's own account
• One payment split between national and local at a set percentage

Chapters set their own local fee amounts, so a chapter with higher local costs charges accordingly without a separate system.

A chapter that is not a separate legal entity uses the parent organization's payment setup. Both models coexist inside the same organization, so a network does not have to wait for every chapter to incorporate before going live.

Each chapter configures its own IBAN for bank transfers, in Native, EUR, USD, or CHF account types. Local admins record cash payments and mark fees as paid, and bank transfers reconcile through unique payment identifiers.

Headquarters sees total revenue, recurring revenue, and donations per chapter, alongside membership growth and signups. This is how a national office identifies which chapters are growing and which have gone dormant, without asking each one for a report.

Every member has one primary home chapter. Members who split time between locations, or who hold a role in more than one group, can also belong to secondary chapters, each with its own permission level.

New members choose their chapter from an auto-populated dropdown on the registration form. Both local and national admins receive a notification with a direct link to the new profile, so approval does not depend on someone checking a shared inbox.

A member submits a transfer request from their own profile, naming the chapter they want to move to. A local or organization admin approves or denies it, and the member's payment, event, and role history moves with them intact.

Chapters with limited capacity enable a waitlist. New applicants and incoming transfers join the queue with priority tiers, and an admin approves entries individually or in bulk when space opens.

The member directory filters by chapter, alongside fee status, account status, user type, interest, industry, and profession. Chapter-scoped admins see the same filters restricted to their own people, and every export is logged.

The map of all chapters embeds into any external website through an iframe, with no Orgo branding, and updates automatically as chapters are added or edited. Visitors browse the network without logging in.

Each chapter edits its own map pin, contact details, description, website, and social links. The national team sets up the map once and stops maintaining it.

Visitor location detection surfaces the nearest chapter, and the map feeds directly into registration: a visitor picks a chapter and registers into it in the same flow.

Each chapter stores its name, address, and geographic coordinates. The same record drives the map, member assignment, and public display, so an address is corrected once.

A group can auto-populate from a role, for example every chapter president across the network. When someone gains or loses the role, their group membership updates automatically, so the leadership channel is never out of date.

Groups sit above local chapters, so every chapter in a state or region shares one discussion space. This is where a chapter short on volunteers for an event asks neighbouring chapters, rather than escalating to the national office.

An organizational chart generates itself from role data and stays browsable by any member, so finding every chapter president or regional treasurer takes one search instead of an email thread.

Local communication managers send newsletters and campaigns to their own chapter's members and contacts only. National campaigns target all members, a specific chapter, a region, a role-based group, or a saved segment.

National admins see new members, active and inactive members, paying members, signups and exits, and age distribution, filterable by period and by chapter. Chapter admins see the same dashboards restricted to their own chapter's data.