When you add group:role permissions to faculty users you will notice a Clinical Faculty checkbox in each organization they are a part of. When you add a user through the user interface this will automatically be checked off. Note that as of Elentra ME1.12 you cannot set a user as a clinical faculty member in one organisation but not another.
This is mostly a tool to store information and is rarely used elsewhere in Elentra. One place it is used is when reporting on annual reporting. When generating reports on annual reports you can filter by clinical and non-clinical faculty (see below).
Most use of features in Elentra is based on a users group and role permission. A user can be assigned multiple group and role permissions within an organization and can hold the same permission across multiple organizations.
Below are group and role settings and their general system permissions. Please remember that your installation of Elentra may have customized aspects of the software and changed the access of specific group and roles.
Alumni
Year of Graduation
Have basic read-only access.
Faculty
Admin
Faculty:Admin can pretty much do anything in the system within their designated organisation. They will be able to access all courses including gradebooks and events. Use this permission sparingly.
Faculty
Director
Faculty:Director can be designated as "Course Directors" for specific courses. They will be able to edit the content of any course pages/websites or learning events in the course they are affiliated with.
Faculty
Lecturer
This is the most common permission for faculty to have. Faculty:Lecturer users can edit the content of any learning event that they are scheduled to teach. They can also be added as graders to assignments and set as assessors for distributions.
Faculty
Faculty
Basic read-only access as faculty members.
Medtech
Admin
Medtech:Admin permissions are generally used for technical staff who support an Elentra installation. Medtech:Admin can view all records in the system and do anything regardless of any organizational restrictions.
Medtech
Staff
Have basic read-only access.
Resident
Lecturer
This can be used in UG installations where residents act as lecturers.
Resident
Resident
This can be used in UG installations where residents play some role. Do not use this group and role for PG installations of Elentra using CBME; in that case the residents should be student:student.
Staff
Admin
Staff:Admin permissions allow a user to access almost all content within an organisation. Staff:Admin users can view and manage all courses (including gradebooks) and events, see user profiles, and edit some system settings. Typically this permission is used for curriculum coordinators (i.e., someone who is responsible for managing all courses in a given year) and sometimes for assessment and evaluation coordinators, accreditation coordinators, etc.
In contrast to medtech:admin users, staff:admin users only have access to organizations in Elentra that they are permissioned to. Also note that a user must have staff:admin permissions to be added as a curriculum coordinator of a course.
Staff
Pcoordinator
Staff:Pcoordinator (as in program coordinator) can add, edit, or delete learning events and manage any content within any of the courses they are designated as a "Program Coordinator" for on the Admin > Manage Courses > Setup tab. This permission is more limited than staff:admin.
Staff
Staff
Staff members have basic read-only access.
Staff
Translator
Can access Curriculum Tags for the purposes of providing translations. Additionally privileges TBD.
Student
Student
Students have basic read permissions to most public modules. They can also edit and in some cases remove information that they add themselves (e.g. discussion forum comments). It is important to note that students cannot be granted access to any administrative module within Elentra. There is a hard-coded exit in case all other security restrictions fail and they access /admin/*
A more detailed matrix of user ability across modules can be found here.
For information on Masked Permissions please see here.
