To grant a user administrative or managerial oversight, Portal Administrators can choose between two different types of reporting relationships between LMS users: a Position Code hierarchy or a direct Person-to-Person structure.
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 the way 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.
This report helps identify positions and associated users who are orphaned by gaps in the hierarchy: Reports > Classic Reports > Users > Orphaned Users by Company.
When building Position Relationships, keep in mind:
The positions can, but are not required to represent the job titles of your organization.
Not all managerial relationships are concerned with employee training management. When users have a number of direct and dotted-line managers, consider building the hierarchy in the LMS that pertains to just those superiors who are relevant to the training aspect of employee management. Consider which superior position would be the one to:
approve a subordinate position’s enrollments, if necessary
assign training to the employee
get notified of subordinates’ training activities
view employee training history via LMS reporting
Having a position hierarchy that is too complex with extensive numbers of superiors and/or subordinates per position can have an adverse impact on system performance. It is okay to have more than one superior position, but it should be restricted to those relationships that make sense from the perspective of employee training oversight.
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.
My Team/Employees: Users who are assigned a position with subordinates gain access to the My Team tool, or the "Employees" tab on the Classic Home page. Managers have a number of tools available to them from this one page, including a list of their employees across all organizational profiles, user details and drill down, and even tabs that navigate between team training views.
Approvals: There are three types of Approvals -- Enrollment, Course Interest, and Self Registration. The Approvals tab automatically appears on a user’s Home page if their position is superior to one or more other positions. A manager can view pending approvals by selecting the appropriate approval type link, then approve or reject as needed.
Other Impacts of Position
Announcements: Portal administrators can use the embedded messaging system to communicate with a targeted set of users based on a wide range of filter options, including their Position assignment. This feature is available on the left navigation menu.
Prerequisites/Course Equivalencies: Use position membership as part of an equivalency or prerequisite rule to restrict course access to users in certain positions only.
Departments: This is one of two ways to group users by position in the LMS. You can find the Department functionality in the left navigation menu under Organizations. It is designed to mimic functional groups in your organization and can be used by the LMS for sending announcements to specific subsets of users.
Position Groups: These are part of the Certification/Curriculum Management feature. Individual Positions that require the same certifications may be organized into groups. Certifications and/or Curriculum requirements can then be assigned to one or more Position Groups, providing automatic assignment of certification/curriculum tracks to all users in a given Position Group.
Add Interest: Use position to find a subset of users to mass enroll in a particular course using the Mass Add Interest function. This is found on the left navigation menu under Interests > Add Interest.
General Search: Position assignment is often used throughout the LMS when searching and targeting specific users, for example, when using tools to batch enroll others, send announcements, and add interests.
Reports: Position, in combination with organization level, contributes to the scoping of report results for a particular user. Managers who can run reports will normally see results only for users in subordinate positions to their own and only at the organizational levels they to which they are assigned.
Follow these steps to add new positions to your LMS and relate them to superior and/or subordinate positions as necessary.
From the left navigation menu, select Organizations > Add Positions.
On the Add Position page, make entries as described below. Asterisks [*] on the page indicate a required field.
Follow these steps to view or edit a position.