MoodleDocs - User contributions [en]

Upload users

2018-06-15T09:36:10Z

Cathkdsc: /* Allow renames */

{{Accounts}}
==Uploading users via text file==

There are many options for uploading information (fields associated with a user) with this method: from enrolling users in multiple courses with course specific [[Roles|roles]] to updating user information in the [[User profile]] to deleting users from the site.

''Tip:'' It is usually not necessary to upload users in bulk with Upload users. To keep maintenance work down you should first explore forms of authentication that do not require manual maintenance, such as [[External database authentication|connecting to existing external databases]] or letting the users create their own accounts ([[Self enrolment]]). See [[Authentication]] for more information.

==File formats for upload users file==
The upload users file has fields separated by a comma (or other delimiter) ONLY - no space. The first line contains the valid field names. The rest of the lines (records) contain information about each user.

''Tip:'' Avoid special characters in field information like quotes or other commas. Test a file with only one record before a large upload.

''Tip:'' You can use a spread sheet program to create the file with the required columns and fields. Then save the file as "CSV (comma delimited)". These files can be opened with simple text editors (eg, [https://notepad-plus-plus.org/ Notepad++]) for verification.

===Valid upload file for testing===
Here is an example of a simple valid upload file:
(Column headers on the first line of the file are only highlighted in bold in this example to distinguish it from the rest of the of the data/user details), assuming you have already created the course 'math102' and the two cohorts of the proper names.

'''username,password,firstname,lastname,email,course1,group1,cohort1'''
jonest,verySecret3$,Tom,Jones,jonest@example.com,math102,Section 1,year 3
reznort,someSecret4#,Trent,Reznor,reznort@example.com,math102,Section 3,year 4

== User Fields that can be included==

''Tip:'' We strongly recommend that you test a file that contains fields you proposed to use with one user before attempting a file upload for the first time.

===Required fields===

These are the required user identification fields:
<code>username,firstname,lastname,email</code>
Validity checks are performed for:
* '''username''' can only contain alphabetical '''lowercase''' letters , numbers, hypen '-', underscore '_', period '.', or at-sign '@'
* '''email''' is in the form: ''name@example.com''

===Passwords===

The "password" field is optional if the 'New user password' setting on the upload screen is set to "Create password if needed and send via email" but is required if the setting to "Field required in file".

If included, values should meet the requirements for the site's [[Site_policies#Password_policy|Password policy]].

To force password change for a particular user, set the password field to '''changeme'''. If omitted, a password will be generated for each user (during the next Cron job) and welcome e-mails sent out. The text for the welcome e-mail is in the language settings in ''Site administration > Language > Language customisation'' with a String identifier of 'newusernewpasswordtext'.

===Optional user fields===

Note: Commas within a field must be encoded as &#44 - the script will decode these back to commas.
Tip: For Boolean fields with only two values, use '''0''' for false and '''1'''for true.

To provide values other than the default you can include one or more of these optional user fields:

<pre>institution,department,city,country,lang,auth,timezone,idnumber,icq,phone1,phone2,address,url,description,mailformat,maildisplay,maildigest,htmleditor,autosubscribe,interests</pre>

Most of the these are user profile fields or user preference fields that belong to the user profile and are the filled in the user or at manual creation. Some however require specific formats:

See [[Additional name fields]] for more details. Key things to note are:

'''country''' - use the country TWO LETTER CODE, in upper case, eg AU,ES,GB,US. These are all UPPER CASE. Using "au" or "es" or "USA" as a country code will result in a database error. If you are having trouble working out the two-letter code for a country, you can consult the list of [http://www.iso.org/iso/country_names_and_code_elements country names and code elements] available on the ISO Website. A common error is to use UK for United Kingdom; it should be GB.

'''lang''' - use the two letter (or extended four lettter) code as defined in the Moodle language packs, e.g. en, es, en_us, de, in ''Site administration > Language > Language packs''.

'''auth''' - The auth field must be used if the site uses an alternative authentication method, such as LDAP, as otherwise the authentication method will default to manual and users using a different auth method won't be able to log in. Use the shortname codes defined in Plugins > Authentication for the various types, e.g. manual, nlogin, ldap, cas, mnet, db, none. If you do not include an auth column, then newly created users will be created with the manual account type.

'''timezone''' - Should be in the format as found in the Location settings in terms of Zone/Region, eg. Australia/Sydney, Asia/Kathmandu, Europe/Madrid, etc. The entry is case sensitive so Europe/London will work but europe/london will not.

NOTE: Needed: settings for '''mailformat''','''maildisplay''','''htmleditor''','''autosubscribe'''

'''maildigest''' To prevent users from receiving a large number of emails from courses or forced subscription forums use the '''maildigest'''. The options for this field are 0 = No digest, 1 = Complete digest and 2 = Digest with just subjects.

===Custom profile field names===

These are optional and depend on whether you have created any custom profile fields in your site. The name of the header in file is of the form 'profile__field_xxxxx' where xxxx is the unique shortname of custom user profile field name as you created it.

The field name should match the case of the profile field shortname. So, for instance if the shortname of your custom profile field is all upper case, for example, ''DOB'', then use a header of ''profile_field_DOB'' to match the case, not ''profile_field_dob'', which will produce a "is not a valid field name" error. Likewise, a mixed case shortname such as ''Dob'' should have a header of ''profile_field_Dob''. (The exception to this is if the shortname is all lower case, then any case will work in the field header, which is a historical quirk: but best practice is to match the case and you will avoid errors.)

<pre>profile_field_xxxxx</pre>

'''Example''': To create a custom field "genre", you must write a shortname "genre" in the new field, and write "profile_field_genre" in the header of the .csv file.

For custom profile fields that are dates, use the ISO standard format YYYY-MM-DD, eg. 2014-06-19 which will then be properly localized in the interfaced. For example, a field called dohire for date of hire, the fields could be:
<pre>
username,firstname,lastname,email,profile_field_dohire
blumbergh,Bill,Lumbergh,blumbergh@example.com,1990-02-19
pgibbons,Peter,BGibbons,pgibbons@example.com,1996-06-05
tsmykowski,Tom,Smykowski,tsmykowski@example.com,1970-01-01
</pre>

For custom profile fields that are a menu, use the corresponding value in the menu list from field as you defined it. For example: a custom field 'corporatedivision' with one of three values 'Management', 'Development' or 'Training'. Just insert one of those three words (e.g. 'Training') as the value for that field. Eg.

<pre>
username,firstname,lastname,email,profile_field_corporatedivision
blumbergh,Bill,Lumbergh,blumbergh@example.com,Management
pgibbons,Peter,BGibbons,pgibbons@example.com,Development
tsmykowski,Tom,Smykowski,tsmykowski@example.com,Training
</pre>

=== Special user change fields===

Three special fields are used for managing user accounts, '''oldusername''', '''deleted''' and '''suspended'''. [[#Allow_renames|See below for details]].

===Enrolment fields===

You may optionally enrol users in already existing courses using manual enrolment. Only manual enrolment is done this way; if the manual enrolment method is disabled in a course, then no enrol is done.

You use fields in the upload file of this type:

<pre>course1,type1,role1,group1,enrolperiod1,enrolstatus1,course2,type2,role2,group2,enrolperiod2,enrolstatus2</pre> etc.

Header fields '''must''' have a numeric suffix such that type1,role1,group1,enrolperiod1 and enrolstatus1 all apply to course1 for course'''1''' to course'''n'''. Even if you are just doing one course enrolment, you must still use the numer 1 on the heading name, i.e. course1,role1, etc. Do not use the bare headings without numbers, e.g. course,role, etc as those will generate an error.

'''course#''' is the shortname of the course, if present the user will be enrolled in that course. Do not use the fullname of the course or it will generate an error. This field is the ONLY required field for a succesful enrolment. All the others are optional.

'''type#''' sets the role to be used for the enrolment. A value of 1 is default course role, 2 is legacy Teacher role and 3 is legacy Non-editing Teacher.

'''role#''' may be used to specify roles directly, using either role short name or the role id (numeric names of roles are not supported). Usually you will use the role name that is the shortname of the role as defined in Users > Permissions > Define roles, eg. student, editingteacher. If the role column is left out, the users will be enroled in the course with the default role, which is normally student.

'''group#''' may be used to assign users to groups in course, using name or id (numeric group names are not supported). NOTE: if the group does not already exist, it will be created.

'''enrolperiod#''' may be used to set the enrolment duration, in days, for each course. If not explicitly set here, all the users will get the duration as set in the Manual enrolment method of the course (which defaults to 0 meaning unlimited.)

'''enrolstatus#''' is optional as by default all newly enrolled users are set to active. If used a value of 1, it will suspend users in the course and if a user is previously set as inactive / suspended then a value of 0 will unsuspend them and make them active again.

=== Cohort membership assignment===

You can assign users to any already existing Cohort by using only the "username" and the "Cohort ID" with just two fields in the file. Note that this is an exception to the usual case where the firstname, lastname and email address of the user are required.

'''cohort#''' is the form to use and like enrolment in courses, you have to add a number to each header, so cohort1,cohort2, etc.

Internal cohort id numbers or non-numeric Cohort IDs of existing cohorts must be used; do not use the full name are not allowed. (Note that cohort id is what is usually known elsewhere as the "shortname".)

Here is a sample CSV file:

<pre>
username,cohort1,cohort2
student1,nursing,2016class
student2,nursing,2014class
student3,nursing,2014class
</pre>

=== MNet ===

Existing [[MNet]]users can be added to courses, groups or cohorts as below by using the field header '''mnethostid'''

#enrolling to courses: username+mnethostid+course required
#adding to group: username+mnethostid+course+group required
#adding to cohort: username+mnethostid+cohort required
#suspending/reviving accounts: username+mnethostid+suspended required

All other operations are ignored. You can not add users, delete them or update them (such as change names or email, profile fields, etc.)

=== Set system roles ===
Users may also be assigned to already defined system roles, using the shortname of the system role as defined in ''Site administration > Users > Permissions > Define roles'' for roles with a system context defined.

<code>sysrole1,sysrole2,sysrole3</code> etc

Users may be uploaded to a system role (usually Manager or Course creator) by entering the shortname of that role. Other roles can only be uploaded if they have already been assigned in the 'system' context. See [[Creating custom roles]]. Multiple roles can be assigned using sysrole2, sysrole3, etc. fields. Note that the number suffix in no way relates to the number suffixes on the enrolment fields. The numbers must go up in sequence starting at 1.

Unassigning system roles
Users can also be removed from a given system role by entering the shortname of that role prefixed with a minus symbol: '-'. If the user is currently assigned to that role, they are removed from it. If the user is not currently assigned to that system role, the field value is ignored. However, the field value must refer to a system role that does exist on the system, otherwise an error will occur.
[[File:GlobalRoles1.png|thumb|500px|center|Example of a file for uploading users with global/system roles]]

==Upload user process==

# Create file for uploading
# Go to ''Site administration > Users > Accounts > Upload users''
# Add file to upload
# Upload users preview - check settings and default user profile settings
# Upload users preview - click "Upload users"
# Upload users results - shows list of users, exceptions made in upload and summary of number of users
# Upload users results - click "Continue"
# Returns to Upload users screen

==Updating users preview==
There are various settings to better control the desired upload behaviour. These settings are found on the "Upload users preview" page.

'''Warning''': errors updating existing accounts can affect your users badly. '''''Be careful''''' when using the options to update.

====Upload type====
The Upload type specifies how to handle existing accounts.

;Add new only, skip existing users : is the default Moodle upload type. It creates a new user account for each new record in the uploaded file. If an existing username is found in the uploaded file matches an existing username, that record is '''skipped'''. By skipping the existing user account, the data in the existing record is not touched (in contrast to the "Add new and update existing users" option) and a second new user account is '''not''' created (in contrast to the "Add all, append number to usernames if needed" option).

;Add all, append number to usernames if needed : creates a new user account for each record in the uploaded file. If an existing user account is found, a new account will be created with a number appended to the username. For example, if a user account for username 'jsmith' already exists and a new record in the uploaded file contains a record forusername 'jsmith' an additional user account is created with a 1 '''appended''' to the username to produce user 'jsmith1'.

;Add new and update existing users : creates a new user account for each new user in the upload file. If an existing user account with the same username is found, the account information is '''updated''' by the data in the uploaded file.
;Update existing users only : ignores any new users found in the upload file and updates the user account if a matching username record is found in the uploaded file.

====New user password====
When creating a new user account Moodle can create a new password (if one is not provided) or require a password in the uploaded file.

;Create password if needed : creates a default password for the new user account if one is not provided in the uploaded file.

;Field required in file : requires that a password be provided in the uploaded file in order. If a password is not provided, an error is generated and the user account is not created.

====Existing user details====
The Existing user details options are only available when the Upload type allows existing user accounts to be updated. It specifies how Moodle should process user detail information for existing users.

;No changes : ignores user detail data in the uploaded and leaves the existing user account data unchanged.
;Override with file : overwrites data in the existing user account with the data provided in the uploaded file.
;Override with file and defaults : overwrites data in the existing user account with data provided in the uploaded file and fills in the default values for existing user details when no data is provided in the uploaded file.
;Fill in missing from file and defaults : adds data in the existing user account with data provided in the uploaded file if the field is empty (does not already contain data) and fills in the default values for existing user details when no data is provided in the uploaded file.

====Existing user password====
The Existing user password option specifies how to handle password data for existing user accounts when Existing user details is set to overwrite data.
;No changes : ignores password field in the uploaded user file and leaves the existing user account password untouched
;Update : overwrites the existing user account password with the password provided in the uploaded file

====Force password change====
The Force password change option specifies when to tag a user account so that the next login attempt will require the user to change the user's password.

;Users having a weak password : If the user account has a weak password as defined by the site's [[Password_policy#Password_policy|Password policy]] then the user will be forced to change the password during the next login attempt. This option is not shown if there the site does not have a [[Password_policy#Password_policy|Password policy]].
;None : None of the users in the uploaded file will be forced to change the password during the user's next login attempt.
;All : All of the users in the uploaded file will be forced to change the password during the user's next login attempt.

====Allow renames====
If the uploaded file contains the special '''oldusername''' field, it is possible to rename a user from the '''oldusername''' to a new '''username'''. The default setting is to '''not''' allow renames. Keep in mind that renaming a user will require the user to use the new username when logging in.
;No : ignores the '''oldusername''' field and leaves the existing user account's username field unchanged.
;Yes : allows the existing user account's username to be changed by the data provided in the uploaded file's username field. The '''oldusername''' will be searched for and then updated with the data provided in the username column.

====Allow deletes====
If the uploaded file contains the '''deleted''' special field, it is possible to use the upload file to delete existing user accounts. The default setting is to '''not''' allow deletes. Keep in mind that deleting a user account will prevent that user from logging in. As a protection, site administrator user accounts cannot be deleted with this method.
;No : ignores the '''deleted''' special field in the uploaded file and leaves the existing user account unchanged
;Yes : allows the existing user account to be deleted when the value of the of the '''deleted''' field is 1.

====Allow suspending and activating of accounts====
If the uploaded file contains the '''suspended''' special field, it is possible to use the upload file to either suspend or make active (unsuspend) existing user accounts. The default setting is to allow suspending/activating of existing user accounts. Keep in mind that suspending an existing user account will prevent that user from logging in.
;Yes : allows the existing user account to be suspended when the value of the of the '''suspended''' field is 1.
;No : ignores the '''suspended''' special field in the uploaded file and leaves the existing user account status unchanged.

====Prevent email address duplicates====
It is possible, but '''not''' recommended to upload users with duplicate email addresses. By default, uploading users with duplicate email addresses is prevented. To allow duplicate email addresses, go to Site administration ► Plugins ► Authentication ► Manage authentication. You can tick "Allow accounts with same email". Then on the upload users screen you will be allowed to change the "Prevent email address duplicates" setting.

However, doing this is not recommended for file uploads. Test thoroughly any user uploads before implementing.

For more info, see the [[Managing_authentication#Allow_accounts_with_same_email|Managing authentication]] docs page
;Yes : prevents user accounts from being created from the uploaded if an existing user account already has the same email address as found in the uploaded file's '''email''' column.
;No : allows user accounts to be created if an existing user account already has the same email address found in the uploaded file's '''email''' column.

====Standardise usernames====
Standardise usernames is used by default to convert the username to all lower case and to strip out illegal characters. It is possible to not standardise the usernames; however, doing so is '''not''' recommended.
;Yes : standardises usernames found in the uploaded file before updating existing or creating new user accounts so that the username contains only lowercase letters and numbers.
;No : skips standardising usernames found in the uploaded file so that the newly created or updated usernames will be exactly as they are in the uploaded file ('''not recommended''').

For those seeking a more technical explanation, the process for standardising the usernames consists of ensuring the characters are all UTF-8 (fix_utf8) encoded, converting the username to lower case, and then stripping out non-letters/non-number characters (unless ''Site administration > Security > Site policies > Allow extended characters in usernames'' is set on) with something similar to:

<code>$username = preg_replace('/[^-\.@_a-z0-9]/', '', $username);</code>

====Select for bulk user actions====
After the uploaded file has finished being processed (all new accounts have been created and existing accounts updated as specified by the previous settings), there is an option to select some of those user accounts to perform additional [[admin/user/user_bulk|bulk user actions]] such as
*Confirm user accounts created through Email-based self-registration which are not yet confirmed by the user
*Send a message (requires Messaging to be enabled)
*Delete user accounts
*Display a list of users on a page
*Download user data in text, ODS or Excel file format
*Force users to change their passwords
*Add users to a cohort

By default, no users are selected for [[admin/user/user_bulk|bulk user actions]].

;No : No users are selected for [[admin/user/user_bulk|bulk user actions]]
;New users : Only newly created users are selected for [[admin/user/user_bulk|bulk user actions]]
;Updated users : Only updated user accounts are selected for [[admin/user/user_bulk|bulk user actions]]
;All users : All users found (existing updated users and newly created user accounts) in the uploaded file are selected for [[admin/user/user_bulk|bulk user actions]]

===Default values===

You can provide default user values for some fields not included in the uploaded file. Some fields include:
*Email display
*Forum auto-subscribe
*City/town
*ID number
*Institution
*Department

==Upload user results ==
After accepting the preview settings by clicking on "Upload users", you should see the the Upload users results screen.
[[File:Upload users results 2.0.JPG|thumb|center|The results screen; everything went well!]]
This screen will show you any exceptions or changes that were made to each user in the upload process. For example if you were updating user information, the updated information will be shown. Or if a user was not added that record will be highlighted.

The screen will summarize how many users were uploaded or updated, indicate the number of weak passwords and the number of errors.

==Advanced potentials of Upload user==
===Templates===

''Note: This section needs checking and updating if necessary for Moodle 2.0. Please do so and remove this note when finished.''

The default values are processed as templates in which the following codes are allowed:

* %l - will be replaced by the lastname
* %f - will be replaced by the firstname
* %u - will be replaced by the username
* %% - will be replaced by the %

Between the percent sign (%) and any code letter (l, f or u) the following modifiers are allowed:

* (-) minus sign - the information specified by the code letter will be converted to lowercase
* (+) plus sign - the information specified by the code letter will be converted to UPPERCASE
* (~) tilde sign - the information specified by the code letter will be converted to Title Case
* a decimal number - the information specified by the code letter will be truncated to that many characters

For example, if the firstname is John and the lastname is Doe, the following values will be obtained with the specified templates:

* %l%f = DoeJohn
* %l%1f = DoeJ
* %-l%+f = doeJOHN
* %-f_%-l = john_doe
*<nowiki> http://www.example.com/~%u/</nowiki> results in <nowiki>http://www.example.com/~jdoe/</nowiki> (if the username is jdoe or %-1f%-l)

Template processing is done only on default values, and not on the values retrieved from the CSV file.

In order to create correct Moodle usernames, the username is always converted to lowercase. Moreover, if the "Allow extended characters in usernames" option in the Site policies page is off, characters different to letters, digits, dash (-) and dot (.) are removed. For example if the firstname is John Jr. and the lastname is Doe, the username %-f_%-l will produce john jr._doe when Allow extended characters in usernames is on, and johnjr.doe when off.

When the "New username duplicate handling" setting is set to Append counter, an auto-increment counter will be append to duplicate usernames produced by the template. For example, if the CSV file contains the users named John Doe, Jane Doe and Jenny Doe without explicit usernames, the default username is %-1f%-l and New username duplicate handling is set to Append counter, then the usernames produced will be jdoe, jdoe2 and jdoe3.

===Deleting accounts===

If the '''deleted''' field is present, users with value 1 for it will be deleted. In this case, all the fields may be omitted, except for '''username'''. After uploading the file, be sure to change the "Upload type" to "Update existing users only" and the "Allow deletes" option to "Yes".

''Tip:'' A similar field is available for '''suspended'''. This enables a user account to be temporarily disabled rather than completely removed.

Deleting and uploading accounts could be done with a single CSV file. For example, the following file will add the user Tom Jones and delete the user reznort:

username,firstname,lastname,deleted
jonest,Tom,Jones,0
reznort,,,1

==Encoding file format==
On the initial Upload user screen, you may select the file encoding format from a pull down list. These include UTF-8 (the default), ASCII, ISO-8859-1 to ISO-8859-11 or any one of over 36 formats.

==Hints==

===Spreadsheet===

If you use a spreadsheet program such as Excel to create your .csv file, check the resulting output in a text editor before you upload it. It is possible to get trailing commas on each line from an empty field if you have added and deleted columns of information prior to saving the final file. Also check the character encoding. A csv file is a simple text file (ASCII or Unicode) that can be used to upload user accounts.

Excel translates passwords that begin with - (minus) or + (plus) as zero. Even when saving as .csv and saying "Yes" to "Keep this format, and leave out any incompatible features." Check for this before uploading, as a zero halts the upload process.

If you use a formula in Excel to create fields (for example, the concatenate function to create a user name), then remember to copy the cells with the formula and use special paste with values checked to make them into an acceptable data for a csv file.

The upload will also fail if you have trailing spaces at the end of your data fields. Often, this can not be removed with a simple Find " " and Replace with "". If information has been copied from web sources than it is possible to include non-breaking spaces which will prevent your upload from being completed correctly. To find these invisible spaces, use the Find and Replace function in Excel. In the find field, hold alt and type 0160. Leave the replace field blank.

===Field size limits===
Some fields have maximum character lengths, as defined in the database fields. Typically the file will import to the preview list screen but not finish the process. Turn on debug to see the fields that are too long. The error will be "User not added - error".

The sizes of some common fields, in number of characters, are currently (3.2):

*username - 100
*password - 255
*idnumber - 255
*firstname - 100
*lastname - 100
*lastnamephonetic - 255
*firstnamephonetic - 255
*middlename - 255
*alternatename - 255
*institution - 255
*department - 255
*address - 255
*city - 120
*icq -15
*skype - 50
*yahoo - 50
*aim - 50
*msn - 50
*phone1 - 20
*phone2 - 20

===All user fields listed here===
:All the user fields that are valid in an upload file are listed below, except for any custom fields you may have created (for which see below.)

<pre>firstname,lastname,username,email,password,auth,idnumber,institution,department,city,country,timezone,lang,mailformat,maildisplay,maildigest,htmleditor,autosubscribe,skype,msn,aim,yahoo,icq,phone1,phone2,address,url,description,descriptionformat,interests,oldusername,deleted,suspended,alternatename,lastnamephonetic,firstnamephonetic,middlename</pre>

The enrolments into courses information are <pre>course1,type1,role1,group1,enrolperiod1,enrolstatus1</pre>
where each enrolment is grouped by number.

===Capabilities===

You may wish to create a limited role to allow some users access to this function. Create a role and assign to the user at the system/site level with the following capabilities allowed
* moodle/site:uploadusers
* moodle/role:assign
* In 'Allow role assignments' permit this new role to assign the required roles

In particular, don't forget the moodle/role:assign capability (even if these users have it in the courses they will be enrolling users in - it won't work).

== See also ==
* [http://youtu.be/PFGLZnuu_JI Adding users by using a CSV in Moodle] MoodleBites video on YouTube
*[[Flat file]] enrolment
* [[User profile fields]] for details of how to include data about custom user profile fields in the upload users file
* [[Upload courses]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=36851 Can I auto enroll from Excel?]
*[http://moodle.org/mod/forum/discuss.php?d=97903 Uploading users to custom roles]
*[http://moodle.org/mod/forum/discuss.php?d=181259 User upload option: standardise usernames]
*[http://moodle.org/mod/forum/discuss.php?d=144569 Matriculacion con flat file csv] - discussion in Spanish

[[fr:Importer des utilisateurs]]
[[ja:ユーザのアップロード]]
[[de:Nutzerliste hochladen]]
[[es:Subir usuarios]]

Using Forum

2017-08-03T17:11:30Z

Cathkdsc: /* Using groups with forums */

{{Forum}}
This page contains extra information for students and teachers about using the forum activity.

==For all users==
===Permalinks===

A permalink allows you to link directly to a specific forum post so you can share it easily with others. You will see the permalink option when clicking to reply to a post. If you click the permalink ''(1)'', it is highlighted to the side ''(2)'' and you will have a particular web address ''(3)'' which you can then copy and paste to use elsewhere:

[[File:permalinkexample.png|thumb|center|600px|Linking directly to a single post]]

===Forum preferences===
Users can set their forum preferences via Preferences in the user menu top right. (Defaults for each of these settings can be set by an administrator in ''Administration > Site administration > Accounts > User default preferences''.)

===Track read and unread forum posts===
*Access the Preferences page from the user menu and select 'Forum preferences'.
* For 'Forum tracking', choose ''Yes: highlight new posts for me'' and if the forum administrator has set the 'Read tracking for this forum?' to On or Optional then unread posts will be highlighted for you:
{|
|[[File:forumtracking1.png|thumb|296px|left|Unread posts alert]]
|}

The posts will be highlighted in the following places:

* Dashboard
* Course page
* Within the forum itself
* In forum discussion threads
{|
|[[File:forumtracking2.png|thumb|447px|left|Click to mark as read]]
|}

Only posts made in the last two weeks are tracked as read or unread. Older posts are all reported as read.

'''New in 3.2:''' You can also choose to have any forum post notifications automatically marked as read (so they don't appear in the Unread list.) Some people find this confusing and prefer to keep them as unread:

{|
|[[File:forumnotificationsread.png|thumb|left|600px|Forum post notification options]]
|}

===Display options===
[[Image:forumviewoptions.jpg|thumb|Reply display options]]A discussion thread may be displayed in four ways. Use the pull down menu at the top of each forum discussion to select a display type.

* Display replies flat, with oldest first
* Display replies flat, with newest first - The discussion will be displayed in one line and the chronological order from the newest to the oldest. This is the same as the above, just a different sort order.
* Display replies in threaded form - Only the post starting the discussion will be displayed in its full form; replies will be reduced to the headlines (including information about its author and date of release) and organised chronologically; moreover, replies will be shifted towards the right so that only replies to the same post were in the same line.
* Display replies in nested form - All posts are displayed in their full forms; replies will be reduced to the headlines (including information about its author and date of release) and organised chronologically; moreover, replies will be shifted towards the right so that only replies to the same post were in the same line.

{|
| [[Image:Forum Flat form mu.png|thumb|Flat Forum discussion, example from middle]]
| [[Image:Forum threaded form mu.png|thumb|Posts in threaded form]]
| [[Image:Forum nested form mu.png|thumb|"Nested reply example"]]
|}

===Forum posting===

The default content of '''Subject''' is usually 'Re: <the name of the 'parent' post>'. You can change it though.

==== Adding images, sound and video ====

*When an image is "attached" as a file to a forum message, it is immediately displayed full size after the message (i.e. no need to click on an attachment). This an excellent way of sharing images without having to go through the process of uploading them as files and linking them from within web pages.
*Images may be dragged and dropped into the box as well as uploading via the "add" link and the [[File picker]].
*If multimedia filters are enabled, a sound file (mp3) or accepted video file can be attached and it will be embedded into the forum post in an appropriate player.

====Post editing time limit====
Once a post has been made, students can go back and edit it within set time limit. This is usually 30 minutes and is set by an administrator in ''Site administration > Security > [[Site policies]]'. Note that teachers can always edit their posts.

====Moving between forum threads====

Links top and bottom left and right (where applicable) take you to the previous and next forum discussion in a list:

[[File:navigateforums1.png|thumbnail|center|500px]]

===Post a copy to all groups===

Teachers and other users with the [[Capabilities/mod/forum:canposttomygroups|capability to post in all groups they have access to]] can post the same message once only to all groups by selecting 'All participants' and clicking the Add a new discussion topic button:

[[File:forumdiscussiongroup1.png]]

Once they have typed the post, they tick the box 'Post a copy to all groups':

[[File:forumdiscussiongroup2.png]]

When saved, the post will be reproduced for each group:

[[File:forumdiscussiongroup3.png]]

===Reply to posts via email===

If enabled by an administrator (in [[Mail configuration]]), you can reply to forum posts via email.

# Click the Reply by email link in the email. You will see a special unique email address to send your reply to.
# Reply using the email address provided. '''IMPORTANT: Make sure you remove the original email content so that your forum post does not contain the quoted text.'''
# You should receive an email saying your reply has been successfully posted.
# Your post now appears in the forum.

{|
| [[File:forumemailreplylatest.png|thumb|400px|(1) Click to reply by email]]
| [[File:specialemailaddress.png|thumb| 300px|(1a) Note the special email address to reply to]]
| [[File:forumemailreply2.png|thumb|400px|(2) Type and send your reply]]
|}

{|
| [[File:forumemailreply3.png|thumb|400px|(3) The success message]]
| [[File:forumemailreply4.png|thumb|400px| (4) Your reply is posted to the forum]]
|}

[[File:navigateforums1.png|thumbnail|center|500px]]

===Exporting forum posts===
Users with the ''mod/forum:exportdiscussion'' or ''mod/forum:exportownpost'' or ''mod/forum:exportpost'' permission can export forum posts to any portfolio the administrator has enabled:

[[File:Exportforum.png]]

See the discussion [https://moodle.org/mod/forum/discuss.php?d=320382 Printing/exporting forum discussions] for further details.

==For teachers==

===Pinned posts===

When adding a new discussion as a teacher, you can make it 'sticky' by ticking the box to 'pin' the discussion to the top of the list. Any forum discussions which come after that will appear underneath this pinned post. If you later untick the box to 'unpin' it, it will display as a regular forum discussion, moving down the list when others are posted.

[[File:pinnedpostexample.png]]

==='Send forum post notifications with no editing time delay'===

Teachers (and others with the [[Capabilities/moodle/course:manageactivities|capability to manage course activities]]) will see this option when posting to a forum. Ticking this box will send a notification to everyone subscribed to that forum with no editing time delay. (Users normally have 30 minutes to edit their posts.)

Note: For users who have enabled email digests in their forum preferences, the notification is NOT sent separately from other forum post notifications.

=== Display period ===

Teachers (and others with the capability [[Capabilities/mod/forum:viewhiddentimedposts|mod/forum:viewhiddentimedposts]]) can set a display period of a date and time for the forum post to appear.

[[File:timedposts.png]]

Note: Timed forum posts was included in previous versions of Moodle as an experimental feature. In Moodle 3.1 onwards it is enabled by default for new installations. For sites upgrading from a previous version, it may be enabled via ''Site administration > Plugins > Activity modules > Forum''.

===Locking a discussion===
{{New features}}

Forum threads may be automatically locked after a certain period of inactivity. This is done from the setting 'Discussion locking' when creating or editing a new forum.

*A period from a day to a year may be selected. The default is for discussions not to be locked.
*Watch the screencast [https://youtu.be/M9ZxCq50hiQ Discussion locking] to see a demonstration.
*Teachers and other users with the [[Capabilities/mod/forum:canoverridediscussionlock|capability to override locked discussions]] can unlock discussions simply by posting a reply.

===Moving a discussion===

Teachers and other users with the [[Capabilities/mod/forum:movediscussions|capability to move discussions]] can move a discussion to any other forum in the course for which they have appropriate rights.
# Click on the arrow in the 'Move this discussion to...' dropdown menu in the top right corner of the page and select a destination forum.
# Click the Move button.

Note: Moving a forum post will display incorrect results in the [[Participation_report|course participation report]] for the affected forums. For example, take a student who posted in forum A and had their post moved to forum B. In the course participation report the student will still be listed has having made a post in forum A, but will not be listed as having made a post yet in forum B.

Note: Discussion subscriptions are retained when a post is moved.

===Splitting a discussion===

Teachers and other users with the [[Capabilities/mod/forum:splitdiscussions|capability to split discussions]] can split a discussion thread. Splitting a discussion means that beginning with the post selected and going to the end of that sub-thread, the posts are cut from the current discussion topic and put into a newly created discussion topic. If discussion has strayed away from the original topic, splitting the discussion can provide new attention and space for the tangent discussion while keeping the original discussion on topic.

# Click the link 'Split' in the forum post
# Enter a new discussion name (optional)
# Click the Split button

Note: Discussion subscriptions are NOT retained when a post is split.

===Using groups with forums===
'Group mode' available from the Common module settings has three options. (Note that you must have groups in your course to use this feature.)

If the group mode is set to '''separate groups''':

* Teachers are given the option of adding a new discussion topic for all participants or for a selected group. If a teacher adds a new discussion topic for a selected group, then only group members can reply to it.
* Students can only start discussions for their own group.
* Students can only reply to discussions started by other group members or discussions for their own group started by a teacher.

If the group mode is set to '''visible groups''':

* Teachers are given the option of adding a new discussion topic for all participants or for a selected group. If a teacher adds a new discussion topic for a selected group, then only group members can reply to it.
* Students can only start discussions for their own group.
* Students can only reply to discussions started by other group members or teachers.

Teachers, and other users with the capability [[Capabilities/moodle/site:accessallgroups|moodle/site:accessallgroups]] set to allow, can view and post in all forum discussions, regardless of the group mode setting.

Where visible groups are used, the user's own groups will be shown first in the list, followed by other groups:

[[File:mygroupsfirst.png]]

Note: Single simple discussions cannot be set to separate groups (as this feature is not implemented). Instead, a standard forum should be used. If required, a permissions override may be set to prevent students from starting new discussions.
For teachers who have access to all or several groups in a forum, this setting allows them post the same message once only to all groups.

Where teacher have access to several groups, they can post the same message once only to all the groups they have access to by selecting 'All participants' and clicking the Add a new discussion topic button:

[[File:forumdiscussiongroup1.png]]

Once they have typed the post, they tick the box 'Post a copy to all groups':

[[File:forumdiscussiongroup2.png]]

When saved, the post will be reproduced for each group:

[[File:forumdiscussiongroup3.png]]

===Ideas for using forums===

Ask yourself

# you wish to have involvement in the forum or if you want the students to lead and own the space
# you want the forum to add value to the face to face environment or have a life of its own in its own right outside the lecture theatre/classroom or seminar room
# you are prepared to make appropriate contributions to the discussion in order to:
## encourage discussion if students are quiet
## help shape ideas if students begin to wander off-task
## your role will be defined as discussions/a course progresses
## you will explicitly but gradually relinquish control of the discussions
## you will encourage and support learners to share control of discussions(for example you might ask a learner/group of learners to summarise contributions to a discussion thread/topic or you might ask learners to initiate discussion topics)
(WIP)

[[de: Forum nutzen]]
[[fr:Afficher un forum]]
[[ja:フォーラムの閲覧]]
[[es:Usando Foro]]

Cohort sync

2017-06-15T11:37:24Z

Cathkdsc:

{{Enrolment}}
==About cohort sync==
Cohort sync is for automatically enrolling members of a cohort in a course. If a user is added or removed from the cohort, they are automatically enrolled or unenrolled respectively. In other words, cohort sync synchronises cohort membership with course enrolment.

==Enabling cohort sync==

To use cohort sync, it must be enabled by an administrator in ''Site administration > Plugins > Enrolments > Manage enrol plugins''.

==Enrolling a cohort in a course==

To enrol a cohort in a course

# Go to ''Course administration > Enrolment methods'' and select 'Cohort sync' in the dropdown menu.
# Choose the required cohort and then click the 'Add method' button.

Teachers can add cohorts to courses by default but a manager or admin can hide certain cohorts from teachers by unchecking the 'Visible' box in the Cohort settings or by clicking the 'eye' icon on the Cohorts screen.

[[File:enrolmentmethods29.png|thumb|center|300px]]

Enrolling cohorts this way means that if members are added or removed from the cohort they are added or removed in the course too - ie, enrolment is synchronised.

{|
|[[File:cohort29.png|thumb|center|500px]]
|}

[[File:cohortcreatenewgroup.png]]

When synchronising a cohort it is also possible to automatically add all cohort members to the group. A new group can also be created when adding the cohort.

===Capabilities===
The required capabilities for setting up a cohort sync are:
* moodle/course:enrolconfig in the course context
* enrol/cohort:config in the course context
* moodle/cohort:view in the course context

The default "Teacher" (editingteacher) role has all these capabilities.

==See also==

* [[Cohorts]] for information on how to create a cohort
* [https://moodle.org/plugins/view.php?plugin=enrol_groupsync Enrolment: Cohort members to group] plugin for users already enrolled via different method

[[de:Einschreibung über globale Gruppen]]
[[es:Sincronización de cohorte]]
[[ja:コーホート同期]]

Workshop activity

2017-04-28T13:13:37Z

Cathkdsc:

{{Activities}}
{{Note|New to Workshop? Try our [[Workshop quick guide]].}}
Workshop is a powerful peer assessment activity. The documentation on [[Workshop settings]] explains the different options available.

Students submit their own work and then receive a number of submissions from other students which they must assess according to the teacher's specifications. (They may also assess their own work if the teacher requests this.) Text may be typed directly into Moodle's editor, or files of any type may be uploaded, as long as others have the software to view them. See '''[[Using Workshop]]''' for details of the phases involved. The teacher can decide whether to show or hide the identities of the students to each other when assessing is taking place.

Two grades are given and appear in the Gradebook: a grade for the student's own submission and a grade for the quality of their peer assessment skills. See [[Workshop grading strategies]] for more information.

Workshop is primarily a student-focused activity; however, the teacher may guide the students by providing example submissions for them to try out before assessing their peers and at the end of the workshop the teacher may publish some good (or less good) examples.

For a working example of a workshop activity, see the [http://school.demo.moodle.net/course/view.php?id=59 Celebrating Cultures course in the School Demonstration site.] with the username ''teacher'' and password ''moodle.''

https://www.youtube.com/embed/8QypkOcAEaE

==See also==

* [[Workshop FAQ]]

[[de:Workshop]]
[[es:Actividad de taller]]
[[fr:Atelier]]

Event monitoring

2017-03-30T14:13:24Z

Cathkdsc: /* What is event monitoring? */

{{Course reports}}

==What is event monitoring?==
*Event monitoring allows admins and teachers to receive notification when certain events happen in Moodle. See [[Events list]] for examples of events and their levels. Note that students may also be allowed to subscribe to rules if they are given the capability ''tool/monitor:subscribe''. It is not recommended that they be allowed to create or manage rules.
*To do this, a 'rule' needs to be created for the event to be monitored and then a user, such as the admin or teacher will need to subscribe to it to be notified.
*The rule will specify what the event is and how often it must happen before notification is sent to the subscriber. The notification may be pop-up, email or other chosen methods.
*A teacher can create a rule from ''Course administration > Reports > Event monitoring rules'' and an administrator can, additionally, create a rule from ''Site administration > Reports > Event monitoring rules.''
*You can subscribe to available rules via the user menu ''Preferences > Event monitoring''.

http://youtu.be/YkuK2w1lJnk

==Enabling event monitoring==

Event monitoring is disabled by default because of performance issues. An administrator can enable it from ''Site administration > Reports > Event monitoring rules''.

==How to create or manage a rule==

As a course teacher, go to ''Course administration > Reports > Event monitoring rules'', or as an admin go to ''Site administration > Reports > Event monitoring rules''.

===Rule name===

You can call the rule what you like but it should be something others will understand as they may wish to subscribe to the rule you created.

===Area to monitor===

When you select an area to monitor, for example, ''Forum'', the 'Event' drop down menu below will then display the events you can select from.

===Event===

Once an area has been chosen, the events for that area will display here.

===Description===

You don't have to use a description but if you do, it should be something meaningful to others as they may wish to subscribe to the rule you created.

===Notification threshold===

*This means: ''how many times should this event happen before I get notified?''
*For example the following setting would mean that if an event happens five times in 30 minutes then Moodle will send you an alert:
[[File:notificationthreshold.png|center]]

===Notification message===

When creating or editing a rule, you can embed placeholders to add details to notification messages. The use of placeholders is optional; you can use any personalised message, but if you wish to use placeholders, there are examples of use below:

The placeholders that can be used in a message template are as follows:
{| class="nicetable"
! Placeholder
! What it does
! Example
|-
| '''{link}'''
| Direct link to the actual event, eg a forum discussion.
| <nowiki>http://YourMoodle.com/mod/forum/discuss.php?d=2</nowiki>
|-
| '''{modulelink}'''
| Link to the module where the event has happened, eg a forum
| <nowiki>http://YourMoodle.com/mod/forum/view.php?id=8</nowiki>
|-
| '''{rulename}'''
| A name for the rule.
| Student discussions
|-
| '''{description}'''
| A description of the rule.
| I want to receive notifications when there is a large volume of student posts in a discussion.
|-
| '''{eventname}'''
| The name of the event being monitored.
| Forum post created.
|-
|}

====Example 1====

The above example shows the placeholders for a rule to monitor the '''Forum post created''' event. The notification message using these placeholders would be as follows:

The rule '''{rulename}''', monitoring the event '''{eventname}''', has just been fulfilled.
Click the following link to go to the forum discussion: '''{link}'''
Rule description: '''{description}'''

The result would display like this:

The rule Student discussions, monitoring the event Forum post created, has just been fulfilled.
Click on the following link to go to the forum discussion: http://YourMoodle.com/mod/forum/discuss.php?d=2 .
Rule description: I want to receive notifications when there are a large volume of student posts in a discussion.

====Example 2====

Let's create a rule called '''Glossary entries''' to monitor when a new glossary entry is created:

The rule '''{rulename}''', monitoring the event '''{eventname}''', has just been fulfilled.
Click the following link to go to see the new entry created: '''{link}'''
Rule description: '''{description}'''

The result would display like this:

The rule Glossary entries, monitoring the event Entry has been created, has just been fulfilled.
Click on the following link to go to see the new entry created: http://YourMoodle.com/mod/glossary/view.php?id=5&mode=entry&hook=1.
Rule description: I want to receive notifications when a new glossary entry is created.

'''Note:''' Some events do not have a link. '''Course deleted''' and '''Course module deleted''' for example, would not display any link if '''{link}''' or '''{modulelink}''' is used.

==How to subscribe to a rule==

*When events are created from ''Site'' or ''Course administration > Reports > Event monitoring rules'', users who have permission to subscribe to rules have an 'Event monitoring' link on their preferences page
*From here, you can unsubscribe to any events you are subscribed to already and you can subscribe to new events created by you or others.

[[File:EMSubscriptions.png|thumb|center|500px]]

==See also==

* [[Events list report]]

[[es:Monitoreo de eventos]]
[[de:Event-Beobachtung]]

Assign roles

2016-06-07T16:13:27Z

Cathkdsc: /* Checking a user's role assignments */

{{Roles}}
==Context and roles==

*In Moodle, apart from the site administrator, users do not normally have a global, site-wide role. In other words, even though you may be a teacher offline, when you are in Moodle you could have a teacher role in the course you teach in but a student role in another course where you are studying for a diploma. There are a few exceptions but this is generally the case.
*Because of the way Moodle works,assigning roles is done for a particular context. A site and course are examples of two different contexts. When you create a new role or tweak a pre-existing role via ''Administration > Site Administration > Users > Permissions > Define roles'', you are asked in which context(s) you want the role to be assigned:
[[File:rolecontexttypes.png]]

*Here are some examples of contexts; how to get to the assign roles screen, and when/why you would assign roles here:

===System context===
*''Administration > Site Administration > Users > Permissions > Assign system roles''
*Any roles assigned here apply to the whole Moodle site. It makes sense therefore that only roles that need this functionality can be assigned here. The [[Manager]] role and [[Course creator]] role are examples of two such roles. Assigning a teacher or student here would result in their being able to teach/study in every single course on the site, which is not usually desirable.
*If you really feel your Moodle needs to have teachers or students assigned in the system context, go to the teacher/student role in ''Administration > Site administration > Users > Permissions > Define roles'' and check the "system" box. Then search for and allow the capability [[Capabilities/moodle/course:view|moodle/course:view]]

=====Assigning system roles by CSV=====

Where certain custom roles are applied in the system context, it is possible to upload users to that role in bulk by adding the field ''sysrole1'' (etc) to a CSV file.

[[File:GlobalRoles1.png|thumb|500px|center|sysrole column]]

When previewed, there is a column indicating their system role:

[[File:GlobalRoles2.png|thumb|center|500px|Preview screen]]

Once uploaded, the users are present on the 'Assign system roles' screen:

[[File:GlobalRoles3.png|thumb|center|500px|Assign system roles screen]]

See [[Upload users]] for information on adding users to roles via CSV.

===Front page context===
*''Administration > Site Administration > Front Page>Users>Permissions>Assigned roles
*Those with a role in the system context do not need to be assigned a role here as well.
*However you might want to allow a teacher to manage items on the front page; in this instance, you would assign them the role on the Front page.

===Course Category context===
*See [[Category enrolments]]
*Users may be enrolled in the category to save enrolling them in each individual course in that category.

===Course context===
[[File:enrolusers.png|thumb|Enrol users]]
* Go to ''Administration > Course administration > Enrolled users''
* Click the "Enrol users" button and click those users you wish to enrol

The dropdown menu at the top shows roles for which you are allowed to enrol; typically those users with lower roles than you. See [[Enrolled users]] for more details.

===Block context===
*(Within the block) ''Administration > Assign roles''
*You may wish to assign roles to a block if, for instance you want specific people to see the block but for it to be hidden from others

=== Activity Module context===
*(Within the activity settings) ''Administration > Locally assigned roles''
*An example of this is assigning a student the teacher role locally in an individual activity like a forum so they can moderate their classmates' posts while still retaining the student role in the rest of the course.

===User context===

The user context is used for roles such as mentor, team leader or the [[Parent role]]. The role to be assigned must have 'User' ticked as the context type where it is to be assigned.

To assign a user the role of mentor in the context of their mentee, click the mentee's profile, then Preferences then 'Assign roles relative to this user'.

In Moodle 3.1 onwards, if a mentor has lots of mentees, the role of mentor can be assigned to them all in one go as follows:

# Put all mentees in a cohort
# Go to ''Site administration > Users > Permissions > Assign user roles to cohort''

==Hierarchy==

By assigning a role to a user in a certain context, you grant them the permissions contained in that role for the current context and all lower contexts.

The list of contexts in hierarchical order is as follows:

*System (no parent)
*Front page (parent = system) -
*Course category (parent = parent category or system)
*Course (parent = category or system)
*Module (parent = course or system)
*Block (parent = course or system)
*User (parent = system)

Roles can be inherited. For example if a user is assigned a Teacher role in a specific course category then the user will have this role in ALL courses within the category. Tip: use the override feature in a specific context for exceptions.

Roles will only work if the role assignment is made in the correct context. Some examples: a Teacher role should be assigned to a user in the course or course category context, a Forum moderator for a particular forum should be assigned in that specific forum.

==Assigning someone the role of Site administrator==

*Site administrators are assigned via a special page: ''Administration > Site Administration > Users > Permissions > Site Administrators''. Select the name from the right and move it over to the left:
[[File:managesiteadmins.png]]
*The original (primary) administrator cannot be deleted.

==Checking a user's role assignments==

To check a user's role assignments go to their profile page, then under the Administration heading, click on 'Preferences'. On the Preferences page, under the 'Roles' heading click on 'This user's role assignments'.

==Hidden roles==

If you want to provide users with access to the course, but don't want them to be visible in the participants list, use the [[Other users]] link in the course administration menu (''Administration > Course Administration > Users > Other Users''). Assigning roles here provides course access, and editing rights according to the permissions set for the role assigned without actually enrolling the user in the course. This is similar to the functionality of the "hidden user" check box in previous versions of Moodle.

Note: By default, the only role which can be assigned to other users is the manager role. To enable other roles, such as teacher to be assigned, the capability [[Capabilities/moodle/course:view|moodle/course:view]] should be allowed for the role (see below).

==Enabling teachers to assign the role of teacher==

By default, teachers are only allowed to assign the roles of non-editing teacher, student and guest. To enable teachers to assign the role of teacher:

#Access ''Site Administration > Users > Permissions > Define roles''.
#Click the tab "Allow role assignments".
#Click the checkbox where the teacher row and column intersect.
#Click the "Save changes" button.

==Beware of assignments that don't make sense==

There are many role assignments that do not make sense as the underlying functionality does not exist. Just because you give someone the "right" to do something does not guarantee that the interface or facility actually exists within the context that you have assigned that right. For example, you can assign a user the right to create new categories in the category context. However there is no interface within Moodle to do that (category creation is only available at the system level).

==Multiple assignments==

A significant part of the roles infrastructure is the ability to assign a user into multiple roles (at the same time). The capabilities of each role are merged to produce the effective set of capabilities. For example, a user could be both a Teacher and Student in the same course. You should be careful to ensure that if you change a user's role that you remove them from any other roles as required as this will no longer be done automatically.

==See also==
*[[Creating custom roles]]
*[[Enrolment]]
*[[Managing roles]] - for administrators
*[[Useful things a teacher can do with roles]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=59900 Discrepancies between Assign Roles lists and Participants list]
*[http://moodle.org/mod/forum/discuss.php?d=66782 What happens if a user has multiple roles in a course?]

[[Category:Roles]]

[[de:Rollen zuweisen]]
[[es:Asignar_roles]]
[[eu:Rolak_esleitu]]
[[fr:Attribution des rôles]]
[[ja:ロールの割り当て]]