Roles and capabilities: Difference between revisions

Latest revision as of 07:39, 30 May 2011

Moodle1.7

Roles and capabilities in Moodle 1.7 onwards provides great flexibility in managing how users interact. Prior to Moodle 1.7, there were only six roles possible: guest, student, non-editing teacher, editing teacher, course creator, and administrator. Whilst these roles may still be used, it's now possible to create additional roles, and to change what a given role can do in a particular activity.

Definitions

Role

An identifier of the user's status. The status depends upon permissions given for one or more capabilities in a context.

For example Teacher and Student are standard user roles. The identifier indicates they probably have different capabilities in some contexts.

When Moodle is first installed, a number of Standard roles are created automatically.

Capability

A description of a particular Moodle feature. A list of many capabilities can be seen in the capability category index page.

For example moodle/blog:create(writing blog entries) or "Backup course" are two capabilities. Note the "mod/blog:create" notation is a common to identify a capability.

Permission

A setting for a capability. Can be any one of four: not set/inherit, allow, prevent or prohibit.

Context

A "space" in Moodle.

For example: a course, activity module or block can each be a context.

Some contexts can contain multiple contexts in their space, For example, a course can contain a lesson, assignment, forum and quiz modules, plus blocks.

@@ Line 1: / Line 1: @@
-{{Roles}}
+{{Roles}}{{Moodle 1.7}}Roles and capabilities in Moodle 1.7 onwards provides great flexibility in managing how users interact. Prior to Moodle 1.7, there were only six roles possible: guest, student, non-editing teacher, editing teacher, course creator, and administrator. Whilst these roles may still be used, it's now possible to create additional roles, and to change what a given role can do in a particular activity.
-{{Moodle 1.7}}
-==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, authorized users may [[Manage roles|create]] any number of customized roles and assign them to users.  From 1.7, an organization may 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''.
+;Role
-*A '''capability''' is a description of a particular Moodle feature, for example ''[[Capabilities/moodle/blog:create|moodle/blog:create]]''. Capabilities are associated with roles.
+:An identifier of the user's status. The status depends upon permissions given for one or more capabilities in a context.
-*A '''permission''' is [[Manage roles#Permissions|a value that is assigned]] for a capability for a particular role, for example ''allow'' or ''prevent''.
+::For example Teacher and Student are standard user roles. The identifier indicates they probably have different capabilities in some contexts.
-*A '''context''' is a "space" in Moodle, such as courses, activity modules or blocks. Roles will only work if the role assignment is made at the correct context level. For example, a ''teacher'' role should be assigned at course context level, a ''forum moderator'' for a particular forum should be assigned at activity level, an ''administrator'' should be assigned at system level and so on.
+:When Moodle is first installed, a number of [[Standard roles]] are created automatically.
+;Capability
+:A description of a particular Moodle feature. A list of many capabilities can be seen in the [https://docs.moodle.org/en/Category:Capabilities capability category index page].
+::For example [[Capabilities/moodle/blog:create|moodle/blog:create]](writing blog entries) or "Backup course" are two capabilities.  Note the "<nowiki>mod/blog:create</nowiki>" notation is a common to identify a capability.
+;Permission
+:A setting for a capability. Can be any one of four: not set/inherit, allow, prevent or prohibit.
+;Context
+:A "space" in Moodle.
+::For example: a course, activity module or block can each be a context.
+::Some contexts can contain multiple contexts in their space, For example, a course can contain a lesson, assignment, forum and quiz modules, plus blocks.
-==Contexts==
+==See also==
-The list of contexts in hierarchical order is as follows:
+*[[Useful things a teacher can do with roles]]
-*System context - accessible via the administrator's block (no parent)
+*[[Development:Roles administration improvements for Moodle 2.0]]
-*Course category context - accessible via the course category page (parent = site)
+*[[How permissions are calculated]]
-*Course context - accessible via the course administration block (old admin block) (parent = course category or site)
-*Module context - accessible whilst updating the module (parent = course)
-*Block context - accessible when editing mode is on (parent = site or course)
-*User context - accessible via the Roles tab in the user profile (parent = site)
-Inheritance will kick in if a role is assigned at a higher level. For example assigning a ''teacher'' to a course category will make this user the teacher for ALL courses within the category.
-==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 (e.g. delete discussions or add activities).  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.
-==Roles in 1.8==
-{{Moodle 1.8}}
-In addition to many Roles fixes and refinements, Moodle 1.8 has separated the SYSTEM context from the SITE context (which makes it more like 1.6 used to work). The SITE context is the "front page course" and it's activities. This should make it easier for admins to set up permissions.
-==See also==
-*[[Development:Roles]]
 *[[:Category:Capabilities]]
 *Using Moodle [http://moodle.org/mod/forum/view.php?id=6826 Roles and Capabilities forum]
-*[http://tracker.moodle.org/secure/IssueNavigator.jspa?mode=hide&requestId=10221 Roles stuff fixed in 1.8]
-[[Category:Teacher]]
-[[Category:Administrator]]
 [[Category:Roles]]
+[[cs:Role]]
+[[es:Roles y capacidades]]
+[[eu:Rolak]]
+[[fr:Rôles et capacités]]
+[[ja:ロールおよびケイパビリティ]]
+[[ru:Роли и возможности]]
+[[de:Rollen und Rechte]]

Documentation

Roles and capabilities: Difference between revisions

Latest revision as of 07:39, 30 May 2011

Definitions

See also