Enterprise hierarchy
Represent companies, divisions, departments, units, teams, or other formal organizational levels used for learning responsibility.
Corporate hierarchies
Deliver the right learning through the structures your organization actually uses.
BaseCamp can model enterprise, geographic, professional, position, reporting, domain, group, and community structures so learning teams can target catalogues, tracks, applications, approvals, calendars, communication, and reporting more accurately. Hierarchies provide context for learning without replacing the authoritative organizational systems that may already exist.
Selected schools, universities, and organizations working with White Mountain Technologies.
Overview
Learning becomes more relevant when organizational context is modeled clearly
A generic list of departments is rarely enough to target corporate learning. The same course may be mandatory for one position, recommended for another, restricted to a profession, localized for a region, offered only to a business unit, or approved through a particular management chain. External learners and vendor instructors may require a different structure again.
BaseCamp can represent multiple complementary views. An enterprise hierarchy can reflect companies, divisions, departments, units, or teams. A geographic hierarchy can represent countries, regions, branches, sites, or operational areas. Profession and specialization structures can group people by the work they perform. Position structures can represent role levels or job families. Management relationships can support approvals and relevant oversight.
Domains, groups, and communities add flexible targeting beyond formal hierarchy. A domain may separate major populations or areas of responsibility. A group may collect users for a program, cohort, project, or common requirement. A community may support ongoing exchange among people with shared expertise or interests. These structures should complement one another rather than duplicate identity or HR data without governance.
Connected process
Build hierarchy context from authoritative data to learning action
The purpose of hierarchy is not visualization alone; it is to improve eligibility, targeting, approval, communication, and analysis.
- 01
Identify authoritative structures
Determine which systems and owners define enterprise, geography, profession, position, management, external population, and organizational status.
- 02
Map learning relationships
Document which structures influence mandatory learning, catalogues, tracks, approvals, registration, communication, reporting, and cost responsibility.
- 03
Configure hierarchy and flexible groups
Create approved hierarchy levels, codes, relationships, domains, groups, communities, effective dates, and ownership.
- 04
Assign or synchronize people
Link learners, managers, instructors, vendors, and external populations through controlled integration or administration.
- 05
Target learning and communication
Use the structures to determine eligibility, recommendation, priority, approval, audience, calendar, content, and notifications.
- 06
Analyze coverage and maintain change
Review participation and progress by organizational context, synchronize changes, and preserve useful history without stale assignments.
Capabilities
Complementary structures for different learning decisions
No single hierarchy should be forced to represent every organizational relationship.
Geographic hierarchy
Organize countries, regions, branches, sites, locations, or areas of operation for localized learning and reporting.
Profession and specialization
Group users by disciplines, areas of expertise, qualifications, or professional development needs.
Position and role structures
Represent job families, grades, positions, responsibility levels, or workforce roles that influence development requirements.
Management relationships
Support manager or supervisor approval, oversight, reporting, escalation, and development follow-up where appropriate.
Domains, groups, and communities
Create flexible populations for programs, cohorts, projects, shared interests, access, communication, or collaborative learning.
Governance
Prevent hierarchy duplication, drift, and conflicting ownership
Hierarchy data can affect access and mandatory learning, so changes must be controlled and traceable.
Authoritative ownership
Specify which system and business owner controls each hierarchy, code, relationship, status, and effective date.
Integration boundaries
Decide what BaseCamp receives, what it maintains, how often it synchronizes, and how exceptions or rejected changes are handled.
Access implications
Review whether hierarchy assignment grants data visibility, approval authority, privileged content, or management reporting.
Historical continuity
Define effective dates, transfers, reorganizations, manager changes, closures, merges, and how past learning remains reportable.
Implementation readiness
Model only the structures that influence real learning decisions
A smaller governed hierarchy is more useful than a detailed organization chart with no defined operational purpose.
Inventory structures and sources
Identify enterprise, geography, profession, position, manager, external population, domain, group, and community data and owners.
Define learning use cases
For each structure, document the eligibility, approval, targeting, communication, access, reporting, or costing decision it supports.
Design codes and relationships
Agree stable identifiers, levels, effective dates, status, ownership, synchronization, exception handling, and history.
Test organizational change
Validate transfer, promotion, manager change, site change, reorganization, leave, exit, external re-entry, and historical reporting scenarios.
Govern ongoing maintenance
Monitor synchronization, unassigned users, stale groups, duplicate structures, unauthorized changes, and hierarchy-based access.
Operational value
More accurate learning audiences and more meaningful organizational insight
Well-designed hierarchies improve both the delivery of learning and the interpretation of its results.
Relevant targeting
Direct mandatory, recommended, elective, local, role-based, professional, or cohort learning to the intended population.
Clear approvals
Route participation and exceptions through the correct management or learning authority where required.
Better coverage analysis
Compare participation, progress, certification, provider activity, and cost across meaningful organizational structures.
Frequently asked questions
Questions about corporate hierarchies
Does BaseCamp replace the HR organizational structure?
Not necessarily. In many implementations, HR or identity systems remain authoritative and BaseCamp receives the structures and assignments needed for learning operations.
Can one person belong to multiple groups or communities?
Yes. Flexible groups and communities can support programs, cohorts, projects, interests, or expertise beyond formal organizational placement.
Can hierarchies control mandatory learning?
Yes. Enterprise, geography, profession, position, role, domain, or group assignments can contribute to eligibility and targeting rules.
Can manager relationships support approvals?
Yes. Where reliable management relationships are available, they can support registration approval, oversight, communication, or reporting.
How are reorganizations handled?
The implementation should define effective dates, synchronization, transfers, merges, closures, manager changes, and preservation of historical learning context.
Can hierarchy data affect access to sensitive information?
Yes, if configured. Any hierarchy-based visibility or authority should therefore be explicitly designed, tested, reviewed, and monitored.
Plan the next step
Model the organizational context that makes learning relevant.
Review your enterprise, geographic, professional, position, management, group, community, integration, and targeting requirements with WMT.