Organization Visibility
Control which member types can see which organizations in the hierarchy — and whether visibility cascades to sub-orgs.
The Organization Visibility page is found under MEMBERS → Org Visibility in the admin sidebar. This page lets you configure, for each member type, which organizations in your hierarchy are visible. Combined with the member type visibility settings, this gives you fine-grained control over what your members can discover about the structure of your organization.
How Visibility Works
Organization visibility is configured as a matrix of member type vs. org component type. For each combination, you set a visibility level and optionally enable sub-org inclusion. This determines what a member of that type can see when browsing the organization directory.
For example, you might configure:
- Full Members can see All Chapters across the organization
- Prospects can only see their Local Chapter
- Honorary Members can see All organizations at every level
Visibility Levels
Each row in the table has a visibility dropdown with three options:
- All — the member can see every organization of this component type across the entire hierarchy. A Full Member with "All" visibility for Chapters can browse every chapter in the directory.
- Hierarchy — the member can see organizations of this type that are in their direct hierarchical path — their own org, its parent, its grandparent, and any siblings. They cannot see orgs in other branches of the tree.
- Local — the member can only see the organization of this type that they directly belong to (or that is directly above them in the tree). Maximum restriction.
Include Sub-Orgs Toggle
The Include Sub-Orgs toggle extends visibility downward through the tree. When enabled, if a member can see an organization, they can also see all organizations nested beneath it — regardless of whether those child orgs are of a different component type.
For example, if a Full Member has "All" visibility for Regions with sub-orgs enabled, they can see all regions and all chapters within those regions. Without the toggle, they'd see the regions but would need a separate visibility rule for chapters.
For most organizations, enabling "Include Sub-Orgs" on the root or container component types is the simplest approach. This means you only need to configure visibility at the highest level, and everything below it inherits automatically.
Interaction with Member Type Visibility
Organization visibility works alongside the visibility setting on Member Types. The two systems complement each other:
- Member Type Visibility controls whether a member appears in searches and the directory to other members
- Organization Visibility controls which organizations a member can browse and discover
Both must allow access for a member to see another member in a different org. If a Full Member has "All" org visibility for chapters but the target member's type has "Local" member visibility, the Full Member still won't see that person unless they share an org.
Admins are not affected by organization visibility restrictions. Any member with admin access (Club, Org, or Local level) can see all organizations within their admin scope, regardless of what their member type's visibility settings would normally allow.