Adding/editing roles: Difference between revisions
(Add basic definations) |
(→Permission terms: attempted to simply define) |
||
| Line 22: | Line 22: | ||
===Permission terms=== | ===Permission terms=== | ||
*Inherit | From lowest to highest, from general to specific. | ||
*Allow | |||
*Prevent | *Inherit - pass along from before | ||
*Inhibit | *Allow - let happen or permit | ||
*Prevent - stop | |||
*Inhibit - forbid | |||
==Examples of roles== | ==Examples of roles== | ||
Revision as of 16:07, 24 October 2006
Template:Moodle 1.7Moodle 1.7 allows the administrator to add or edit existing roles available on the Moodle site. This is done through the Administration block>>User>>Permission>>Define roles menu area.
Define roles
There are 3 tabs on the define role page.
Manage roles
The place to add and define permissions for a new role, or edit name and/or permissions associated with existing Moodle roles.
Allow role assignments
A matrix which determines which role can assign users to other roles.
Allow role overrides
A matric which determines which role can override a previously assigned role. The default is that only an administrator can override any role assigned by another role.
Permissions
The permissions matrix allows a very granular approach to assigning rights to a role (a class of users). Assigning or editing permissions should be done with great care. A change can produce a profound unwanted effect, or an annoying effect that will be hard to understand the cause.
There are over 150 lines of capabilities where any of 4 different permissions can be assigned. The capabilities are grouped in 21 catagories. Here is the top of the list.
Permission terms
From lowest to highest, from general to specific.
- Inherit - pass along from before
- Allow - let happen or permit
- Prevent - stop
- Inhibit - forbid
Examples of roles
Why would a site want different roles? Consider
| *Site Designers | *Educational Authority Adviser | *Educational Inspector | |
| *Second Marker / Moderator | *Peer observer of teaching | *External Examiner | |
| *Parent | *Manager | *Weekly Seminar Leader | |
| *Mentor/Mentee | *Community-Designed Rating Criteria | *Visitor | |
| *Guest Speaker | *Former Student | *Alumnus | |
| *Librarian | *Teacher | *Community Education Tutors/Trainers | |
| *Secretary/Student Worker | *Teaching Assistant | *Student - FERPA rights | |
| *Help Desk |
Basic concept definations
- A role is an identifier of the user's status in some context. For example, teacher, student and fourm moderator are examples of roles.
- A capability is a description of some particular Moodle feature. Capabilities are associated with roles. For example, being able to reply to a forum post is a capability.
- A permission is some value that is assigned for a capability for a particular role. For example, using the prevent permission to limit all students from posting to any forum.
- A context is a "space" in the Moodle, such as courses, activity modules, blocks, forums etc.
- A hieracary of permissions determines which permission wins or is going to be in effect if there is an apparent conflict. For example, the site allow all students the permission to to post in forums, but a teacher might prevent that right in a particular course. The hieracary of permissions would allow a student to post in one course but not in another course.
See Also
Assign roles User Policies
