Organisation structure: Difference between revisions
No edit summary |
Paul Holden (talk | contribs) (Small grammar changes.) |
||
| Line 2: | Line 2: | ||
= Overview = | = Overview = | ||
Organisation structure is a combination of three Moodle Workplace features: departments, positions and jobs. | |||
{{MediaPlayer | url = https://youtu.be/c-vx7SL2Q20 | desc = Moodle Workplace | Training | Organisation Structure}} | {{MediaPlayer | url = https://youtu.be/c-vx7SL2Q20 | desc = Moodle Workplace | Training | Organisation Structure}} | ||
| Line 9: | Line 9: | ||
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. | 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 | This page is available to users with either the [[Tenant administrator role|Tenant administrator]] or [[Organisation manager role|Organisation manager]] role. | ||
Departments and positions can be grouped together into frameworks. | 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 could be based on physical location and another one on a team within an organisation. Frameworks can also represent sub-divisions of a big organisation. | ||
There can be different use cases for the frameworks - they can be used to create completely isolated sets of departments, for example | |||
Both | Both position and department 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". | Positions have additional properties that are called "Global manager" and "Department manager". See the following example for an explanation: | ||
Example 1: Organisation structure hierarchy based on positions | |||
The company chooses to store their hierarchy in the "Positions" tree. The CEO is the top position, underneath are the CTO and CFO. Managers of several technical teams are under the CTO, and members of these teams are under these managers. This means that there are separate positions in the hierarchy for "Members of team A" and "Members of team B". The same company uses departments as physical locations (countries, cities or rooms). They may or may not have a hierarchy. In this structure all positions that have "children" will be marked as a "Global manager". This will allow people who hold jobs in these positions to see everybody in the positions below them as their team. It's probable that the CEO does not need to "Receive notifications" from everybody in their company but they may 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 the "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. | |||
It's possible to create more complex structures with hierarchies in both positions and departments, and also positions that are both "Global manager" and "Department manager". | |||
= Assigning jobs = | = Assigning jobs = | ||
When the organisation structure is defined, the 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: | Being an organisation manager means that: | ||
- your team list is displayed on your dashboard | - your team list is displayed on your dashboard | ||
- you are able to allocate your team members to | - you are able to allocate your team members to 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 are able to view custom reports on your team members WITHOUT any capabilities (if enabled in the position settings) | ||
- you can receive | - you can receive notifications about completions/overdue certifications (if enabled in the position settings) | ||
Having organisation structure can also help tenant administrator to: | Having an organisation structure can also help the tenant administrator to: | ||
- create dynamic rules that automatically do something based on users positions or departments (for example, enrol them in induction course) | - create dynamic rules that automatically do something based on users positions or departments (for example, enrol them in an induction course) | ||
- create custom reports that have a specific department (or position) as it's audience | - create custom reports that have a specific department (or position) as it's audience | ||
- filter/search | - filter/search lists of users within the organisation based on their position and department | ||
Revision as of 10:06, 20 September 2019
This feature is part of Moodle Workplace, which is available through Moodle Partners.
Overview
Organisation structure is a combination of three Moodle 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 either the Tenant administrator or Organisation manager role.
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 could be based on physical location and another one on a team within an organisation. Frameworks can also represent sub-divisions of a big organisation.
Both position and department 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". See the following example for an explanation:
Example 1: Organisation structure hierarchy based on positions
The company chooses to store their hierarchy in the "Positions" tree. The CEO is the top position, underneath are the CTO and CFO. Managers of several technical teams are under the CTO, and members of these teams are under these managers. This means that there are separate positions in the hierarchy for "Members of team A" and "Members of team B". The same company uses departments as physical locations (countries, cities or rooms). They may or may not have a hierarchy. In this structure all positions that have "children" will be marked as a "Global manager". This will allow people who hold jobs in these positions to see everybody in the positions below them as their team. It's probable that the CEO does not need to "Receive notifications" from everybody in their company but they may 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 the "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.
It's possible to create more complex structures with hierarchies in both positions and departments, and also positions that are both "Global manager" and "Department manager".
Assigning jobs
When the organisation structure is defined, the 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 an organisation manager means that:
- your team list is displayed on your dashboard - you are able to allocate your team members to 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 notifications about completions/overdue certifications (if enabled in the position settings)
Having an organisation structure can also help the tenant administrator to:
- create dynamic rules that automatically do something based on users positions or departments (for example, enrol them in an induction course) - create custom reports that have a specific department (or position) as it's audience - filter/search lists of users within the organisation based on their position and department
