The institutional hierarchy provides us with a tree structure to organize different elements of the LMS: roles, tabs, courses, organizations, users, modules, tools... which makes it possible to "copy" the structure of our institution into Blackboard.
By using the hierarchy, Blackboard administrators can create a multi-level structure that reflects the actual structure of the institution. It is designed to delegate administrative tasks to other users by assigning system roles associated with those nodes, so, for example, each faculty, department, or campus can have its own administrator who manages users, courses, organizations, tools, etc., as long as they belong to the node where that user is an administrator.
The larger the institution, the more important the use of this organizational hierarchy in Blackboard becomes for managing the system at different levels.
Example:
- Institution
- Faculty 1
- Department A
- Department B
- Faculty 2
- Faculty 3
- Faculty 1
Administrator 1 belongs to Faculty 1 and manages the entire system for that faculty. If we assign them as an administrator at that level, they will be able to manage the Faculty 1 node and all its aspects.
In Department A, there is a person who helps professors manage courses, Intern A. Intern A is assigned the course administrator role for Department A. Therefore, they will have access to administer the courses – and only the courses – of Department A.
If Faculty 2 and Faculty 3 have a single Administrator 2+3 who manages the system for both faculties, we will assign Administrator 2+3 the administrator role for both nodes.
Then we could have Secretariat 2 and Secretariat 3, who handle managing the students of the respective faculties and thus would have user administrator permissions for each of them.
At the Institution level, there could also be a graphic designer who manages the branding of each faculty, holding a brand administrator role.
In a small institution, using this hierarchy is not necessary, although it can also be useful, for example, to organize all courses of each program or master's degree for administrative purposes. As the number of faculties, users, and complexity grows, it will become essential.
Using the institutional hierarchy allows us to separate data when generating reports in Illuminate, as well as the activation of tools by nodes in Learn.
Comments
0 comments
Please sign in to leave a comment.