Planning's Organizational Hierarchy is meant to provide structure to both content and users. This structure is maintained locally within the Planning application and is not connected to the Campus Labs Core Data organizational structure.
In many cases, institutions may need to change their respective Organizational Hierarchy for strategic and organizational purposes (new reporting structure, one unit absorbs another, unit name change, etc.). As such, changes can be made per time period (fiscal/academic year). As units move and change from year-to-year, those changes can be reflected in your organizational.
The Organizational Hierarchy is based on the concept of child and parent nodes. For example, Academic Affairs is the parent of the following children nodes: College of Arts and Sciences, College of Business, College of Health Sciences, Honors College, etc...Children of Academic Affairs can have child units of their own. This structure helps to organize data and users. Below is a screenshot of an example Organizational Hierarchy for the FY 2016.
The organizational hierarchy can be accessed by Site Administrators through the settings area inside of Planning.
| Associate a Time Period and Organizational Hierarchy |
After creating a new Time Period within Planning an Organizational Hierarchy will need to be associated with the time period before the time period is displayed inside of Planning. You can choose your new Time Period from the drop-down menu, in the example below FY 2019 does not have an Organizational Hierarchy associated with it, which the application lets us know. We then have the option to copy an Organizational Hierarchy from another time period.
Once you have copied the Organizational Hierarchy from another time period, you will be able to edit units for your newly created Time period.
It is highly encouraged that site administrators speak with their Campus Consultant before making changes to the organizational tree.