Qumuna organizational units explained

Short answer: Organizational units represent established groups inside a Qumuna community, such as buildings, chapters, teams, or departments. They can be linked to community structures so access and organization reflect real membership without becoming a separate identity system.

Represent the groups that already exist

Administrators and moderators with the organizational-units grant can create community-scoped units and link them to sub-communities or other supported entities. Clear unit names help leaders organize a complex community without relying on private spreadsheets or labels hidden in individual accounts.

Use unit-members-only mode deliberately

A sub-community can be configured so linked-unit membership defines its eligible roster. This is a sub-community-wide mode, not a casual per-link audience toggle. Enabling it may identify or remove current outsiders and can require explicit confirmation before the restriction changes.

Know what units do not replace

Organizational units are not a standalone human-resources directory, an external identity provider, or an automatic synchronization service. Availability depends on the community plan and configuration, public communities without units cannot use unit-only linking, and names cannot collide with unlinked sub-communities.

Related resources

• Qumuna sub-communities explained
• Qumuna roles and permissions explained

Next step

List the real groups that affect access, remove duplicates, and test one unit-to-sub-community link with representative members before enabling a restriction. Verify current plan availability.