There are many different types of organizations possible on our platform. Read this article to understand their abilities and how they all work together on our platform.
Overview of the types of organizations on the platform
Level | What it represents | Belongs to |
Partner | The top-level tier for benefit providers to build and offer benefits on the platform | not applicable |
Organization Group (optional) | A parent company holding multiple organizations | One partner |
Organization | A single employer, company, or organization that offers benefits to members | One partner or (optionally) one organization group |
Division (optional) | A sub-unit of an organization | One managing organization |
Member | An enrolled individual | One organization or one division |
Partners
A partner is the highest-level group on the platform. It’s who signs a statement of work with the platform provider and designs and builds benefits, including choosing the branding of the benefit and the technical configuration of the benefit (API, SSO). A partner admin can perform all actions that an affiliated organization group admin, organization admin, or division admin can.
Platform hierarchy
Partner → Organization Group → Organization → Division → Member
Organization groups
An organization group, or org group, is an optional group structure that sits above individual organizations. It allows a partner, whether a holding company or a parent corporation, to organize multiple employer organizations under a shared umbrella. Organization groups enable someone who oversees multiple related employer organizations to see and administer them as a group.
Platform hierarchy
Partner → Organization Group → Organization → Division → Member
Why organization groups
Here's why you might set up an organization group:
You need a way to organize multiple employer organizations under a shared umbrella.
Key rules
Each organization belongs to at most one org group, or remain ungrouped.
Org groups are lightweight administrative containers, not sub-partners. They don't own banking, identity, or their own partner configuration.
Partners can have both org groups and direct (ungrouped) organizations simultaneously — the structures aren't mutually exclusive.
An organization group comes with a dedicated persona, an org group admin, who gets read-only visibility into every organization and member inside their assigned group (and nothing outside it). This lets a partner delegate day-to-day oversight without handing out partner-wide access.
Organizations
An organization is a platform group that most commonly represents an employer. It’s where benefit templates are assigned, where members are enrolled, and where day-to-day administration happens.
Platform hierarchy
Partner → Organization Group → Organization → Division → Member
Why organizations
Here's why you might set up an organization:
You want to design and issue benefits to individuals who are part of an organization.
Key rules
An individual must be a member of an organization before they can be enrolled in any of its benefit plans.
Each organization has its own benefits (HSA, FSA, HRA, lifestyle accounts, etc.) configured under a benefits program.
Organization admins manage the org's members, benefits, contributions, reports, and banking.
An organization belongs to exactly one partner.
An organization can optionally belong to one org group or remain ungrouped.
A member stays in an organization until removed.
Once enrolled, a member's organization membership persists even if employment ends (especially for HSAs, which belong to the individual, not the employer).
Divisions
A division sits at one level below its parent (aka managing) organization. Each division has its own list of members, its own benefit plans, and its own banking, but it shares the parent organization’s payment-processor and card-program identity. Each division belongs to exactly one parent organization.
Platform hierarchy
Partner → Organization Group → Organization → Division → Member
Why divisions
Here's why you might set up a division:
A managing organization has a set of benefits, and each division has its own different, separate set of benefits.
A managing organization shares a card program with their divisions but wants separate banking for each.
Example
If a managing organization offers a benefit that a division doesn't want to offer, the division can opt out. And if a division wants to offer a benefit that the managing organization doesn't have, the division can have a standalone benefit offering
Divisions have their own:
Members, assigned to the division rather than the parent org.
Benefits, with a dedicated bank account and funding.
Admins, who manage the division's members, enrollment, and reporting.
Divisions share their parent organization’s:
Payment processor and card program. A member's card keeps working even if they move between divisions, and benefits stay unified under a single program.
Key rules
Each division belongs to exactly one parent organization.
Divisions are optional.
Partner admins can create, manage, and view divisions across all organizations.
Organization group admins can view divisions in read-only mode.
Organization admins can create and manage divisions within their own organization via a Divisions tab.
Division admins are simply organization admins scoped to a single division — they can manage members, run enrollment, and access reporting.
Members
An individual enrolled in benefits.
Platform hierarchy
Partner → Organization Group → Organization → Division → Member
Why members
Here’s why you might add a member:
You need to enroll someone in benefits!