Units, chapters, and groups
All four sit on the same underlying structure in Orgo, which is why they share features like member roles and a name, but they behave differently:
The practical difference: a unit describes where someone sits in the org chart, a group describes what they are working on.
Units and chapters both nest, and they are separate trees. Chapters nest into each other to any depth (national, region, district, branch), and units nest inside one chapter along your chain of unit types. A unit never spans two chapters, and a unit is never the parent of a chapter.
Before you start
Unit types
A unit type is the template for a layer of your structure. Define them once at Settings → Modules → Groups & Teams → Unit Types, then create units of that type inside each chapter.
Creating, editing, and deleting unit types is restricted to the Orgo administrator. Delete a type only after nothing uses it.
Within local center is the switch that decides whether a type shows up as a chapter tab and in the chapter row menu. A type without it produces units that are not tied to any chapter, so only tenant-level admins can manage them.
Working with units
The unit list
In the chapters list, the … row menu has one entry per local unit type, shown to members of that chapter and to organization-wide HR managers. Each opens a list of every unit of that type in the chapter. The heading is the type’s plural name. Chapter HR managers get an active / archived filter. Chapter admins get an add button naming the type, and a pencil on each row. Each row shows the member type badge or logo, the unit name linking to its members, the member count, and the parent unit name (with an archived tag if the parent is closed). Clicking a row slides in the unit form:
Deleting a unit asks for confirmation and removes its role assignments with it.
The segmented board
The chapter header carries a tab named after your local unit types (for example Patrols), and the chapter’s shortcut card has the same link. It opens the drag-and-drop board for the whole chapter. Chapter HR managers see every unit; a unit admin sees only the units they run. When your types nest, the board renders as columns: one per parent unit, with its child units stacked inside. Any child unit that has not been given a parent is collected in a final Unassigned column. When the type you are looking at has no parent type, the board is flat instead: one section per unit. Chapter HR managers can drag a member from one unit to another, use Add member to search and place someone, create a unit, set each member’s role, and mark a member as Admin of their unit. Editing or deleting a unit takes chapter admin rights. A unit admin can add and remove members in their own units only. Add member searches active members only, so a suspended or inactive member cannot be placed. If a placement fails, the reason shows under the search box: “This member already has this role in this unit”, or “You do not have permission to add members to this unit”. To create a unit, use the dashed add tile on the board. On a flat board (no parent unit type) it sits above the units and shows even when the chapter has no units yet. It is labelled with the unit type’s name, or with all the local type names separated by a slash when there are several; with several types, clicking it asks you to pick one, and with one type it opens the form straight away. A new unit is created in the chapter whose board you are on.From the chapters list
When units are enabled, each chapter row in the chapters list grows a chevron. Expanding it loads that chapter’s whole unit tree inline, indented by depth, showing each unit’s type, member type color, and member count. A unit name in that tree is a link only if you can open it. You can when you hold chapter HR manager rights over the chapter, or you are an admin of that unit or one above it, or you hold a role on that unit type (or any type above it in the parent chain).Chapter admin rights reach the units of the holder’s own chapter only, however deeply those units are nested inside it. They do not reach units belonging to a chapter below yours in the chapter tree, even one directly below. To administer a branch’s units you need a parent-chapter permission, which is the permission family that travels down the chapter tree.
Who can do what
Chapters and role groups can never be created or edited through the unit screens even by tenant admins; they have their own flows.
Common questions
How deep can units nest?
How deep can units nest?
As deep as your chain of unit types. Each type points at one parent type, and units of a type can only sit under units of that parent type. The chapters list renders the resulting tree at whatever depth it finds.
A member should be in two units.
A member should be in two units.
Unit membership is a role assignment, so a member can hold roles in more than one unit at the same time. Dragging on the segmented board moves them; adding them from a second unit’s Add member leaves both.
Why does no unit tab appear on my chapter?
Why does no unit tab appear on my chapter?
Three things must all be true: Enable Organizational Units is on, at least one unit type has Within local center ticked, and you hold chapter HR manager rights over the chapter.
What happens to members when a unit is archived?
What happens to members when a unit is archived?
Archiving sets the unit’s status to closed and records an end date. It stays visible under the archived filter and keeps its history; it just stops appearing in the active list and in the chapter’s unit tree.
Should I use a unit or a group for a committee?
Should I use a unit or a group for a committee?
A unit if the committee is a permanent part of the chapter’s structure and you want it in the org chart and in fee scoping. A private group if it is a working space people join for a project.
Related
- Local Centers - the chapters that units live inside
- Groups Overview - all group types and when to use each
- Role Groups - membership defined by a query instead of an assignment
- Member Transfers - what happens to assignments when a member changes chapter
- Permissions - how the local roles are evaluated

