Roles and permissions: Difference between revisions
Mark Watts (talk | contribs) m (→Roles) |
|||
| Line 20: | Line 20: | ||
==Upgrading to 1.7== | ==Upgrading to 1.7== | ||
The upgrade to 1.7 is as smooth as we could make it. The existing roles (admin, teacher, student, etc), and the existing capabilities will be automatically 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, mirroring what we have in 1.6. With no modifications, Moodle will operate almost exactly the same before and after the upgrade. | |||
==See also== | ==See also== | ||
Revision as of 08:41, 7 November 2006
Roles
Previous Moodle versions had predefined, fixed roles. There was no easy way to change what a teacher, or student, for instance, could do. While fixed roles are adequate for many users, others require greater flexibility in regulating how users see and interact with the system.
With Roles, authorised users can create any number of customised roles and assign them to users. From 1.7, an organisation can create multiple roles so that, for instance, students assigned Role A could post to forums, while students assigned Role B are prevented from posting.
Definitions
- A role is an identifier of the user's status in some context. For example, teacher, student and forum moderator are examples of roles.
- A capability is a description of some particular Moodle feature. Capabilities are associated with roles. For example, mod/forum:replypost is a capability.
- A permission is a value that is assigned for a capability for a particular role. For example, allow or prevent.
- A context is a "space" in the Moodle, such as courses, activity modules, blocks etc.
Capabilities
Capabilities are aggregated and controlled via roles. Stated another way, a role consists of a list of capabilities for different possible actions within Moodle (eg delete discussions, add activities etc). With 1.7 it's now possible to have sophisticated yet flexible levels of control over participants and what they can or can't do.
Upgrading to 1.7
The upgrade to 1.7 is as smooth as we could make it. The existing roles (admin, teacher, student, etc), and the existing capabilities will be automatically 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, mirroring what we have in 1.6. With no modifications, Moodle will operate almost exactly the same before and after the upgrade.
See also
- Development:Roles
- Using Moodle Roles and Capabilities forum
