Portal Administrators can choose between two different types of reporting relationships between LMS users to grant a user administrative or managerial oversight: a Position Code hierarchy or a direct Person-to-Person structure. This page covers how to Manage Positions.
In Position Code reporting, position codes are created to establish Superior/Subordinate relationships that determine user oversight. These relationships enable users with superior positions (managers) to view training, approve course enrollment requests, and set and manage training goals for subordinate users (students) within their organization. This reporting style is best used when the reporting structure designates subordinates to report to a specific superior position consistently throughout the organization.
Person-to-Person reporting enables Portal Administrators to set up reporting relationships based on Username, rather than Position codes. With Person-to-Person reporting, a user may have zero, one, or multiple managers, similar to how many organizations are structured today. These relationships also enable managers to view training, approve course enrollments, and enroll others in courses in the same way they can with for Position Code Reporting. Managerial assignments in P2P reporting are established at the profile level, so it is possible to have different managers across multiple user profiles.
LatitudeLearning® uses Position Hierarchy as the default reporting structure for new portals. Even Portal Administrators who select Person-to-Person for user and training management must still rely on a sound LMS Position Hierarchy structure to generate Training Progress Reports, assign Certifications and Curriculums (via Position Groups), and approve Self Registrations.
Whether you’re considering implementing Person-to-Person in your new LMS or transitioning an existing LMS to this new reporting structure, please consider contacting Latitude Support for consultation services.
It is helpful to understand how you want your organization to oversee training and report on training activities prior to setting up your positions or building a position hierarchy. The position hierarchy’s primary purpose is to provide managerial oversight of training for users in subordinate positions and to ensure that managers have visibility of those users in reports and on their My Team or Employees Tab pages. It also drives Certification and Curriculum goals and eligibility-based on a user’s primary profile assignments.
IMPORTANT!
When relying on Positions for managerial oversight, it is critical that the hierarchy of superior/subordinate relationships has NO gaps. The top position in the hierarchy, which should have no superiors, is the position that should be assigned to anyone acting as a portal administrator, who needs to see every active/inactive user. All other positions should be assigned at least one superior position and they must all eventually be connected, indirectly or directly to the top position. The TRA – Training Administrator position is the default top provided in the LMS. It is acceptable to create a different top level position, but care is required to ensure it is properly linked to other positions and is assigned to all portal administrators under their highest profile.
Use this report to identify positions and associated users orphaned by gaps in the hierarchy:
Reports > Classic Reports > Users > Orphaned Users by Company.
When building Position Relationships, keep in mind:
The LMS uses Position in conjunction with Organization and Role information to support managerial users in several key ways. This section assumes that Position-to-Position reporting is enabled, not Person-to-Person.
Follow these steps to add new positions to your LMS and relate them to superior and/or subordinate positions as necessary.
Follow these steps to view or edit a position.