Organisation structure
This feature is part of Moodle Workplace, which is available through Moodle Partners.
Overview
Organization Structure is a combination of three workplace features: departments, positions, and jobs.
Departments and positions
From the workplace launcher, the manager clicks "Organisation structure". We can use departments and positions hierarchies to define any organisation structure and define all reporting lines, assigning jobs to employees in any department with any position.
This page is available to users with role Tenant administrator or Organisation manager.
Departments and positions can be grouped together into frameworks. There can be different use cases for the frameworks - they can be used to create completely isolated sets of departments, for example, one framework would be based on physical location and another one on the team within organisation. Or frameworks can represent sub-divisions of a big organisation.
Both positions and departments structures can be hierarchical, however it is more likely that the organisation would have only one of them hierarchical and another one as a flat list.
Positions have additional properties that are called "Global manager" and "Department manager".
It is probably easier to explain on example.
Example 1, organisation structure hierarchy based on positions
The company chose to store the hierarchy in the "Positions" tree. CEO is the top position, underneath are CTO and CFO, Managers of several technical teams are under CTO, members of these teams are under these managers. This means that there are separate positions in the hierarchy for the "Member of team A" and the "Member of team B". The same company uses departments as physical locations (countries, cities or rooms), they may or may not have hierarchy. In this structure all positions that have "children" will be marked as "Global manager". This will allow people who hold jobs in this positions to see everybody in the positions below them as their team. Probably CEO does not need to "Receive notifications" from everybody in their company but they definitely need to see reports on them.
Example 2, organisation structure hierarchy based on departments
In this company departments represent different divisions and teams inside the company. Their structure is hierarchical. There are several positions, such as "Facilitator" and "Staff member". The "Facilitator" position has "Department manager" checkbox enabled. When people get assigned jobs in different departments, the facilitators will be able to see everybody from their department as their team.
There can be more complex structures with hierarchies in both positions and departments and also positions that are both "Global manager" and "Department manager".
Assigning jobs
Now when the organisation structure is defined, tenant administrator can assign jobs to different users. As shown in the examples above, when somebody is assigned a job that has manager permissions, they are able to see other people as their team.
Being organisation manager means that:
- your team list is displayed on your dashboard - you are able to allocate your team members to the programs and certifications WITHOUT any capabilities (if enabled in the position settings) - you are able to view custom reports on your team members WITHOUT any capabilities (if enabled in the position settings) - you can receive notificaitons about completions/overdue certifications (if enabled in the position settings)
Having organisation structure can also help tenant administrator to:
- create dynamic rules that automatically do something based on users positions or departments (for example, enrol them in induction course) - create custom reports that have a specific department (or position) as it's audience - filter/search list of users in the organisation based on their position and department
