Development:Roles
Roles and capabilities are planned to be included in Moodle 1.7. For now, we have some basic ideas of how to implement such a structure in Moodle.
Please note that none of the following is finalised.
Definitions
By roles, we mean an identifier of the user's status, for example, teacher, student and forum moderator are examples of roles.
A capability is a permission to access some particular Moodle feature. Capabilities are associated with roles. For example, forum_canreadpost is a capability.
The existing system
Currently in Moodle, we have a fixed set of roles i.e. primary admin, admins, course creators, editing teachers, non-editing teachers, students, and guests. For each role, the capability or actions that they can performed are fixed. For example, the role student allows the user to submit an assignment, but doesn't allow the user to browse/edit other users' work. By using this setup we limit ourselves to a rather rigid set of capabilities for each role. If we want, say a particular student or group to be able to mark assignments in a particular course, we can't do that without giving these users teacher privileges.
The new roles and capability system
The new system will allow authorized users to define an arbitrary number of roles. Each role can have a customizable set of capabilities in every context. A context can be the whole Moodle site, a course, or a module instance, e.g. quiz 5 in 'Introduction to Photography'. An authorized user will be able to assign an arbitrary number of roles to each user. Since the capabilities in each role could be different, there could be conflict in capabilities. This is resolved by giving roles different 'priorities'. For example, to prevent a naughty student from posting, one could assign him a 'naughty student' role that does not allow him to post. This role should have a priority higher than that of a normal 'student' role.
To facilitate exceptional cases in roles and capabilities, we can use exception rules. For example, we can specify a rule saying that all students are able to mark/read other students' assignment in this particular course. Note that such rules need to have a priority as well. The capability of a user, in any context is then resolved by finding the highest priority role/rule.
A smooth upgrade will be provided with 1.7. The existing roles (admin, teacher, student, etc), and the exisiting capabilities will be retained. This is done by creating default roles at site/course levels, and assigning the current users to these roles accordingly. The default roles will have default capabilities associated with them, which pretty much is what we have in 1.6. The whole process is automatic so there's nothing to worry about =). With no modifications, Moodle will operate exactly the same before and after the upgrade.
The plan
There are a few major things that need to be done. Here's a list (in no particular order):
- Identify permissions required for site/course/each module.
- Define the database structure for storing roles and capabilities.
- Recode the whole of Moodle, including all modules to support the new structure. Instead of using
isteacher()orisstudent()we should be usinghas_capability($capability, $instanceid)etc. A new API for handling roles and capabilities will be implemented (accesslib.php). - Add storage of capabilities for each module. Can be done either in a file, e.g. db/capability.xml, or as a sql file that gets installed to a central db whenever this module is installed. Either way, what do we do when we need to upgrade these capabilities? Some capabilities might need refining/splitting later on. How do we control the 'version' of a capability?
- Consider interface issues, especially how to manage conflicting role/exception rules.
- Upon logging in, we should use a cache to store capability, down to module level. How should that be structured?
- Consider the impact on backup/restore.
- Upgrade path for current users. The user information in table user_coursecreators, user_admins, user_teachers, and user_students will most likely be migrated to the new roles and capabilities tables. The users will most likely be assigned default roles that comes with default capabilities (e.g. teachers, admins, students, etc). The old tables themselves could possibly be dropped at the end of the upgrade.
Capabilities
This is a comprehensive list of capabilities, well, in the making. It is important that capability names are unique. Please edit. Should we distinguish canedit and candelete?
What about a canview capability? Like for choice, where a person is allowed to see the choice question but not participate in it? --N Hansen 19:29, 16 May 2006 (WST)
Certainly need a canview or cansee capability for parents as linked to their child's data/contributions.
Do we need to add canview and cansearch logs at site/course/user/group level?
I could use a canview at a course level, if I understand what that means exactly.--N Hansen 19:43, 12 June 2006 (WST)
Core-level Capabilities
Moodle core capabilitie names start with 'moodle/'. The capabilities for the Moodle core are defined in lib/db/access.php Do we still keep student view? What is a student view?
- moodle/site:config - applicialbe in admin/index.php and config.php (might break down later)
- moodle/course:create - create courses
- moodle/course:view - possibly a capability used for checking student role
- moodle/course:viewparticipants - allows a user to view participant list
- moodle/course:update - updates a course, i.e. adding/removing/editting activities
- moodle/course:viewscales - view scales (i.e. in a help window?)
- moodle/course:managescales - add, delete, edit scales, move scales up and down
- moodle/course:managegroups - managing groups, add, delete, add user in etc
Module-level Capabilities
The capabilities are cached into a database table when a module is installed or updated. Whenever the capability definitions are updated, the module version number should be bumped up so that the database table can be updated.
The naming convention for capabilities that are specific to modules and blocks is 'mod/mod_name:capability'. The module capabilities are defined in mod/mod_name/db/access.php.
- Assignment
- mod/assignment:read - reading the assignment description
- mod/assignment:grade - grading, viewing of list of submitted assignments
- Chat
- mod/chat:chat - allows a user to participate in this chat
- mod/chat:readlog - allows a user to read past chat session logs
- mod/chat:deletelog - allows a user to delete past chat logs
- Choice
- mod/choice:choose - make a choice
- mod/choice:readresponses - read all responses
- mod/choice:deleteresponses - deletes all responses
- mod/choice:downloadresponses - download responses
- Database
- mod/data:readentry - reads other people's entry
- mod/data:writeentry - add / edit and delete (own) entries
- mod/data:managetemplates - add, delete, edit fields and templates
- mod/data:manageentries - edit/delete all entry
- mod/data:comment - comment
- mod/data:managecomments - edit/delete all comments
- mod/data:rate - rate an entry
- mod/data:approve - approves an entry
- mod/data:uploadentries - batch upload of entries
- Exercise
- mod/exercise:assess
- Forum
- mod/forum:viewforum
- mod/forum:viewdiscussion
- mod/forum:viewdiscussionsfromallgroups
- mod/forum:startdiscussion
- mod/forum:replypost
- mod/forum:managediscussions
- mod/forum:viewrating
- mod/forum:rate
- Glossary
- mod/glossary:read - view entries
- mod/glossary:write - add entries
- mod/glossary:manageentries - add, edit, delete entries
- mod/glossary:managecategories - create, delete, edit categories
- mod/glossary:comment - comment on an entry
- mod/glossary:managecomments - edit, delete comments
- mod/glossary:import - import glossaries
- mod/glossary:export - export glossaries
- mod/glossary:approve - approve glossaries
- mod/glossary:rate - rates glossary
- mod/glossary:readrate - view rating?
- Hotpot
- Label
- Lams
- Lesson
- Quiz
- Resource
- Scorm
- Survey
- mod/survey:download - downloads survery result
- mod/survey:participate - participate/ do survey
- mod/survey:readresponses - read all user's responese
- Wiki
- Workshop
OU Desired Capabilities
We will use this page to detail the specific capabilities needed to create the roles for the OU. Each capability has three parts:
- the name itself which can be anything and should be simple and short
- the name of the module it belongs to ("moodle", "blog", "course", "forum" etc)
- the name of the "class" it belongs to, currently "read" or "write". We can change
this in future if we can work out a sensible scheme. This is purely used for the GUI to "clump" similar capabilties together
I would recommend we create a table for each module with the name, module and class of the capability
Moodle Site
| Name | Module | Class | Comment |
| Create Course | Site | Write | |
| Delete Course | Site | Write | |
| Create Catagory | Site | Write | |
| View Courses | Site | Read | |
| Add User | Site | Write | |
| Move course to another category | Site | write | |
| Make course visible to students | Site | write | |
| new features? Site wide subscription default/setting | Site | optional/forced etc | recommended default optional for all OU forums |
| Access site | Site | read/write/no access | used to ban individuals from Moodle? |
Course - home page
| Name | Module | Class | Comment |
| Add Blocks | Course | On/Off | CT & Staff = Off, Admins = On |
| Add/View users ALs/Staff/Students | Course | Read/Write | CT/Staff = Read (this should be managed through circe or the administrator). Admins = Write |
| Course settings | Course | Read/Write | Course teams = Read, Staff = no access. Admins = write |
| Move blocks? | Course | on/off | CT/Staff = off, Admin = on |
| Delete resource/page/activity/block | Course | on/off | CT/Staff= off, Admin = on. As we have no recovery process would it be best to prevent course teams from deleting resource pages & other items on the home page? |
| hide items | Course | on/off | Ct=on, staff=off, admin=on |
| add resource | Course | on/off | Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which resource types are listed per course/site |
| add activity | Course | on/off | Ct=on, Staff=off, admin=on used in conjunction with admin filer to restrcit which activity types are listed per course/site |
| upload calendar (OU feature?) | Course | read/write | Ct=read, admin=write. CTs should not be able to upload a calendar (admin will add this & need to ensure the CT don't overwrite it with an alternative) |
| edit calendar | Course | read/write | Ct=write, Staff=read, admin=write |
| admin functions, e.g. back up, restore, import | Course | read/write | Ct=read, admin=write |
| edit groups | Course | read/write | Admins = write CT/Moderators=on staff=read? |
| Access course | Course | read/write/no access |
Course - resource page (OU version)
| Name | Module | Class | Comment |
| add authid | Course (resource page) | Read/Write | Admin=Write, CT=Read |
| add placeholder | Course (resource page) | on/off | admin=on, CT=Off |
| Add RSS feed | Course resource page | on/off | admin=on, ct=off? |
| access page | Course resource page | read/write/noaccess | use to restrict access to pages by role? |
Forum
| Name | Module | Class | Comment |
| move discussion to (archive/move feature) | Forum | on/off | admin=on, CT/Moderator=on AL=off? |
| update this forum | Forum | read/write | admin=write, CT/Moderator=off? it would be good to break this down further and or premote some defaults for use. e.g subscription I think there should be a server wide default of optional for all OU forums which can't be oevrriden at the course level. |
| delete message/thread | Forum | on/off | admin=on, CT/Moderator=on AL/student=off? some course teams won't want students/als to be able to delete their own posts |
| split | Forum | on/off | admin=on, CT/Moderator=on AL/student=off |
| post to forum | Forum | on/off | |
| access forum | Forum | read/write/no access | |
| attach file to message | Forum | on/off access |
Blog
| Name | Module | Class | Comment |
| replace | replace | replace | replace |
Quiz
| Name | Module | Class | Comment |
| replace | replace | replace | replace |
Wiki
| Name | Module | Class | Comment |
| replace | replace | replace | replace |
Resources
| Name | Module | Class | Comment |
| replace | replace | replace | replace |
Questions
I am adding question categories here because they seem to have been forgotten in the whole scheme of things since having been removed from the quiz module itself. I've made a suggestion on how these could be handled in bug 6118.
Scenarios
This section is for brainstorming some example roles that we would like to support:
Student
Has this one been missed?
Site Designers
Is there a role for people involved in how the site looks but not full administrators? Thinking here of online control of themes rather than FTP theme uploading. But in either case they caneditlogos, caneditcss, candeditlevelatwhichthemeapplies.
Educational Authority Adviser
Someone who would want to browse the site and may be asked to comment or contribute to particular discussions or developments in school. Access for this role would be controlled by the school in the case of school level moodles but may be different if there were to be a Local Authority wide Moodle.
Educational Inspector
Someone who will visit the site to verify the school's self review that comments on home school relationships, extending the classroom etc. They may want to see summaries of usage and reports from surveys garnering parent and pupil views.
Second Marker / Moderator
A teacher within ths site that has access to assignments and quizzes from another teacher's course for second marking purposes. This may need additional functionality adding to the assignment module so that two sets of grades/feedback can be given to one set of assignments.
External Examiner
Has all the rights of inpectors, but would also need to be able to review assignments and feedback, view forums, glossaries etc. However, would not want to post, feedback onto the site at all.
Parent
A parent will have one or more children in one or more institutions which could be using one or more moodle instances or a mixture of Learning Platforms. A parent's role will vary depending on the age of their children and whether they are contributing as a parent or a school supporter.
In Early Years (EY) and Key Stage 1 (KS1) they may play/learn on an activity or write for the child. Parents often interpret homework tasks and read to their children perhaps filling in a joint reading diary.
In Key stages 3 and 4 this changes to more of a monitoring/awareness role where a parent would expect to have a summary report of attendance, attainment and general achievement on a weekly/monthly/termly or annual basis. Parents will often be asked to sign and write back comments about this review report.
In all Key Stages there is a great need for parents to receive communication from the school which they can confirm they have received by signing a form. In some cases this may also involve making choices from a list. It may also involve payment for a trip or disco being returned so there could be the possibility of electronic payments.
Parent's evenings often involve complex booking systems that attempt to get parent's and teachers together. Easy for EY/KS1/KS2 very difficult for KS3/KS4. Wow would this help if it was built into the Learning Platform.
In some cases there needs to be confidential communication between the parent and the teacher without the child being party to this. It may involve teaching and learning but could also involve a behaviour or medical issue. Often this may be done via a sealed letter or face to face.
The latest incarnation of OfSTED with the Self Review Framework (SEF) there is a greater emphasis on schools gathering parent voice via surveys and discussion. There is a clear match here with parents have access to parental votes, questionnaires and discussions and for schools to be able to publish news, results and reports back to parents.
In the UK the LP framework and agenda as being pushed by the DfES via Becta emphasises that within the mandatory groups and roles functionality the parent role is likely to be required to meet the LP Framework procurement standard.
Manager
Please add text here...
Weekly Seminar Leader
In a university seminar, typically 8-15 students in their 3rd/4th year, each student is responsible for leading one topic in a study series. I ask each student to research 5-10 resources, then give a powerpoint presentation to the other students. This is followed by an in-class discussion and then online homework. The homework involves some fun quiz questions and then some reflective journal questions. I ask each seminar leader to prepare the quiz questions and journal questions as well as their presentation. To do that, I would like to assign activity-making/authoring roles to the student--either for a short period, or for duration of the whole course. Thus "Allow Quiz Authoring Role" or "Allow Assignment Authoring Role" at the course level or, if possible, even the Topic level (in a topic or week format course) would be important.
Mentor/Mentee
Please add text here...
Community-Designed Rating Criteria
The gradebook tends to be the domain of the teacher. What if community/peer ratings/marks could also be entered there? What if peer assessment criteria could be designed by the students, not just the teacher?
Visitor
This would be a role whereby one could allow a visitor to visit one's classroom. This might be a colleague interested in seeing your course, or a journalist who might be writing an article about one's site. They should not be able to see the names of any students anywhere (eg recent activity, forum posts) for privacy reasons. They should be able to try out things like quizzes, and lessons but no grades would be recorded (like in teacher preview mode). They would not be able to participate in choices and forums but could view them. It would be read only in a way like former-student role below but without access to a particular student's records that former student role would grant.
Former Student
This role would be of particular use for courses with rolling enrollments. This role would be one where a student had completed all of the requirements of a course (ie assignments, quizzes etc.) but wished to have continued access to the course material for review or consultation. The key factor is that one would give access to the completed student to the notes he read, his work and the teacher's comments on it, but he would not be allowed to do anything that would take up the teacher's time. In other words, a sort-of read-only access to the course. How forums, which might contain pertinent information and would continue to grow, would be handled is a question. Perhaps the student would be shown only what was in the forums at the time he completed the course. He would not be allowed to see any new posts or add any himself. Same thing for database and glossary entries. In other words, a snapshot of the course at the time his regular enrollment ended. He shouldn't be able to see the names or profiles of any newly enrolled students for privacy reasons-hence the restrictions on forum access. One issue that would have to be dealt with would be changes to existing modules-such as resources. Does the student get access to the module as it was or as it is? We have no versioning of resources in Moodle so this would be a problem. What about a teacher changing a quiz question so that the answer is different? What would a former student see?
Librarian
Reference Librarians have an active role in most of the courses taught at Earlham College (with Bibliographic Instruction). The Librarian role within Moodle could encompass default read access to all courses (unless prohibited by course teacher) and read access to all components of the course unless access is barred (again by teacher). The Librarians would also perhaps have a block called perhaps Reference Services or Reference Desk with write access where they could deposit resources. Also this block might have a chat applet whereby enrolled students could chat to the Reference Librarian on duty about their bibliographic research needs.
Teacher
Teachers should have read access to other Teacher's courses unless explictly prohibited. They should be able to set parts of their own course to be totally private (perhaps even to admin?). Just as each activity can currently be set to have group access, each activity could have a permissions field. Teachers could set default permissions for all activities on their course (eg they might disallow Librarian access for example) and then change the access permission for an individual activity.
I think that what is needed is a simple heirarchy of permissions and levels of granularity.
I would take issue with "teachers should have read access to other teacher's courses unless explicitly prohibited." This is a violation of the students' privacy as how they perform and what they do in one class isn't the business of another teacher. Moreover, in the real world a teacher wouldn't suddenly go sit in on a colleague's class without asking permission first. I would not have appreciated such an invasion of privacy as either a teacher or a student. It could be an option, but shouldn't be default.--N Hansen 19:54, 12 June 2006 (WST)
Community Education Tutors/Trainers
Teachers may be community adult education trainers making use of a school moodle so must only have access to their courses unless given access elsewhere. They would not necessarily get the default teacher privileges.
Secretary/Student Worker
We often have faculty who want their departmental secretary or student worker to scan and upload files and perhaps create resources. Currently they have to be given teacher access to the course. This is dangerous from a FERPA standpoint since they could easily get access to grades.
Teaching Assistant
Our Faculty frequently have undergraduate students acting as Teaching Assistants. These students need to be able to add resources, create assignments, and possibly grade assignments. However, due to FERPA they cannot have access to other students' overall grade information. I think the requirements here are slightly different than those of Secretary/Student Worker
Admin - Catgory based
Basically a person in between full Admin and Creator that has the permissions of an Admin but only with respect to courses and students. Currently a Creator has permissions site-wide which does not always meet the requirements of a given organisation (e.g. Department A may not be happy that a person from Department B can create/modify courses within Department A's area). The ability to designate a Creator within a specific category would allow areas to be set up for a faculty/department/organisation and allow the Admin for that area to create/delete courses, upload users, add site-wide entries to the calendar etc.
PROCESS ROLES
organising the learning process for a group you wish to have the choice to place students in differnt roles: examples of this are:
See also
- Using Moodle Roles and Permissions architecture forum discussion
