Every customer institution is divided into org units — usually a tree of colleges and departments. Org units determine which faculty roll up to which leadership view, who gets which notifications, and which subset of data a staff member is allowed to see.

The hierarchy

• Customer — the institution itself. Top of the tree.
• College / school — middle layer.
• Department — leaf nodes. Faculty are usually mapped here.

A faculty member can belong to multiple units when they hold joint or cross-listed appointments.

How scope cascades

When you select a parent unit (for example, a college) in any scoped view, its sub-units are included automatically. Deselecting a parent removes its sub-units from the selection but they remain individually controllable. This is true for notification scope, leadership filters, and analytics roll-ups.

"Available to" in matches

Many opportunities specify the eligible institution types or geographic scope. The matching engine treats those as eligibility signals — they show on a match as a qualitative badge so the reader can see at a glance whether the opportunity is open to them.

Who manages org units

Institution admins manage the org tree from Clubhouse. Converge admins can edit any customer's tree when acting as them.