Note: You are currently viewing documentation for Moodle 2.9. Up-to-date documentation for the latest stable version of Moodle may be available here: Roles and permissions.

Roles and permissions: Difference between revisions

From MoodleDocs
No edit summary
 
m (link renaming)
 
(74 intermediate revisions by 25 users not shown)
Line 1: Line 1:
This page is intended to be a quick overview of the Roles functionality that was introduced in Moodle 1.7.
{{Managing a Moodle site}}
A role is a collection of permissions defined for the whole system that you can assign to specific users in specific contexts. The combination of roles and context define a specific user's ability to do something on any page. The most common examples are the roles of student and teacher in the context of a course.  


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 participants see and interact with the system.  With Roles, authorised users can create any number of customised roles and assign them to participants.  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. 
*[[Managing roles]]
*[[Assign roles]]
*[[User policies]]
*[[Using roles]]
*[[Standard roles]]
*[[Creating custom roles]]
*[[Role export and import]]
*[[Permissions]]
*[[Override permissions]]


A capability is a description of some particular Moodle feature.  Capabilities are aggregated and controlled via roles.  Stated another way, a role consists of a list of permissions 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.
==See also==


A smooth upgrade will be provided with 1.7. 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 exactly the same before and after the upgrade.
*[[Roles FAQ]]


For more in-depth documentation on Roles, see [https://docs.moodle.org/en/Roles this] link.
[[Category:Roles]]
 
 
==See also==


*[http://moodle.org/mod/forum/discuss.php?d=38788 Roles and Permissions architecture]
[[es:Roles y permisos]]
*[http://moodle.org/mod/forum/discuss.php?d=56302#256313 An example of admin roles as set in the database]
[[eu:Rolak]]
[[Category:Roles]]
[[fr:Rôles et permissions]]
[[ja:ロールおよびケイパビリティ]]
[[de:Rollen und Rechte]]

Latest revision as of 15:50, 18 May 2015

A role is a collection of permissions defined for the whole system that you can assign to specific users in specific contexts. The combination of roles and context define a specific user's ability to do something on any page. The most common examples are the roles of student and teacher in the context of a course.

See also