MoodleDocs - User contributions [en]

MediaWiki:Sitenotice

2020-11-09T15:22:16Z

Tsala: note and link to latest stable version docs

<p class="note">''Note: You are currently viewing documentation for Moodle 3.4. Up-to-date documentation for the latest stable version of Moodle is likely available here: '''[[:en:{{NAMESPACE}}:{{PAGENAME}}|{{PAGENAME}}]].'''''</p>

MediaWiki:MoodleDocsVersionLinks

2019-05-17T07:03:58Z

Tsala: 3.7 link

3.4 docs: /34/en/{{FULLPAGENAMEE}}
3.7 docs: /37/en/{{FULLPAGENAMEE}}
3.6 docs: /36/en/{{FULLPAGENAMEE}}
3.5 docs: /35/en/{{FULLPAGENAMEE}}

Grade import

2019-04-04T09:10:11Z

Tsala: /* Grade import capabilities */ gradeimport/direct:view

{{Grades}}
==Importing grades==
Grades may be imported as a CSV or XML file, or by pasting from a spreadsheet.

The import file format is the same as the corresponding export format.

'''Note 1:''' Grade import is equivalent to manual grading in the [[Grader report|grader report]]. Thus, if grades for a particular Moodle activity such as an assignment are imported, they can no longer be edited via the assignment submission page.

'''Note 2:''' To import grades above 100% you need to check the 'unlimitedgrades' and 'gradepointmax' settings in ''Site administration>Administration>Grades>General settings''.

'''Note 3:''' Importing feedback will also overwrite any grades that are linked to that assessment. Please include both feedback and grades for the activity when mapping and importing grades via CSV. If both columns are not included then all grades for that activity will be lost.

[[Image:Csv grade import.png|thumb|CSV grade import]]
To import grades into the gradebook:

# Decide on an import format - CSV or XML file, or paste from spreadsheet (see below) - then [[Grade export|export some grades]] using the corresponding export format.
# Edit the export file as appropriate and save it.
# Tip: If you opened your exported file in Excel, don't add columns there because Moodle will reject the import if there are new columns that didn't exist in the exported file. If you need to add columns, do that in Moodle BEFORE you export your gradebook.
# Select your chosen import format from the gradebook dropdown menu.
# Browse and upload your previously saved file.
# Set options as required.
# Click the "Upload grades" button.
# CSV import only: Preview the grade import and choose the column mapping then click the "Upload grades" button to complete the grade import.
## Tip: By default "Map from" is set to First Name, and "Map to" to userid. Change both dropdowns to: "Email Address" to "useremail", or to "Id Number" to "useridnumber" (assuming that your users have ID number fields filled in in their profiles).
## Tip: Unlike in most email programs, email addresses are case sensitive in grade import files. (This should eventually be fixed as per MDL-29315.)

You need two permissions to import grades: (1) general permission to import grades and (2) permission to import grades in a particular format. For example, to import CSV grades you need moodle/grade:import ("Import grades") = Allow and gradeimport/csv:view ("Import grades from CSV") = Allow

==CSV import==

CSV import is more flexible than XML import, as you may choose the column mapping.

===Grade Mapping===

After selecting your CSV for import you'll be prompted to map user fields and grade items to the new column headers to ensure that there is a match. More than one item can be mapped to the same grade item in your destination course so be mindful of the mapping to ensure that grade data is imported properly, any collisions (i.e. if two or more fields are mapped to the same but duplicate data exists) will cause an error. User grade data for users not yet enrolled to the destination course will be noted (and once enrolled their grade data will display).

===Encoding===

If you are unsure of the encoding of your CSV file, try selecting the second option in the encoding dropdown menu. If you've used Excel to produce the CSV file the second option WINDOWS-xxx encoding is probably the correct one. The grade import preview will tell you if you guessed the encoding correctly.

===Verbose scales===

Scales can be either specified as a raw id - eg. 0, 1, 2, 3, etc. or as a string, eg. "good", "bad", "not very bad". The later format is called "verbose".

===Force import===

This prevents grade overriding during the grade importing in a scenario where more than one teacher exports the course grades and then re-imports them. If a second teacher exports the grades and tries to import them, the following error message will be displayed and the grade importing procedure will be aborted:
<pre>(''Student name'') grades have not been imported because the grades in the import file are older than in the grader report. To proceed with the grade import anyway, use the force import option.</pre>

It will not be possible to import a file that had been exported file longer than a year ago, one with dates in the future. However, in cases where a teacher needs to import the grades regardless, they should use the '''Force import'''. option. This will then import the grades irrespective of the dates.

==Paste from spreadsheet==

Grades may be pasted directly from a spreadsheet such as Excel or Libre Office:

1) Ensure you have the correct column names for your grades (eg the assignment title or manual grade) It might help to download and edit the relevant students and graded information by using the [[Grade export]] feature.

2) For the students you need either their username, their ID or their email address. Add the grades you need and copy the relevant section:
[[File:pastegrades1.png|thumb|center|400px]]
3) In your course, go to ''Grade administration>Import>Paste from spreadsheet'' and paste:
[[File:pastegrades2.png|thumb|center|400px]]
4) In the preview, ensure you match up the identifier you used for the students -so if you used 'username', ensure it maps to 'username'. Do the same for your graded activities:
[[File:pastegrades3.png|thumb|400px|center]]
5) If everything has been correctly mapped (See grade mapping above), you should get a success message and the grades will have been added, displaying in a different colour to show they were imported directly into the gradebook:
{|
| [[File:pastegrades4.png|thumb|400px]]
| [[File:pastegrades5.png|thumb|400px]]
|}

Paste from a spreadsheet requires similar permissions to a csv file import: (1) general permission to import grades and (2) permission to import grades in a particular format i.e. moodle/grade:import ("Import grades") = Allow and gradeimport/direct:view ("Import grades from spreadsheet") = Allow

==XML import==

Before importing an XML file you will need to ensure that all of the students that you want to alter grades for have their ID number field filled out. This is located in the "Optional" section of the user edit profile page.
You will also need to set the ID number of the activity as well. You can find this under "Common module settings" when editing the activity.

The format for the XML should be as follows:
<pre>
<results>
<result>
<assignment>activityidnumber</assignment>
<student>studentidnumber</student>
<score>53.00</score>
</result>
<result>
<assignment>differentactivityidnumber</assignment>
<student>studentidnumber</student>
<score>73.00</score>
</result>
</results>
</pre>

For a working example try exporting the gradebook as an xml file and view the format.

===Remote file URL===

The remote file URL field is for fetching data from a remote server, such as a student information system.

==Grade import capabilities==

* [[Capabilities/gradeimport/csv:view|Import grades from CSV]]
* [[Capabilities/gradeimport/direct:view|Import grades from spreadsheet]]
* [[Capabilities/gradeimport/xml:publish|Publish import grades from XML]]
* [[Capabilities/gradeimport/xml:view|Import grades from XML]]

==See also==

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=85944 Gradebook confusion]
*[http://moodle.org/mod/forum/discuss.php?d=92081 Can external software insert data into the gradebook?]

[[ja:評定のインポート]]
[[de:Bewertungen importieren]]
[[es:Importar calificaciones]]
[[fr:Importation de notes]]

Capabilities/gradeimport/direct:view

2019-04-04T09:07:27Z

Tsala: capabilities template, description, categories

{{Capabilities}}
* This allows a user to [[Grade import|import grades]] by pasting from a spreadsheet
* This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Grade]]
[[Category:Grades]]

Main page

2019-02-14T06:57:00Z

Tsala: pt-br interlang link

{{#addbodyclass:moodledocs-logo}}
<div class="navtrail">[https://docs.moodle.org/overview/ Docs overview] ► [[{{PAGENAME}}|Moodle Docs 3.4]]</div>

<div class="row-fluid">
<div class="row-fluid">
<ul class="thumbnails">
<li class="span4">
<div class="thumbnail">
<div class="caption">
<h4>Get started</h4>
* [[Features|Browse features]]
* [[Teacher quick guide]]
* [[Admin quick guide]]
* [[Installation quick guide]]
: [[:Category:Quick guide|More quick guides >>]]
</div>
</div>
</li>
<li class="span4">
<div class="thumbnail">
<div class="caption">
<h4>Manage your course</h4>
* [[Course homepage|Set up your course]]
* [[Add students|Add students]]
* [[Tracking progress|Track progress]]
* [[Working with files|Upload files]]
: [[Managing a Moodle course|More for teachers >>]]
</div>
</div>
</li>
<li class="span4">
<div class="thumbnail">
<div class="caption">
<h4>Add activities</h4>
* [[Assignment activity|Use assignments to assess]]
* [[Forum activity|Discuss in forums]]
* [[Quiz activity|Test students with a quiz]]
* [[Workshop activity|Peer-assess with a workshop]]
: [[Activities|More activities >>]]
</div>
</div>
</li>
</ul>
</div>

<div class="row-fluid">
<ul class="thumbnails">
<li class="span4">
<div class="thumbnail">
<div class="caption">
<h4>What's new</h4>
* [[New for teachers|For teachers]]
*[[New for students|For students]]
* [[New for administrators|For admins]]
* [[New for mobile|Mobile]]
: [[New features|New features list >>]]
</div>
</div>
</li>
<li class="span4">
<div class="thumbnail">
<div class="caption">
<h4>Manage your site</h4>
* [[Add users|Add users]]
* [[Adding a new course|Add courses]]
* [[Site appearance|Change the look and feel]]
* [[Installing plugins|Install plugins]]
: [[Managing a Moodle site|More for administrators >>]]
</div>
</div>
</li>
<li class="span4">
<div class="thumbnail">
<div class="caption">
<h4>Mobile app</h4>
* [[Moodle Mobile features|View app features]]
* [[Mobile app notifications|Keep up-to-date with notifications]]
* [[Creating Moodle Mobile friendly courses|Create mobile-friendly courses]]
* [[Moodle Mobile additional features|Add more app features]]
: [[Moodle Mobile|More about Moodle Mobile >>]]
</div>
</div>
</li>
</ul>
</div>

__NOTOC__

[[de:Hauptseite]]
[[es:Página Principal]]
[[eu:Azala]]
[[fr:Accueil]]
[[hr:Glavna stranica]]
[[ja:メインページ]]
[[pt-br:Página_principal]]
[[zh:首页]]

Grade aggregation

2019-02-14T06:54:09Z

Tsala: pt-br interlang link

{{Grades}}
The aggregation dropdown menu lets you choose the aggregation strategy that will be used to calculate each participant's overall grade for a [[Grade categories|grade category]]. The different options are explained below.

== Aggregation strategy ==

The grades are first converted to percentage values (interval from 0 to 1), then aggregated using one of the strategies below and finally converted to the associated category item's range (between Minimum grade and Maximum grade). In what follows all Minimum grades are assumed to be 0.

'''Important''': An empty grade is simply a missing gradebook entry, and could mean different things. For example, it could be a participant who hasn't yet submitted an assignment, an assignment submission not yet graded by the teacher, or a grade that has been manually deleted by the gradebook administrator. Caution in interpreting these "empty grades" is thus advised.

== Mean of grades ==
The sum of all grades divided by the total number of grades.
A1 70/100, A2 20/80, A3 10/10, category max 100:
(0.7 + 0.25 + 1.0)/3 = 0.65 --> 65/100

== Weighted mean ==
Each grade item can be given a weight to influence its importance in the overall mean. In simple terms, the category "total" will be equal to the sum of the scores in each grade item, these scores being multiplied by the grade items' weights, and that sum being finally divided by the sum of the weights, as shown in this example.
A1 70/100 weight 10, A2 20/80 weight 5, A3 10/10 weight 3, category max 100:
(0.7*10 + 0.25*5 + 1.0*3)/(10 + 5 + 3) = 0.625 --> 62.5/100

== Simple weighted mean ==
The difference from Weighted mean is that the weight of each item is simply the difference between its Maximum and Minimum grade.
A1 70/100, A2 20/80, A3 10/10, category max 100:
(0.7*100 + 0.25*80 + 1.0*10)/(100 + 80 + 10) = 0.526 --> 52.6/100

When the "Simple weighted mean" aggregation strategy is used, a grade item can act as Extra credit for the category. This means that the grade item's maximum grade will not be added to the category total's maximum grade, but the item's grade will. For example, if A3 is marked as extra credit in the above calculation:
A1 70/100, A2 20/80, A3 (extra credit) 10/10, category max 100:
(0.7*100 + 0.25*80 + 1.0*10)/(100 + 80) = 0.556 --> 55.6/100

== Mean of grades (with extra credits) ==
Arithmetic mean with a twist. An old, now unsupported, aggregation strategy provided here only for backward compatibility with old activities.

A value greater than 0 treats a grade item's grades as extra credit during aggregation. The number is a factor by which the grade value will be multiplied before it is added to the sum of all grades, but the item itself will not be counted in the division. For example:

* Item 1 is graded 0-100 and its "Extra credit" value is set to 2
* Item 2 is graded 0-100 and its "Extra credit" value is left at 0.0000
* Item 3 is graded 0-100 and its "Extra credit" value is left at 0.0000
* All 3 items belong to Category 1, which has "Mean of grades (with extra credits)" as its aggregation strategy
* A student gets graded 20 on Item 1, 40 on Item 2 and 70 on Item 3
* The student's total for Category 1 will be 95/100 since 20*2 + (40 + 70)/2 = 95

== Median of grades ==
The middle value (or the mean of the two middle values) when percentages (the tatios between grades and their maximum values) are arranged in order of value. The advantage over the mean is that it is not affected by outliers (grades which are uncommonly far from the mean).
A1 70/100, A2 20/80, A3 10/10, category max 100:
median(0.7; 0.25; 1.0) --> 0.70 --> 70/100

== Smallest grade ==
The result is the smallest grade after normalisation. It is usually used in combination with Aggregate only non-empty grades.
A1 70/100, A2 20/80, A3 10/10, category max 100:
min(0.7; 0.25; 1.0) = 0.25 --> 25/100

== Highest grade ==
The result is the highest grade after normalisation.
A1 70/100, A2 20/80, A3 10/10, category max 100:
max(0.7; 0.25; 1.0) = 1.0 --> 100/100

== Mode of grades ==
The mode is the normalised grade that occurs the most frequently. It is often used for non-numerical grades. The advantage over the mean is that it is not affected by outliers (grades which are uncommonly far from the mean). However it loses its meaning once there is more than one most frequently occurring grade (only one is kept), or when all the grades are different from each other.
A1 70/100, A2 35/50, A3 20/80, A4 10/10, A5 7/10 category max 100:
mode(0.7; 0.7; 0.25; 1.0; 0.7) = 0.7 --> 70/100

== Natural ==

This is the sum of all grade values, scaled by weight. The Maximum grade of the category is the sum of the maximums of all aggregated items.
A1 70/100, A2 20/80, A3 10/10, without forcing weights:
(70 + 20 + 10)/(100 + 80 + 10) --> 100/190

'''Note''': Scale grades are ignored.

When the "Natural" aggregation strategy is used, a grade item can act as Extra credit for the category. This means that the grade item's maximum grade will not be added to the category total's maximum grade, but the item's grade will. Following is an example:

* Item 1 is graded 0-100
* Item 2 is graded 0-75
* Item 1 has the "Act as extra credit" checkbox ticked, Item 2 doesn't.
* Both items belong to Category 1, which has "Natural" as its aggregation strategy
* Category 1's total will be graded 0-75
* A student gets graded 20 on Item 1 and 70 on Item 2
* The student's total for Category 1 will be 75/75 (20+70 = 90 but Item 1 only acts as extra credit, so it brings the total to its maximum)

Natural aggregation functions as a sum of grades when the weight boxes are left alone. In this situation, the numbers in the weight boxes are informational and represent the effective weights in the sum. Natural aggregation can also function as a mean of grades, when the weight boxes are checked and then adjusted so that the weights are equal across a set of items in a category, or across a set of categories. Items can still be marked as "Extra credit" while using the weights to calculate a mean, and contribute to the total for the category.

==Available aggregation types==
[[Image:availableaggregationtypes1.png|thumb|Available aggregation types setting]]
The default is 'Natural' but the administrator can specify other types from '' Site administration >administration > Grades > [[Grade category settings]]''.

Note that reducing the number of aggregation types simply results in disabled aggregation types not appearing in the aggregation type dropdown menu. All existing grade category calculations remain the same, regardless of whether the aggregation type is later disabled by an administrator.

[[ca:Agregació de les categories]]
[[fr:Tendance centrale de la catégorie]]
[[es:Agregación de categoría]]
[[de:Bewertungen zusammenfassen]]
[[pt-br:Agregação de Notas]]

MediaWiki:MoodleDocsVersionLinks

2018-11-30T16:02:23Z

Tsala: 3.6 link

3.4 docs: /34/en/{{FULLPAGENAMEE}}
3.6 docs: /36/en/{{FULLPAGENAMEE}}
3.5 docs: /35/en/{{FULLPAGENAMEE}}
3.1 docs: /31/en/{{FULLPAGENAMEE}}

Template:MediaPlayer

2018-10-30T12:20:40Z

Tsala: Fix the urlargs parameter syntax (copied from 35 docs)

<includeonly>{{#evt:
service=youtube
|id={{{url}}}
|description={{{desc|{{{url}}}}}}
|urlargs=modestbranding=1&rel=0
}}</includeonly><noinclude>

Displays an embedded media player of the given YouTube video.

== Syntax ==

<nowiki>{{MediaPlayer | url = https://www.youtube.com/watch?v=U7M3sZL6wts | desc = Video description}}</nowiki>

</noinclude>

Moodle Mobile guide for admins

2018-10-18T15:00:36Z

Tsala: /* Custom language strings */ updated link

{{Mobile}}
==Enable mobile services on your site==
Your site needs to have mobile access enabled so users can use the mobile app.

For sites using https, mobile access is enabled by default in new installations of Moodle 3.0 onwards.

For http sites, mobile access can be enabled by an administrator as follows:

# In ''Site administration > Mobile app > Mobile settings'' tick the 'Enable web services for mobile devices' checkbox
# Click the button to save changes.

If your site uses a [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL certificate], it must be a trusted certificate. For security reasons the app doesn't work with self-signed certificates.

Please, verify that your certificate is valid via: https://www.geocerts.com/ssl_checker (you shouldn't see any warning).

If your site has the /login directory protected (frequently done when using the Shibboleth authentication method), you must enable access to the login/token.php script.

===Frame embedding===
If your sites uses [https://en.wikipedia.org/wiki/ReCAPTCHA reCaptcha], Vimeo videos or custom menu items (as described bellow) you must enable the admin setting "Allow frame embedding" (allowframembedding).

==Mobile authentication==

If your site uses a SSO authentication method (CAS, Shibboleth, LDAP SSO, OAuth...), then select via a browser window or via an embedded browser for 'Type of login' (typeoflogin) in 'Mobile authentication' in the Site administration. (This setting is provided for older pre-Moodle 3.2 sites via the [[Moodle Mobile additional features]] plugin.)

The options 'browser window' and 'embedded browser' are very similar; the only difference is when redirecting the user to enter their credentials in the site, the site will be opened in the device's default browser (for browser window) or the site will be opened "embedded" in the mobile app (for embedded browser). The user experience is better in embedded browser, but not all the authentication plugins will work in embedded browser (for example, if JavaScript popups are required they must use the 'browser window'). The admin should check whether both options work, and if so, choose 'embedded browser'.

If you are using Google OAuth you will have to use the 'browser window' method because Google recently blocked authentication via 'embedded browsers'.

If your organisation uses a custom branded app and 'Type of login' is set to 'Via a browser window' or 'Via embedded browser', then a URL scheme (forcedurlscheme) may be set. This will result in only the custom branded app working for the site: the official Moodle Mobile app will not work.

== Customise your app theme ==

The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can safely apply any CSS, CSS2 and CSS3 style.

Go to ''Administration > Site administration > Mobile app > Mobile appearance'' and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles.

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin).

'''For example:''' ''https://mymoodlesite.com/theme/mytheme/style/mymobileapp.css''

Once the user is logged in the app, remote CSS files for applying your custom styles are regularly retrieved.

Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.

For further information, see the dev docs [[:dev:Moodle Mobile Themes|Moodle Mobile Themes]].

If you want your own custom branding for your organization, Moodle offers the The Branded Moodle Mobile app service, please visit https://moodle.com/mobileapp/ for more information.

== Moodle Mobile additional features plugin for old Moodle sites ==

For old Moodle sites it is recommended to install the [[Moodle Mobile additional features]] plugin.

== Notifications ==

You might find them annoying but push notifications keeps you and your users informed and updated on everything about the app. Moodle only send useful and important notifications such as new features or service disruptions.

Enabling push notifications is easy! An administrator can enable it by connecting their Moodle site/s to our free Notifications server available (only) for registered Moodle sites.

An access key can be obtained via Administration > Site administration > Plugins > Message outputs > Mobile Notifications.

The full guide on enabling push notifications can be found here: [[Mobile app notifications]]

== App banners ==
[[File:app banner.png|thumb|Moodle Mobile app banner]]
App banners let your users know that there is a mobile app available for the site. App banners are only displayed when accessing the site using a mobile browser.

In Moodle 3.3 onwards, app banners for Android are supported as well as for iOS.

App banners are disabled by default. They can be enabled in 'Mobile appearance' in the Site administration.

If you are using a custom mobile app, you need to provide the unique identifier for the iOS and Android app; if you are using the Moodle Mobile app, the settings may be left as default.

=='Get the mobile app' link==

{{New features}}In Moodle 3.4 onwards, the link 'Get the mobile app' in the footer of each page on the site encourages users to make use of the mobile app.

By default, the link is https://download.moodle.org/mobile however the setting 'App download page' can be changed e.g. for sites using a branded mobile app.

If mobile services are not enabled for the site, then the 'Get the mobile app' link is not displayed.

To prevent the 'Get the mobile app' link being displayed, simply remove the URL from the 'App download page' setting and save changes.

== Configuring the app from your site ==

In Moodle 3.3 onwards, or with the [[Moodle Mobile additional features]] plugin, settings in the Site administration enable admins to configure the app.

* In Moodle 3.3 onwards go to ''Site administration > Mobile features''
* In sites with the Moodle Mobile additional features plugin installed, go to ''Site administration > Plugins > Local plugins > Mobile additional features''

===Force log out===

Replace the Change site option to "Log out" so that users must enter their credentials on their next access. This is useful for custom mobile apps, as there is no reason for users wanting to switch to a different site.

===Disabled features===

Disable app functionalities for your site. If there's a feature you don't want to make available via the app you can disable it here.

===Custom menu items===

Additional items can be added to the app main menu (the side menu), such as a link to a different grade book.

Each custom menu item should have format: item text, link URL, link-opening method and language code (optional, for displaying the item to users of the specified language only), separated by pipe characters.

Possible link-opening methods are:

* app - for linking to an activity supported by the app i.e. almost all activity types, as listed in [[Moodle Mobile features]].
* inappbrowser - for linking to external URLs or site functionalities not supported by the app. The link will open in a browser inside the app overlaying the complete screen.
* browser - as for inappbrowser except that the link will instead open in the device default browser outside the app.
* embedded - as for inappbrowser except that the link will instead open in an iframe in a new page in the app. (For this option you may need to enable the admin setting "Allow frame embedding" (allowframembedding)

Tip: If you add a custom menu item and save changes, then it doesn't appear in the app main menu, double check that the item is correctly formatted.

Please, note that if the app is using a language not indicated in the previous list, the first language in the list will be used.

If you want options tied to a language, you can append _only to the language code, for example:
en_only
es_only

Will display the custom menu item only when the app language is English or Spanish.

===Custom language strings ===

Words and phrases displayed in the app can be customised via the "Custom language strings" (customlangstrings) setting.

Enter each custom language string on a new line with format: string identifier, custom language string and language code, separated by pipe characters. For example:

mm.user.student|Learner|en
mm.user.student|Aprendiz|es

The complete list of string identifiers is listed in https://raw.githubusercontent.com/moodlehq/moodlemobile-phonegapbuild/master/assets/lang/en.json. The string identifier is before the colon.

For example:

[[File:Mobile string identifiers list examples.png|300px]]

means that the string "Student" has string identifier "mm.user.student".

==Web services token duration==

{{New features}}In Moodle 3.4 onwards, an admin can set how long a web services token created by a user (for example via the mobile app) is valid. (In previous versions of Moodle a token was valid for 3 months.)

==See also==

* [[Moodle Mobile FAQ]] for other administration-related mobile app questions.
* [[:dev:Moodle Mobile debugging WS requests]] - a guide to helping you find and report problems with the Moodle Mobile app on your site
* [[:dev: Moodle Mobile Roadmap]]
* [[:dev:Moodle Mobile release notes]]
* [[:dev:Moodle Mobile|Moodle Mobile developer docs]]
* [[Moodle Mobile availability plugin]]
* [[Mobile web services]]

[[es:Moodle Mobile guía para administradores]]
[[de:Moodle Mobile - Anleitung für Administrator/innen]]

Search engine optimization

2018-10-15T08:30:23Z

Tsala: removing out-of-date items

{{Update}}

Search Engine Optimization (SEO) in Moodle is limited however there are several steps that can be taken to improve search engine visibility and ranking.

- Enable the opentogoogle setting in siteadmin > security > site policies

- Have a simple site name that is clean and obvious
e.g. [Organisation Name] E-Learning

- Set the site description (Used by many themes as the metadata)

- Set course descriptions (Also have the course links on the front page otherwise descriptions will not be crawled)

There are other factors that come into play in SEO such as amount of content, website traffic and website trust. In short, lots of relevant content and lots of traffic.

== Moodle settings ==

The ''opentogoogle'' setting in Site policies may be set to 'Yes' to allow Google to enter your site as a Guest. In addition, people coming in to your site via a Google search will automatically be logged in as a Guest. However, people can just read the content from Google's site without ever visiting your site.

The text that Google lists next to your website is taken from the meta description tag. You can fill this information in the Admin > Site Settings area of Moodle.

==Links to and from other sites==

Linking is a major contributor to SEO. If you link to reputable sites your ranking will increase, but more importantly other sites linking to you will increase your ranking.

Other sites linking to you is very important, but you cant just go and create 30 sites with a link to your site because Google is smarter than that. Reputation is important to Google and 100 links from small sites with no reputation won't count for a single link from say www.time.com.

== Other methods ==

Of course, the standard stuff applies:
* Making your content interesting
* Linking to relevant sites and getting relevant sites to link to you (within reason)
* Making your site accessible (as Google sees roughly the same things as a blind web surfer with JavaScript turned off)
* Getting bloggers in your field to talk about your site (this seems to be the current best method)

[[Category:Administrator]]

[[ja:サーチエンジン最適化]]

Talk:Policies plugin

2018-09-17T14:27:52Z

Tsala: Tsala moved page Talk:Policies plugin to Talk:Policies

#REDIRECT [[Talk:Policies]]

Talk:Policies

2018-09-17T14:27:52Z

Tsala: Tsala moved page Talk:Policies plugin to Talk:Policies

Guideline says:
# Go to 'Policy settings' in the Site administration.
Can we make this more specific? We recently updated to 3.4.3 (with the two GDPR plugins) and the Policy settings appear in:

Site administration > Users > Privacy and policies > Policy settings...

I have seen though in other sites that Privacy and policies are directly under the the Site administration.

Perhaps this is a minor difference between the 3.4.3 and 3.5 version?

Anna Krassa 6 Jun 18:21 GTM+3

: Thanks Anna for your comment. We generally only mention the page or setting name for items in the Site administration as it's quicker to search than to try and follow a navigation trail. --[[User:Helen Foster|Helen Foster]] ([[User talk:Helen Foster|talk]]) 14:21, 17 September 2018 (UTC)

Policies plugin

2018-09-17T14:27:51Z

Tsala: Tsala moved page Policies plugin to Policies over redirect

#REDIRECT [[Policies]]

Policies

2018-09-17T14:27:51Z

Tsala: Tsala moved page Policies plugin to Policies over redirect

{{New features}}The policies tool provides a new user sign-on process, with ability to define multiple policies (site, privacy, third party), track user consents, and manage updates and versioning of the policies.

It was introduced as a plugin [https://moodle.org/plugins/tool_policy tool_policy] in Moodle 3.4 and is available as standard in Moodle 3.4.5 onwards.

==Enabling the policies tool==

To enable the policies tool:

# Go to 'Policy settings' in the Site administration.
# Set the Site policy handler to 'Policies (tool_policy)'.
# Save changes.

Two new pages will then appear in the Site administration - 'Manage policies' and 'User agreements'.

Note that when Policies is set as the site policy handler, the settings 'Site policy' and 'Site policy for guests' are ignored.

==Adding and managing policies==
[[File:policies and agreements.png|thumb|Policies and agreements]]
An admin or any user with the [[Capabilities/tool/policy:managedocs|Manage policies]] capability (by default manager) can access the page 'Manage policies' in the Site administration and:

* Add a new site / privacy / third parties / other policy for all users, authenticated users or guests
* Change the active / inactive status of each policy
* View the number and percentage of users who have agreed to each policy
* Edit a policy and specify whether it is a minor change (not requiring users to reconfirm their consent) or not
* View the current version of each policy and also previous versions
* Change the order in which policies are shown to users

To add a new policy:

# Go to 'Manage policies' in the Site administration.
# Click the button 'New policy'
# Complete the form and save changes.

Note that once created, a policy can be edited, or set to inactive, but if users have agreed to it, it can't be deleted.

==Giving consent to policies==
[[File:Agreeing to policies.png|thumb|Giving consent to policies]]
All users (with the exception of admins) will be required to give their consent to all policies defined either for “Authenticated users” or for “All users” before proceeding further on the site.

If a new policy is added, all users will be required to give their consent when they next log in. Similarly, if an existing policy is edited and is not marked as a minor change, all users will be required to give their consent when they next log in.

If self-registration is enabled on the site, new users will be required to give their consent to all policies before proceeding to the sign-up form. If digital age of consent verification (a new setting in Moodle 3.4.2 onwards) is enabled in '[[Privacy|Privacy settings]]' in the Site administration, when a new user clicks the 'Create new account' button, they will be prompted to enter their age and country. If the user's age is lower than the age of consent for their country, they will see a message prompting them to ask their parent/guardian to contact the support contact (as specified in 'Support contact' in the Site administration).

==Policies for guests==
[[File:policies modal window.png|thumb|Policies for guests modal window]]
If a user logs in as a [[Guest access|guest]], a modal window will be shown at the bottom of the user's browser window with links to all policies defined either for guests or for all users.

==Minors==
[[File:No permission to agree to policies.png|thumb|Minor prevented from proceeding further on the site]]
Users who are younger than the age of digital consent, called 'minors', may be prevented from giving their consent by prohibiting the capability [[Capabilities/tool/policy:accept|Agree to policies]]. They will then be prevented from proceeding further on the site until someone can give consent on their behalf.

===Sites with minors as the majority of users===

To prohibit users from agreeing to policies because they are a minor:

# Go to 'Define roles' in the Site administration.
# Edit the role of authenticated user and set [[Capabilities/tool/policy:accept|Agree to policies]] to prohibit.
# Save changes.

To enable teachers and other users who are not minors to agree to policies:

# Go to 'Define roles' in the Site administration.
# Click the button 'Add a new role'.
# Give the role a name such as 'Able to give consent', short name and description.
# For context types where this role may be assigned, tick system.
# Enter policy in the filter box, then allow the capability Agree to policies.
# Click the button 'Create this role'.
# Go to 'Assign system roles' in the Site administration.
# Choose the 'Able to give consent' role to assign.
# Select teachers and other users in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

===Sites with only a few minors===

To prohibit users from agreeing to policies because they are a minor:

# Go to 'Define roles' in the Site administration.
# Click the button 'Add a new role'.
# Give the role a name such as 'Digital minor', short name and description.
# For context types where this role may be assigned, tick system.
# Enter policy in the filter box, then prohibit the capability Agree to policies.
# Click the button 'Create this role'.
# Go to 'Assign system roles' in the Site administration.
# Choose the 'Digital minor' role to assign.
# Select minors in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

==User agreements==
[[File:user agreements.png|thumb|User agreements filtered to show minors]]
An admin or any user with the [[Capabilities/tool/policy:viewacceptances|View user agreements reports]] capability (by default manager) can access the page 'User agreements' in the Site administration and:

* View user consents
* Filter by policy, permission, status or role
* Give consent on behalf of minors
* Download table data

User agreements for a particular policy may also be viewed via the 'Manage policies' page by clicking the link in the Agreements column.

==Giving consent on behalf of other users==

An admin or any user with the capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] can give consent on behalf of minors or when a written consent was obtained offline.

===Giving consent on behalf of multiple users===
[[File:Record of consents.png|thumb|Record of consents with remarks]]
Users with capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] in the system context, such as managers, can give consent on behalf of multiple users as follows:

# Go to 'User agreements' in the Site administration.
# If necessary, filter by 'Permission: Can not agree'.
# To give consent for multiple policies, tick the box next to selected users' names then click the consent button.
# To give consent for a single policy, click the red cross next to the user's name.

When giving consent on behalf of other users, there is an opportunity to add some remarks. Clicking on the link in the Overall column gives an overview with details of who gave consent and when, together with any remarks.

===Giving consent on behalf of a child===

A parent or guardian may be allowed to give consent on behalf of their child by giving them the capability [[Capabilities/tool/policy:acceptbehalf|Agree to the policies on someone else's behalf]] in the user context. See the [[Parent role]] for details of how to create the role and assign a parent to a student. The parent or guardian will then be able to give consent as follows:

# Go to the child's profile page.
# Click the link 'Policies and agreements'.
# Click the red cross next to the policy name.

==Capabilities==

* [[Capabilities/tool/policy:accept|Agree to policies]] - allowed for authenticated user role
* [[Capabilities/tool/policy:managedocs|Manage policies]] - allowed for default role of manager only
* [[Capabilities/tool/policy:manageprivacy|Manage privacy settings]] - allowed for default role of manager only
* [[Capabilities/tool/policy:viewacceptances|View user agreements reports]] - allowed for default role of manager only
* [[Capabilities/tool/policy:acceptbehalf|Agree to policies on someone else's behalf]] - allowed for default role of manager only

==See also==

* [[GDPR for administrators (Moodle 3.4.2+)]]

[[Category:Privacy]]

[[es:Plugin de políticas]]
[[de:Richtlinien und Einwilligungen]]

Policies

2018-09-17T14:26:47Z

Tsala: tool_policies standard in 3.4.5 (MDL-62800)

Data privacy

2018-09-17T14:24:54Z

Tsala: removing heading

{{New features}}The Data privacy functionality provides the workflow for users to submit a data request (also known as a subject access request or SAR) and for the site administrator or privacy officer to process these requests. It was introduced as a plugin [https://moodle.org/plugins/tool_dataprivacy tool_dataprivacy] in Moodle 3.4 and is available as standard in Moodle 3.4.5 onwards.

==Privacy officer role==

It is recommended that you create a [[Privacy officer role]] and assign it to the person responsible. If there is nobody on the site with the role of privacy officer i.e. nobody with the capability to manage data requests, then a site admin can respond to data requests and manage the data registry.

==Data requests==
[[File:requesting data.png|thumb|Requesting data]]
Any user can send a message to the privacy officer via the 'Contact privacy officer' link on their profile page.

In addition, they can request a copy of all of their personal data or request that their personal data should be deleted as follows:

# Go to your profile page (via the user menu).
# Click the link 'Data requests' then click the 'New request' button.
# Select 'Export all of my personal data' or 'Delete all of my personal data' as appropriate.
# Save changes.
[[File:Request approved.png|thumb|Request approved]]
The privacy officer will then receive a data request notification.

If the user has requested a copy of all of their personal data, once the request is approved, they will receive a notification to inform them that their personal data may be downloaded from their Data requests page. In Moodle 3.4.5 onwards, the user has by default one week to download their data before the download link expires. (An administrator can set a different expiry time for the data request in 'Privacy settings' in the Site administration.)

If the user has requested that their personal data should be deleted, once the request is approved, they will receive an email to inform them and they will no longer be able to log in to the site.

==Responding to data requests==
[[File:viewing a data request.png|thumb|Viewing a data request]]
The privacy officer can respond to data requests as follows:

# Go to 'Data requests' in the Site administration (or follow the link in the data request notification).
# In the Actions dropdown, select View, Approve, or Deny as appropriate.

If the user has sent a message, the privacy officer can view the message and copy the user's email address, then reply via email. In Moodle 3.4.5 onwards, after replying they can mark it as complete.

==Data registry==
[[File:data registry.png|thumb|Data registry]]
The privacy officer can set purposes (why the organisation is processing data) with retention periods and categories for data stored in Moodle in the data registry.

A default purpose and retention period may be set for course categories, courses, activity modules and blocks.

===Example categories===

* Administrative: Civil status, identity, identification data, images …
* Personal life (lifestyle, family situation, etc.)
* Economic and financial information (income, financial situation, tax situation, etc.)
* Connection data (IP address, logs, etc.)
* Educational Data (Assessed Coursework, exam scripts etc)
* Records of Education Attainment (Results of exams, assessments, qualifications awarded etc)
* Location data (travel, GPS data, GSM, etc.)

===Data registry set-up===

To add purposes and categories:

# Go to 'Data registry' in the Site administration.
# In the Edit menu select Categories.
# On the 'Edit categories' page, click the + button to add a new category.
# Enter a category name and description then click the Save button.
# Go to 'Data registry' again and in the Edit menu select Purposes.
# On the 'Edit purposes' page, click the + button to add a new purpose.
# Enter a purpose name, description and retention period then click the Save button.

To set default categories and purposes:

# In 'Data registry' in the Site administration click the 'Set defaults' button.
# Select a default category and purpose for the site, and for users, course categories, courses, activity modules and blocks as required.
# Save changes.

==Capabilities==

* [[Capabilities/tool/dataprivacy:managedataregistry|Manage data registry]]
* [[Capabilities/tool/dataprivacy:managedatarequests|Manage data requests]]
* [[Capabilities/tool/dataprivacy:makedatarequestsforchildren|Make data requests for children]]

[[Category: Privacy]]

[[es:Plugin de privacidad de datos]]
[[de:Schutz persönlicher Daten]]

Talk:Policies

2018-09-17T14:21:45Z

Tsala: reply

Data privacy plugin

2018-09-17T13:50:53Z

Tsala: Tsala moved page Data privacy plugin to Data privacy

#REDIRECT [[Data privacy]]

Data privacy

2018-09-17T13:50:53Z

Tsala: Tsala moved page Data privacy plugin to Data privacy

==Data privacy functionality==
{{New features}}The Data privacy functionality provides the workflow for users to submit a data request (also known as a subject access request or SAR) and for the site administrator or privacy officer to process these requests. It was introduced as a plugin [https://moodle.org/plugins/tool_dataprivacy tool_dataprivacy] in Moodle 3.4 and is available as standard in Moodle 3.4.5 onwards.

==Privacy officer role==

It is recommended that you create a [[Privacy officer role]] and assign it to the person responsible. If there is nobody on the site with the role of privacy officer i.e. nobody with the capability to manage data requests, then a site admin can respond to data requests and manage the data registry.

==Data requests==
[[File:requesting data.png|thumb|Requesting data]]
Any user can send a message to the privacy officer via the 'Contact privacy officer' link on their profile page.

In addition, they can request a copy of all of their personal data or request that their personal data should be deleted as follows:

# Go to your profile page (via the user menu).
# Click the link 'Data requests' then click the 'New request' button.
# Select 'Export all of my personal data' or 'Delete all of my personal data' as appropriate.
# Save changes.
[[File:Request approved.png|thumb|Request approved]]
The privacy officer will then receive a data request notification.

If the user has requested a copy of all of their personal data, once the request is approved, they will receive a notification to inform them that their personal data may be downloaded from their Data requests page. In Moodle 3.4.5 onwards, the user has by default one week to download their data before the download link expires. (An administrator can set a different expiry time for the data request in 'Privacy settings' in the Site administration.)

If the user has requested that their personal data should be deleted, once the request is approved, they will receive an email to inform them and they will no longer be able to log in to the site.

==Responding to data requests==
[[File:viewing a data request.png|thumb|Viewing a data request]]
The privacy officer can respond to data requests as follows:

# Go to 'Data requests' in the Site administration (or follow the link in the data request notification).
# In the Actions dropdown, select View, Approve, or Deny as appropriate.

If the user has sent a message, the privacy officer can view the message and copy the user's email address, then reply via email. In Moodle 3.4.5 onwards, after replying they can mark it as complete.

==Data registry==
[[File:data registry.png|thumb|Data registry]]
The privacy officer can set purposes (why the organisation is processing data) with retention periods and categories for data stored in Moodle in the data registry.

A default purpose and retention period may be set for course categories, courses, activity modules and blocks.

===Example categories===

* Administrative: Civil status, identity, identification data, images …
* Personal life (lifestyle, family situation, etc.)
* Economic and financial information (income, financial situation, tax situation, etc.)
* Connection data (IP address, logs, etc.)
* Educational Data (Assessed Coursework, exam scripts etc)
* Records of Education Attainment (Results of exams, assessments, qualifications awarded etc)
* Location data (travel, GPS data, GSM, etc.)

===Data registry set-up===

To add purposes and categories:

# Go to 'Data registry' in the Site administration.
# In the Edit menu select Categories.
# On the 'Edit categories' page, click the + button to add a new category.
# Enter a category name and description then click the Save button.
# Go to 'Data registry' again and in the Edit menu select Purposes.
# On the 'Edit purposes' page, click the + button to add a new purpose.
# Enter a purpose name, description and retention period then click the Save button.

To set default categories and purposes:

# In 'Data registry' in the Site administration click the 'Set defaults' button.
# Select a default category and purpose for the site, and for users, course categories, courses, activity modules and blocks as required.
# Save changes.

==Capabilities==

* [[Capabilities/tool/dataprivacy:managedataregistry|Manage data registry]]
* [[Capabilities/tool/dataprivacy:managedatarequests|Manage data requests]]
* [[Capabilities/tool/dataprivacy:makedatarequestsforchildren|Make data requests for children]]

[[Category: Privacy]]

[[es:Plugin de privacidad de datos]]
[[de:Schutz persönlicher Daten]]

Data privacy

2018-09-17T13:50:45Z

Tsala: data privacy standard in 3.4.5 (MDL-62799)

Data privacy

2018-09-17T13:21:43Z

Tsala: data request expiry time in 3.4.5 (MDL-62660)

{{Infobox plugin
|type = Admin tools
|entry = https://moodle.org/plugins/tool_dataprivacy
|tracker = https://tracker.moodle.org/issues/?jql=component%20%3D%20Privacy
|discussion =
|maintainer = Moodle HQ
}}

The Data privacy plugin provides the workflow for users to submit subject access requests and for the site administrator or Data Protection Officer (DPO) to process these requests.

The Data Privacy plugin forms part of Moodle’s privacy feature set and will assist sites to become GDPR compliant. It requires Moodle 3.4.2 or later and will be integrated in the Moodle 3.5 release in May 2018.

==Data Protection Officer role==

After installing the data privacy plugin, the first thing to do is to create a [[Data Protection Officer role]] and assign it.

(If there is nobody on the site with the role of Data Protection Officer i.e. nobody with the capability to manage data requests, then a site admin can respond to data requests and manage the data registry.)

==Data requests==
[[File:requesting data.png|thumb|Requesting data]]
Any user can send a message to the Data Protection Officer via the 'Contact Data Protection Officer' link on their profile page.

In addition, they can request a copy of all of their personal data or request that their personal data should be deleted as follows:

# Go to your profile page (via the user menu).
# Click the link 'Data requests' then click the 'New request' button.
# Select 'Export all of my personal data' or 'Delete all of my personal data' as appropriate.
# Save changes.
[[File:Request approved.png|thumb|Request approved]]
The DPO will then receive a data request notification.

If the user has requested a copy of all of their personal data, once the request is approved, they will receive a notification to inform them that their personal data may be downloaded from their Data requests page. In Moodle 3.4.5 onwards, the user has by default one week to download their data before the download link expires. (An administrator can set a different expiry time for the data request in 'Privacy settings' in the Site administration.)

If the user has requested that their personal data should be deleted, once the request is approved, they will receive an email to inform them and they will no longer be able to log in to the site.

==Responding to data requests==
[[File:viewing a data request.png|thumb|Viewing a data request]]
The DPO can respond to data requests as follows:

# Go to 'Data requests' in the Site administration (or follow the link in the data request notification).
# In the Actions dropdown, select View, Approve, or Deny as appropriate.

If the user has sent a message, the privacy officer can view the message and copy the user's email address, then reply via email. In Moodle 3.4.5 onwards, after replying they can mark it as complete.

==Data registry==
[[File:data registry.png|thumb|Data registry]]
The DPO can set purposes (why the organisation is processing data) with retention periods and categories for data stored in Moodle in the data registry.

A default purpose and retention period may be set for course categories, courses, activity modules and blocks.

===Example categories===

* Administrative: Civil status, identity, identification data, images …
* Personal life (lifestyle, family situation, etc.)
* Economic and financial information (income, financial situation, tax situation, etc.)
* Connection data (IP address, logs, etc.)
* Educational Data (Assessed Coursework, exam scripts etc)
* Records of Education Attainment (Results of exams, assessments, qualifications awarded etc)
* Location data (travel, GPS data, GSM, etc.)

===Data registry set-up===

To add purposes and categories:

# Go to 'Data registry' in the Site administration.
# In the Edit menu select Categories.
# On the 'Edit categories' page, click the + button to add a new category.
# Enter a category name and description then click the Save button.
# Go to 'Data registry' again and in the Edit menu select Purposes.
# On the 'Edit purposes' page, click the + button to add a new purpose.
# Enter a purpose name, description and retention period then click the Save button.

To set default categories and purposes:

# In 'Data registry' in the Site administration click the 'Set defaults' button.
# Select a default category and purpose for the site, and for users, course categories, courses, activity modules and blocks as required.
# Save changes.

==Capabilities==

* [[Capabilities/tool/dataprivacy:managedataregistry|Manage data registry]]
* [[Capabilities/tool/dataprivacy:managedatarequests|Manage data requests]]
* [[Capabilities/tool/dataprivacy:makedatarequestsforchildren|Make data requests for children]]

==See also==

* [[GDPR for administrators (Moodle 3.4.2+)]]
* [https://gdprdemo.moodle.net/ Moodle GDPR sandbox demo site] for exploring all the [[Policies plugin]] and Data privacy plugin functionality

[[Category: Privacy]]

[[es:Plugin de privacidad de datos]]
[[de:Schutz persönlicher Daten]]

Capabilities/mod/assign:viewgrades

2018-09-07T14:30:52Z

Tsala: viewing feedback files (MDL-62782)

{{Capabilities}}
* This capability allows a user to view assignment grades and feedback (both text and uploaded files) without being able to change them.
* This capability is set to 'Allow' for managers, teachers and non-editing teachers and is not set for other roles.

[[Category:Capabilities|Grade]]
[[Category:Grades]]

[[Es:Capabilities/mod/assign:viewgrades]]
[[de:Capabilities/mod/assign:viewgrades]]

Grade viewer role

2018-09-07T14:28:28Z

Tsala: viewing feedback files (MDL-62782)

{{Roles}}
The Grade viewer role may be used for a Moderator, a Facilitator, Assistant Teacher, Inspector, or any person who needs to view the course grades of students without being able to modify them. Typically, this person would be able to view assignment grades and feedback (both text and uploaded files), although the role may also be extended to include being able to view (but not edit) quiz grades or other gradable activities.

==Creating the Grade viewer role==
*As an administrator, go to ''Site administration>Users>Permissions>Define roles'' and click the 'Add a new role' button at the bottom of the screen.
*On the next screen, choose 'Non-editing teacher' as role archetype and click 'Continue'
*Give the role a name and if desired a description and tick the "System" context:

[[File:Gradeviewer.png|center|thumb|600px]]

*In the filter, type 'view courses' to display the capability 'view courses without participation' and set this to 'Allow':

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

==Viewing assignment grades without editing them==
*In the filter, type 'assign' to display the assignment capabilities.
*Set to 'Prevent' the following capabilities:
**mod/assign:grade
**mod/assign:grantextension
**mod/assign:manageallocations
**mod/assign:managegrades
**mod/assign/releasegrades

*Set to 'Allow' the following capabilities:
**mod/assign:viewgrades
**mod/assign:view

==Viewing quiz results without editing them==
*In the filter, type 'quiz' to display the quiz capabilities.
*Set to 'Prevent' the following capabilities:
**mod/quiz:grade
**mod/quiz:manage
**mod/quiz:manageoverrides
**mod/quiz:regrade

*Click 'Create this role'

==Assigning a user the role of Grade viewer==
#As an administrator, go to ''Site administration > Users > Permissions > Assign system roles''.
#You should now see your newly created role here
#Assign the role to the required users.

''Note'': the users will have view only access to any course on your site and will be able to see but not grade assignments and quizzes.

If you would like to restrict the role further, then you can create the role in the 'Course' context; set 'view courses without participation' to 'Non-set' and then enrol the user into the relevant courses with the role of Grade viewer.

[[Category:Grades]]

[[es:Observador de calificación]]

Grade viewer

2018-09-07T14:27:42Z

Tsala: Tsala moved page Grade viewer to Grade viewer role

#REDIRECT [[Grade viewer role]]

Grade viewer role

2018-09-07T14:27:42Z

Tsala: Tsala moved page Grade viewer to Grade viewer role

{{Roles}}
The Grade viewer role may be used for a Moderator, a Facilitator, Assistant Teacher, Inspector, or any person who needs to view the course grades of students without being able to modify them. Typically, this person would be able to view assignment grades and text feedback,although the role may also be extended to include being able to view (but not edit) quiz grades or other gradeable activities. (Note the role does not permit the person to view uploaded feedback files.)
==Creating the Grade viewer role==
*As an administrator, go to ''Site administration>Users>Permissions>Define roles'' and click the 'Add a new role' button at the bottom of the screen.
*On the next screen, choose 'Non-editing teacher' as role archetype and click 'Continue'
*Give the role a name and if desired a description and tick the "System" context:

[[File:Gradeviewer.png|center|thumb|600px]]

*In the filter, type 'view courses' to display the capability 'view courses without participation' and set this to 'Allow':

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

==Viewing assignment grades without editing them==
*In the filter, type 'assign' to display the assignment capabilities.
*Set to 'Prevent' the following capabilities:
**mod/assign:grade
**mod/assign:grantextension
**mod/assign:manageallocations
**mod/assign:managegrades
**mod/assign/releasegrades

*Set to 'Allow' the following capabilities:
**mod/assign:viewgrades
**mod/assign:view

==Viewing quiz results without editing them==
*In the filter, type 'quiz' to display the quiz capabilities.
*Set to 'Prevent' the following capabilities:
**mod/quiz:grade
**mod/quiz:manage
**mod/quiz:manageoverrides
**mod/quiz:regrade

*Click 'Create this role'

==Assigning a user the role of Grade viewer==
#As an administrator, go to ''Site administration > Users > Permissions > Assign system roles''.
#You should now see your newly created role here
#Assign the role to the required users.

''Note'': the users will have view only access to any course on your site and will be able to see but not grade assignments and quizzes.

If you would like to restrict the role further, then you can create the role in the 'Course' context; set 'view courses without participation' to 'Non-set' and then enrol the user into the relevant courses with the role of Grade viewer.

[[Category:Grades]]

[[es:Observador de calificación]]

Data privacy

2018-09-05T07:42:26Z

Tsala: marking messages as complete in 3.4.5 (MDL-62026)

{{Infobox plugin
|type = Admin tools
|entry = https://moodle.org/plugins/tool_dataprivacy
|tracker = https://tracker.moodle.org/issues/?jql=component%20%3D%20Privacy
|discussion =
|maintainer = Moodle HQ
}}

The Data privacy plugin provides the workflow for users to submit subject access requests and for the site administrator or Data Protection Officer (DPO) to process these requests.

The Data Privacy plugin forms part of Moodle’s privacy feature set and will assist sites to become GDPR compliant. It requires Moodle 3.4.2 or later and will be integrated in the Moodle 3.5 release in May 2018.

==Data Protection Officer role==

After installing the data privacy plugin, the first thing to do is to create a [[Data Protection Officer role]] and assign it.

(If there is nobody on the site with the role of Data Protection Officer i.e. nobody with the capability to manage data requests, then a site admin can respond to data requests and manage the data registry.)

==Data requests==
[[File:requesting data.png|thumb|Requesting data]]
Any user can send a message to the Data Protection Officer via the 'Contact Data Protection Officer' link on their profile page.

In addition, they can request a copy of all of their personal data or request that their personal data should be deleted as follows:

# Go to your profile page (via the user menu).
# Click the link 'Data requests' then click the 'New request' button.
# Select 'Export all of my personal data' or 'Delete all of my personal data' as appropriate.
# Save changes.
[[File:Request approved.png|thumb|Request approved]]
The DPO will then receive a data request notification.

If the user has requested a copy of all of their personal data, once the request is approved, they will receive a notification to inform them that their personal data may be downloaded from their Data requests page.

If the user has requested that their personal data should be deleted, once the request is approved, they will receive an email to inform them and they will no longer be able to log in to the site.

==Responding to data requests==
[[File:viewing a data request.png|thumb|Viewing a data request]]
The DPO can respond to data requests as follows:

# Go to 'Data requests' in the Site administration (or follow the link in the data request notification).
# In the Actions dropdown, select View, Approve, or Deny as appropriate.

If the user has sent a message, the privacy officer can view the message and copy the user's email address, then reply via email. In Moodle 3.4.5 onwards, after replying they can mark it as complete.

==Data registry==
[[File:data registry.png|thumb|Data registry]]
The DPO can set purposes (why the organisation is processing data) with retention periods and categories for data stored in Moodle in the data registry.

A default purpose and retention period may be set for course categories, courses, activity modules and blocks.

===Example categories===

* Administrative: Civil status, identity, identification data, images …
* Personal life (lifestyle, family situation, etc.)
* Economic and financial information (income, financial situation, tax situation, etc.)
* Connection data (IP address, logs, etc.)
* Educational Data (Assessed Coursework, exam scripts etc)
* Records of Education Attainment (Results of exams, assessments, qualifications awarded etc)
* Location data (travel, GPS data, GSM, etc.)

===Data registry set-up===

To add purposes and categories:

# Go to 'Data registry' in the Site administration.
# In the Edit menu select Categories.
# On the 'Edit categories' page, click the + button to add a new category.
# Enter a category name and description then click the Save button.
# Go to 'Data registry' again and in the Edit menu select Purposes.
# On the 'Edit purposes' page, click the + button to add a new purpose.
# Enter a purpose name, description and retention period then click the Save button.

To set default categories and purposes:

# In 'Data registry' in the Site administration click the 'Set defaults' button.
# Select a default category and purpose for the site, and for users, course categories, courses, activity modules and blocks as required.
# Save changes.

==Capabilities==

* [[Capabilities/tool/dataprivacy:managedataregistry|Manage data registry]]
* [[Capabilities/tool/dataprivacy:managedatarequests|Manage data requests]]
* [[Capabilities/tool/dataprivacy:makedatarequestsforchildren|Make data requests for children]]

==See also==

* [[GDPR for administrators (Moodle 3.4.2+)]]
* [https://gdprdemo.moodle.net/ Moodle GDPR sandbox demo site] for exploring all the [[Policies plugin]] and Data privacy plugin functionality

[[Category: Privacy]]

[[es:Plugin de privacidad de datos]]
[[de:Schutz persönlicher Daten]]

Publish as LTI tool

2018-09-04T14:47:33Z

Tsala: /* Sharing access to a course or activity */ launch URL (new in Moodle 3.4.5) (MDL-57741)

{{Enrolment}}
==Moodle as an LTI provider==

The 'Publish as LTI tool' enrolment plugin, together with the LTI authentication plugin, allows remote users on a different site (known as an LTI consumer) to access selected courses and activities. In other words, Moodle functions as an LTI tool provider. Grades are sent back to the remote system. See the screencast [https://www.youtube.com/watch?v=cMQiKjXdm3A Publish as LTI tool] for a demonstration.

If your moodle instance is using HTTP (and not HTTPS) you will only be able to use the tool on sites that are also using HTTP (and not HTTPS). It's recommended that you use HTTPS on your moodle instance. See [[Transitioning to HTTPS]]

Note: LTI 2 is supported in Moodle 3.2, making it easier for others to access your shared content.

==Enabling 'Publish as LTI tool' at site level==

An administrator can enable the 'Publish as LTI tool' for use across the site:

# Go to ''Site administration > Plugins > Authentication > Manage authentication'' and enable LTI
# Go to ''Site administration > Plugins > Enrolments > Manage enrol plugins'' and enable 'Publish as LTI tool'

It is recommended that the site administration setting 'Allow frame embedding' is enabled (in "Site Administration > Security > HTTP security") so that tools are displayed within a frame rather than in a new window.

==Sharing access to a course or activity==
[[File:published tools.png|thumb|Published tools]]
# Go to the 'Enrolment methods' page and add 'Publish as LTI tool' as an enrolment method
# In 'Tool to be published' select the course or activity to be shared
# Click the 'Add method' button
# Go to ''Course Administration > Published as LTI tools'' page (/enrol/lti/index.php?courseid=''n'') and make a note of the launch details or just the registration URL for the LTI consumer site (see below for info on which to choose). The URL will be of the form: .../enrol/lti/...
# You will also need to give the LTI consumer site a consumer key - this can be anything you want.

{{New features}}The LTI consumer can be another Moodle site or any other LTI-consumer-compliant LMS, such as Sakai. Depending on the requirements of the LTI consumer, you can provide either a cartridge URL (also called configuration URL) plus secret OR a launch URL (new in Moodle 3.4.5) OR a registration URL.

Grade and user synchronisation (if required) are done via the 'Publish as LTI tool grade sync' and 'Publish as LTI tool users sync' [[Scheduled tasks|scheduled tasks]], which run by default every 30 minutes.

If user synchronisation is set to yes, enrolled users in the remote system are synchronised with enrolments in the course, with an account created for each remote user as necessary, and the user enrolled or unenrolled as required. If set to no, at the moment when a remote user accesses the tool, an account will be created for them and they will be automatically enrolled.

==LTI 1 or LTI 2?==

LTI 1 actually means a launch URL (which is compatible with LTI 1 or LTI 2 compliant consumers). LTI 2 actually means a proxy (which is compatible with LTI 2 compliant consumers).

{| class="nicetable"
|-
!IMS Spec
!Moodle
!Canvas
!Edu app center (Canvas)
!Desire2Learn
!Blackboard
!Sakai
|-
|Tool consumer
|External Tool
|External App
|App
|Link
|LTI Tool provider*
|Sakai Basic LTI portlet
|-
|Launch URL
|Tool URL
|Launch URL
|n/a
|URL
|Provider Domain
|Remote Tool URL
|-
|Secret
|Secret
|Secret
|Secret
|Secret
|Tool Provider Secret
|Remote tool secret
|-
|Cartridge URL
|Tool URL
|Paste XML
|Configuration URL
|n/a
|n/a
|Tool registration file?
|-
|Proxy URL
|Registration URL/Tool URL
|LTI 2 Registration URL
|n/a
|n/a
|n/a
| -
|}

==On the LTI consumer site==

# Visit a course.
# Add a LTI activity
#Give it a name and save the changes.
#Enter the LTI activity settings again
#Click on the + icon to the right of the 'Preconfigured tool' dropdown
#On a separate tab on your browser, enter the Cartridge URL (ending in .xml)
#Find "<blti:launch_url>" and copy the link which appears after that. (It will be in the fomat [yourmoodlesiteurl]/enrol/lti/tool.php?id=x)
#Back on the previous tab (External tool configuration), enter a Tool Name, the Tool URL (paste the link you just copied), any consumer key you want, and in the Shared Secret, enter the Secret. Save your changes.
#Navigate back to your course page, and again, go to the settings of your LTI.
#Now choose the LTI that you just created from the 'Preconfigured tool' dropdown, and save your changes.
# Log in as a student.
# Visit the course and click on the LTI activity.
# Check the activity displays as expected.

==See also==

* [[LTI and Moodle]]
* [https://moodle.org/mod/forum/discuss.php?d=345828 LTI authentication not working] forum discussion

==Any further questions?==

Please post in the [http://moodle.org/mod/forum/view.php?id=7978 LTI and Moodle forum] on moodle.org

[[Category:LTI]]

[[es:Herramienta publicar como LTI]]
[[de:Als LTI-Tool bereitstellen]]

File:published tools.png

2018-09-04T14:46:22Z

Tsala: Tsala uploaded a new version of File:published tools.png

External tool settings

2018-09-03T13:27:03Z

Tsala: /* External tool capabilities */ mod/lti:admin (MDL-58851)

{{External tool}}
==Adding a new external tool to a course==
[[File:preconfigured tool in activity chooser.png|frame|right|A preconfigured tool 'Chemistry quiz' shown in the activity chooser]]

#With the editing turned on, in the section you wish to add your external tool, click the "Add an activity or resource" link and choose either 'External tool' or a preconfigured tool.
#This will take you to the settings page titled "Adding a new external tool". All settings may expanded by clicking the "Expand all" link top right.
#If the external tool has not been configured by the administrator, you will need to have in advance the correct URL, consumer key and secret. These should have been provided to you by the managers of the LTI-compliant website you are going to be connecting to. Click "Show more" to access the consumer key and secret fields.

==General settings==
{|
|[[File:externaltool26.png|thumb|400px|General settings before expanding. When expanded, [https://docs.moodle.org/en/File:externaltoolexpanded.png extra options are available.]]]
|}
*'''Activity name''' - give the title you wish the students to see on the course page
*'''Preconfigured tool''' - this is how Moodle communicates with the tool provider. If in doubt, leave as default. If your administrator has made a tool available site-wide, you will be able to select it here:
{|
| [[File:sitewidetool.png|Selecting a preconfigured tool]]
|}
*'Select content' button - for LTI Content-Item configuration
*'''Tool URL''' - This is the URL for connecting to site. If your moodle site uses [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL] (is on [[HTTPS]]) you will only be able to use a tool that also uses [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL]. Make sure the tool URL has [[HTTPS]] before attempting to use it or you may get a blank page.
*'''Launch container'''- this is how the external tool will be displayed.
**Default - if in doubt; leave as default
**Embed - the external tool will be embedded in the Moodle course page with blocks and navigation bar
**Embed without blocks - the external tool will be embedded in the Moodle course page but without blocks
**New Window - the external tool will open in a new window. (A new window or tab will open with the External tool and the old browser window containing the course page will not change.)

''The following settings are available by clicking ""Show more":''
*'''Activity description''' - give a short description here
*'''Display description on course page''' - choose to show the description along with the activity name
*'''Display activity name when launched''' - have this appear when the student clicks the link.
*'''Display activity description when launched''' - have this appear when the student clicks the link.
*'''Secure tool URL''' - This overrides the tool URL when moodle uses [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL] (if your site is configured to use [[HTTPS]] in the wwwroot)
*'''Consumer key''' -this tells the connecting LTI compliant site that your Moodle is allowed to connect. The "tool provider", ie the manger of the connecting LTI compliant site will issue you with this key. If you are merely linking to a tool with no secure access or gradebook sharing then you won't need a consumer key. If you are linking to a course or activity from another Moodle site, then you can add any consumer key.
*'''Shared secret''' - this is the "password" to connect to the tool - the LTI compliant site.
*'''Custom parameters''' - most times you can leave this blank. The tool provider might use this to allow you to display a specific resource.
*'''Icon URL''' - you can display a different icon from the default External Tool icon by entering its URL here
*'''Secure Icon URL''' - enter the URL of a different icon here if your students are accessing Moodle securely via [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL].

==Privacy settings==
(These settings are collapsed by default)
{|
|[[File:externaltoolprivacy25.png|Privacy settings expanded]]
|}

*'''Share launcher's name with the tool''' - this means that the student's name will be displayed on the connected site [[ Media:demoexternaltool.png| as in this example]]
*'''Share launcher's email with the tool''' - this means that the student's email will be displayed on the connected site [[Media:externaltoolfrontpage.png| as in this example]]
*'''Accept grades from the tool''' - if this is checked, the connecting site will send back grades to Moodle's gradebook. See [[Using External tool]] for more information on this.

==Site administration settings==

===Adding a tool site-wide===

An administrator can manually configure external tools in ''Site administration > Plugins > Activity modules > External tool> Manage tools'' so that they are available across the site.

[[File:LTIAddTool.png|thumb|center|450px|Adding an external tool]]

A tool may be configured by an administrator so that it is shown in the activity chooser (in addition to the external tool activity) for a teacher to select to add to a course. Its description, if one is present, will appear in the activity chooser.

===Registering a tool using a cartridge===

You can register a tool type using a cartridge. A cartridge will configure all the information such as launch url, tool name & description and icons for you.

To do this, simply enter the url to a tool's cartridge in the 'Tool URL' and press 'Add'. You will be asked to enter a key and secret. If you don't have them, you can leave them blank and press save changes.

[[File:LTIKeyAndSecret.png|thumb|center|450px|Entering a consumer key and secret]]

===Registering an external tool===

To register an external tool, simply enter the url to a tool in the 'Tool URL' and press 'Add'.

This will open the tool, which may in turn ask you to decide on some settings.

[[File:LTIConfirmCapabilities.png|thumb|center|450px|Viewing and confirming capabilities]]

Then you will be shown the capabilities the tool wants to use and you can decide if you want to allow the tool or not.

=== Viewing more details ===

On the 'Manage tools' page you can also visit 'Manage preconfigured tools' to view the preconfigured tools in a tabular format.

There are tabs to add an external tool, to view those which are pending and to view those which have been rejected:
{|
| [[File:LTItype.png|thumb|450px|Setting up a new external tool]]
|}

You can also visit 'Manage external tool registrations' to view the tool registrations in a tabular format, or to add an external registration with limited capabilities.

To add a tool with limited capabilities.
1. Click 'Configure a new external tool registration'
[[File:LTIreg.png|thumb|450px|center|Registering an external tool]]
2. Configure the details on the settings page:
[[File:LTIregdetails1.png|450px|center|Registration settings page]]

'Memberships', allow the external tool to request a list of users with a certain role in a specified context e.g. users enrolled in a course.

3. Click the tick/checkmark to register:
[[File:ticktoreg.png|center|thumb|450px|Activating]]
4. After obtaining a success message, click to complete the process:
[[File:reqmet.png|450|thumb|center|Completing the registration]]
5. If all requirements are met then you will be able to register automatically.

6. Now go to ''Site administration > Plugins > Activity modules > External tool > Manage external tool types'' and click the 'Pending tab'

7. Click the tick/checkmark to activate it:
[[File:pendingactivate.png|thumb|center|450px|Activating from the Pending tab]]

See the screencast [http://www.spvsoftwareproducts.com/temp/lti2-moodle/ External tool registration] for a demonstration of the above steps.

==External tool capabilities==

*[[Capabilities/mod/lti:addcoursetool|Add course-specific tool configurations]]
*[[Capabilities/mod/lti:addinstance|Add a new external tool]]
*[[Capabilities/mod/lti:requesttooladd|Submit a tool to admins for configuration]]
*[[Capabilities/mod/lti:admin|Be an admin when the tool is launched]]
*[[Capabilities/mod/lti:manage|Edit external tool activities]] i.e. be an Instructor when the tool is launched
*[[Capabilities/mod/lti:view|View external tool activities]] i.e. launch external tool activities

[[es:Configuraciones de herramienta externa]]
[[de:Externes Tool konfigurieren]]

Capabilities/mod/lti:admin

2018-09-03T13:25:52Z

Tsala: capabilities template, description, see also, categories (MDL-58851)

{{Capabilities}}
* This allows a user to be an admin in an [[External tool]] activity
* This capability is not allowed for any of the default roles

==See also==

* MDL-58851 for details of the reasoning behind this capability

[[Category:Capabilities|LTI]]
[[Category:External tool]]

Participants

2018-08-27T08:15:04Z

Tsala: City/town or country (MDL-59436)

{{Course enrolment}}
==About==
{{New features}}The Participants page enables teachers to easily enrol, view, search for, filter, edit and delete course participants.

The Participants page can be accessed from the navigation drawer in the [[Boost theme]] or the Administration block in other themes. It can also be accessed from the More link in the gear menu, by clicking Enrolled users in the Users tab.

{{MediaPlayer | url = https://youtu.be/jj_ynDPpHBk | desc = 3.4 Participants and Enrolments Page}}

==Enrolling users==
Users may be enrolled from the Enrol users button at the top right and bottom right of the screen.

[[File:NewEnrolUsers.png]]

==Filtering and searching for users==
The filter at the top left of the screen allows for filtering by period of activity, enrolment method, group, role and status:

[[File:ParticipantsFilter.png]]

==Roles==
*To assign an enrolled user a role, click the pencil icon in the Roles column then select the desired role and click the save icon to confirm the change.
*To remove a role assignment, click the delete icon (a cross) next to the role name.
*Only roles which can be assigned in the course context type are available to select. The course context type may be set by an admin by editing the role via Site administration > Users > Permissions > Define roles.
*Only roles which a user is allowed to assign are available to select.

==Groups==
To add a user to a group (requires at least one group to have been created previously), click the pencil icon in the Groups column, select the group and then click the save icon to confirm the change.

[[File:NewGroupSelect.png]]

==Status==
The status column shows the current status of a user's enrolments, for example Active or Suspended. Where a user has two different enrolment types (eg manual/cohort sync) both are displayed in the status column:

[[File:Statuscolumn.png]]

==City/town or country==

Users' city/town or country may be displayed for users with the capability moodle/site:viewuseridentity (by default manager, teacher and non-editing teacher) by selecting these fields in 'Show user identity' in [[User policies]] in the Site administration.

==Sending a message, adding a note, or editing manual user enrolments==

You can send a message, add a note, or edit or delete selected manual user enrolments via the dropdown menu below the list of course participants.

Note that only users who were previously ''manually'' enrolled can have their enrolment edited or deleted in bulk. The enrolment for users who enrolled using a different enrolment method, such as self enrolment, may be edited or deleted via the edit enrolment link (cog icon) in the status column.

[[File:BulkEditDeleteUsers.png]]

[[es:Participantes]]
[[de:Teilnehmer/innen]]

Upgrading

2018-08-27T08:08:48Z

Tsala: /* Possible issues that may affect you in Moodle {{Version}} */ Participants

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Check that your server meets all requirements for {{Version}} in ''Administration > Site administration > Server > [[Environment]]''.

See the [{{Release notes}} release notes] in the dev docs for software requirements.

Notes:

* You can only upgrade to Moodle {{Version}} from Moodle 3.0 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/30/en/Upgrading_to_Moodle_3.0 upgrade to 3.0] as a first step.
* The minimum PHP version has increased and is now 7.0.0.
* The PHP extension '''intl''' is now required in Moodle 3.4 (previously it was only recommended).

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

Consider setting the [[Upgrade key|upgrade key]] for your site.

== Backup important data ==

There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

==Put your site into maintenance mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in. Then you should wait for any currently running cron processes to complete before proceeding.

== Install the new Moodle software ==
You can fetch the current version of the software through

wget http://sourceforge.net/projects/moodle/files/Moodle/stable{{Version2}}/moodle-latest-{{Version2}}.tgz

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the Migration documents.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-{{Version}}.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.

chown -R www-data:www-data moodle (Linux debian - change to appropriate user and group for your OS version)
chmod -R 755 moodle

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle {{Version}} supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

== Finishing the upgrade ==

The last step is to trigger the upgrade processes within Moodle.

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to ''Administration > Site administration > Notifications''.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 3.0 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 3.0 config-dist.php.

===Cron===

Cron has received a major update (MDL-25499) and now has support for both scheduled and ad hoc tasks.

The benefits of these changes are:
* The schedule for every task can be configured by the admin
* Tasks can run in parallel
* Cron processes use locking to prevent the same task running at the same time by different processes
* Clusters with multiple identical application nodes are supported, you can run cron on all of them

A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner. To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least ''once per minute''.

You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string "Cron script completed correctly" (if that is what you were doing). An alternative is to monitor the output for the string "task failed:". If you detect that a task is failing, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure.

Before the upgrade, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade.

===Assignments===

The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one.

If you are still using the old assignment (2.2) module, after upgrading to Moodle 3.0 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.

If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 3.0, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.

==Possible issues that may affect you in Moodle {{Version}}==

* Setting "Use HTTPS for logins" ('loginhttps') was completely removed since it provided false sense of security. If it was enabled before upgrade the whole site will be served via HTTPS protocol. [[HTTPS conversion tool]] is available for administrator to convert links to embedded contents from http to https.
* Minimum supported PHP version was raised to 7.0. You cannot run your Moodle 3.4 site on PHP 5.6 or lower (please refer to [https://docs.moodle.org/dev/Moodle_3.4_release_notes#Server_requirements requirements section] for details).
* The following authentication plugins were removed from core and can be found at the following URLs. If you use them, you must provide them manually during the upgrade (MDL-50925).
** FirstClass (auth_fc) - https://github.com/moodlehq/moodle-auth_fc
** IMAP Mail server (auth_imap) - https://github.com/moodlehq/moodle-auth_imap
** Network News Transfer Protocol (auth_nntp) - https://github.com/moodlehq/moodle-auth_nntp
** Pluggable Authentication Modules (auth_pam) - https://github.com/moodlehq/moodle-auth_pam
** POP3 Mail server (auth_pop3) - https://github.com/moodlehq/moodle-auth_pop3.
* The Messages block has been removed from the standard distribution. The new messages notification is displayed on the top of every page and this block is no longer needed. Block can be [https://github.com/moodlehq/moodle-block_messages manually downloaded] if needed
* Support for custom registration hubs has been completely removed. Registration and course publishing is possible only with https://moodle.net
* Course restore and import operations now will never change user dates and log dates. Only activity dates (due, open/close, etc.) will now change respective of the new course start date.
* The [[Participants]] page no longer shows users' city/town or country unless specified in 'Show user identity' in 'User policies' in the Site administration.

See the [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]] for the full list of changes in Moodle {{Version}}.

=== Moodle 3.1, 3.2 and 3.3 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/31/en/Upgrading Upgrading to Moodle 3.1]
* [https://docs.moodle.org/32/en/Upgrading Upgrading to Moodle 3.2]
* [https://docs.moodle.org/33/en/Upgrading Upgrading to Moodle 3.3]

==See also==

* [[Installation]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation help forum]
* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

Upgrading

2018-08-27T08:06:51Z

Tsala: /* Possible issues that may affect you in Moodle {{Version}} */ MDL-59436

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Check that your server meets all requirements for {{Version}} in ''Administration > Site administration > Server > [[Environment]]''.

See the [{{Release notes}} release notes] in the dev docs for software requirements.

Notes:

* You can only upgrade to Moodle {{Version}} from Moodle 3.0 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/30/en/Upgrading_to_Moodle_3.0 upgrade to 3.0] as a first step.
* The minimum PHP version has increased and is now 7.0.0.
* The PHP extension '''intl''' is now required in Moodle 3.4 (previously it was only recommended).

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

Consider setting the [[Upgrade key|upgrade key]] for your site.

== Backup important data ==

There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

==Put your site into maintenance mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in. Then you should wait for any currently running cron processes to complete before proceeding.

== Install the new Moodle software ==
You can fetch the current version of the software through

wget http://sourceforge.net/projects/moodle/files/Moodle/stable{{Version2}}/moodle-latest-{{Version2}}.tgz

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the Migration documents.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-{{Version}}.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.

chown -R www-data:www-data moodle (Linux debian - change to appropriate user and group for your OS version)
chmod -R 755 moodle

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle {{Version}} supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

== Finishing the upgrade ==

The last step is to trigger the upgrade processes within Moodle.

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to ''Administration > Site administration > Notifications''.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 3.0 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 3.0 config-dist.php.

===Cron===

Cron has received a major update (MDL-25499) and now has support for both scheduled and ad hoc tasks.

The benefits of these changes are:
* The schedule for every task can be configured by the admin
* Tasks can run in parallel
* Cron processes use locking to prevent the same task running at the same time by different processes
* Clusters with multiple identical application nodes are supported, you can run cron on all of them

A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner. To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least ''once per minute''.

You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string "Cron script completed correctly" (if that is what you were doing). An alternative is to monitor the output for the string "task failed:". If you detect that a task is failing, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure.

Before the upgrade, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade.

===Assignments===

The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one.

If you are still using the old assignment (2.2) module, after upgrading to Moodle 3.0 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.

If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 3.0, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.

==Possible issues that may affect you in Moodle {{Version}}==

* Setting "Use HTTPS for logins" ('loginhttps') was completely removed since it provided false sense of security. If it was enabled before upgrade the whole site will be served via HTTPS protocol. [[HTTPS conversion tool]] is available for administrator to convert links to embedded contents from http to https.
* Minimum supported PHP version was raised to 7.0. You cannot run your Moodle 3.4 site on PHP 5.6 or lower (please refer to [https://docs.moodle.org/dev/Moodle_3.4_release_notes#Server_requirements requirements section] for details).
* The following authentication plugins were removed from core and can be found at the following URLs. If you use them, you must provide them manually during the upgrade (MDL-50925).
** FirstClass (auth_fc) - https://github.com/moodlehq/moodle-auth_fc
** IMAP Mail server (auth_imap) - https://github.com/moodlehq/moodle-auth_imap
** Network News Transfer Protocol (auth_nntp) - https://github.com/moodlehq/moodle-auth_nntp
** Pluggable Authentication Modules (auth_pam) - https://github.com/moodlehq/moodle-auth_pam
** POP3 Mail server (auth_pop3) - https://github.com/moodlehq/moodle-auth_pop3.
* The Messages block has been removed from the standard distribution. The new messages notification is displayed on the top of every page and this block is no longer needed. Block can be [https://github.com/moodlehq/moodle-block_messages manually downloaded] if needed
* Support for custom registration hubs has been completely removed. Registration and course publishing is possible only with https://moodle.net
* Course restore and import operations now will never change user dates and log dates. Only activity dates (due, open/close, etc.) will now change respective of the new course start date.
* The Participants page no longer shows users' city/town or country unless specified in 'Show user identity' in 'User policies' in the Site administration.

See the [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]] for the full list of changes in Moodle {{Version}}.

=== Moodle 3.1, 3.2 and 3.3 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/31/en/Upgrading Upgrading to Moodle 3.1]
* [https://docs.moodle.org/32/en/Upgrading Upgrading to Moodle 3.2]
* [https://docs.moodle.org/33/en/Upgrading Upgrading to Moodle 3.3]

==See also==

* [[Installation]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation help forum]
* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

User policies

2018-08-27T07:50:31Z

Tsala: /* Show user identity */ City/town and country (MDL-59436)

{{Roles}}
==User policies==
The following settings may be changed by an administrator in ''User policies'' in the Site administration.

===Role for visitors===
Users who are not logged in to the site will be treated as if they have the role specified here, granted to them at the site context. The role of Guest is the default and the recommended setting for standard Moodle sites. The user will still be required to login to participate in an activity.

===Role for guest===
This option specifies the role that will automatically be assigned to the guest user. This role is also temporarily assigned to non enrolled users when they enter a course that allows guests without password.

(If you wish to deny guest access to a site altogether, the guest login button should be set to hide in ''Manage authentication'' in the Site administration.)

===Default role for all users===

It is recommended that the default role for all users is set to [[Authenticated user]]. To set it to a custom role, the custom role must be assignable in the system context and have role archetype set to none.

Note: It is not recommended that the default role for all users is set to student.

===Auto-login guest===

If not set, then visitors must click the "Login as a guest" button before entering a course which allows [[Guest|guest access]].

Note: If auto-login guest is set, the guest login button also needs to be set to show in ''Manage authentication'' in the Site administration, even though visitors won't necessarily use it.

===Hide user fields===
The following user fields appear on users' profile pages. Certain user fields are also listed on the course participants page. You can increase student privacy by hiding selected user fields.

Description, city/town, country, web page, ICQ number, Skype ID, Yahoo ID, AIM ID, MSN ID, last access, My courses and first access and groups

*User fields on users' profile pages are hidden from all users with the capability [[Capabilities/moodle/user:viewhiddendetails|moodle/user:viewhiddendetails]] not set.
*User fields on the course participants page are hidden from all users with the capability [[Capabilities/moodle/course:viewhiddenuserfields|moodle/course:viewhiddenuserfields]] not set.

===Show user identity===

Any of the following fields may be shown to users with the capability [[Capabilities/moodle/site:viewuseridentity|moodle/site:viewuseridentity]] when searching for users and displaying lists of users.

*ID number
*Email address
*Phone number
*Mobile phone
*Department
*Institution
*City/town (new in 3.4)
*Country (new in 3.4)

This setting is useful for sites with large number of users, where the likelihood of users with the same name is high.

Locations where user identity fields are shown are as follows:

*User selectors ([[Assign roles]] in some places, [[Groups|groups]], forum subscribers)
*[[Browse list of users]]
*[[Participants]]
*[[Gradebook|Grader report]]
*[[Quiz reports]]
*[[Using SCORM|SCORM reports]]
*[[Using Assignment|Assignment submissions]]
*[[Using Course completion|Course completion report]]
*[[Using Activity completion|Activity completion report]]

Tip: Select only one or two fields that are mandatory at your institution. Do not select more than two fields otherwise tables become very wide.

===Full name format===

See [[Additional name fields]] for details, also about the alternative full name format.

===Maximum users per page===

You can choose here the maximum number of users to be displayed when searching in courses, groups, cohorts etc. The default is 100 but if your Moodle site is very large you can increase the number here.

===Enable Gravatar===

[http://gravatar.com/ Gravatar] (an abbreviation for globally recognized avatar) is a service for providing globally unique avatars.

If a user has not uploaded a user picture, Moodle will check whether the user's email address has an associated gravatar and if so, will use the gravatar as the user's picture.

* [http://www.youtube.com/watch?v=Z4b7tJedlMA Use your Gravatar in Moodle 2.2 screencast]

===Gravatar default image URL===

In Moodle 2.3.3 onwards, if gravatars are enabled, an alternative default user picture may be specified. The options are:

* A gravatar default image - by entering a code such as mm. See https://en.gravatar.com/site/implement/images/ for codes of other gravatar default images.
* A specified image - by entering the image URL

If the field is left empty then the theme's default user picture is used.

==Unsupported role assignments==

Unsupported role assignments are role assignments in contexts that make no sense for that role, such as the course creator role in the course or activity context, or the teacher role in the user context.

Prior to Moodle 2.0, there was no 'Context types where this role may be assigned' setting in the edit role form, and so any role could be assigned in any context. Upon upgrading a site from 1.9, any role assignments in contexts that make no sense for that role are listed as unsupported role assignments.

In general, it is safe to delete all unsupported role assignments. In doing so, the worst that can happen is for a user to be unassigned a custom role; no other data loss will occur.

[[Category:Site administration]]

[[de:Einstellungen für Rollen]]
[[fr:Réglages des rôles]]
[[ja:ユーザポリシー]]
[[es:Políticas para el usuario]]

Self enrolment

2018-07-23T12:00:08Z

Tsala: /* Sending a welcome message to new users */ sent from first user to be assigned the role of course contact (MDL-61236)

{{Enrolment}}

{{Note|If you want your learners to create accounts on your site and have access to your courses, then you first need to enable [[Email-based self registration]] so they can create accounts, and then enable self enrolment within your course(s) so they can enrol. These are two separate steps.}}
Self enrolment is the method whereby users can choose to enrol themselves into a course, either immediately by clicking "\enrol me in this course" or by typing in an enrolment key they have been given. The enrolment plugin needs to be enabled by the site admin in [[Enrolment_plugins|Enrolment plugins]] and has to be enabled within the course. The manual enrolment plugin has to be enabled in the same course as well.

==Enabling self-enrolment in a course==

{{MediaPlayer | url = https://youtu.be/UCVfOIY1m0Y }}

1. In your course, click the Participants link from the navigation drawer (or, for non-Boost themes, click Users in the Course administration block)

2. Click the cogwheel/gear icon and click Enrolment methods(or for non-Boost themes, expand the Users link and click Enrolment methods)

[[File:BoostEnrolmentMethods.png|center]]

3. Open the "eye" icon next to the Self enrolment method:

[[File:OpenSelfEnrolment.png|center]]

===Adding an enrolment key to a course===

If you wish only a certain group of users to self enrol (and not anyone) then you can set an enrolment key which you then tell them to use when they access the self-enrolment screen. See section 1 of [[Enrolment_key|enrolment key]] for how to do this.

===Adding a group enrolment key to a course===

If you wish your users to enrol themselves directly into a group in the course then you can set a group enrolment key which you then tell them to use when they access the self-enrolment screen. See section 2 of [[Enrolment_key|enrolment key]] for how to do this.

The following settings may be changed by clicking the edit (hand/pen) icon to the right of the self-enrolment option in ''Administration > Course administration > Users > Enrolment methods'':

===Setting the enrolment period===

Tick the "enable" box to the right of Enrolment period and then choose your dates.

=== Enrolment duration===

Set the amount of time a user enrolment is valid, starting with the moment the user enrols themselves. If disabled, the enrolment duration will be unlimited.

===Notifying users when their enrolment expires===

It is possible also for students and/or teachers to be notified when enrolments expire by selecting either "Enroller only" or "Enroller and enrolled user" from the dropdown "Notify before enrolment expires" and a time in "Notification threshold".

{|
|[[File:selfenrolmenexpirynotification.png|thumb|Settings for notifiying users before enrolment expires. Click to enlarge.]]
|}

====Editing individual enrolment times====

It is possible to edit the date and hour of an individual's enrolment from ''Administration>Course administration>Users>Enrolled users'' by clicking the edit icon in the enrolment methods column for the user in question. This then brings up a screen where the date and time can be modified.

{|
|[[File:selfenrolment241.png|thumb|Click the edit icon in the enrolment methods column for the user]]
|[[File:selfenrolment242.png|thumb|Modifying the date and time]]
|}

===Unenrolling students who haven't been active on the course===

Choose from the dropdown to the right of "Unenrol inactive after..."

===Deciding the maximum number of users in your course===

Type the maximum number of users you want in your course in "Max enrolled users". When this limit is reached, nobody will be able to self-enrol. If you leave the number at 0 then there will be no maximum number.

===Allowing only cohort members to self-enrol===

If you have cohorts set up, then you can restrict self enrolment to particular cohorts by selecting the name of the cohort from the drop down box, A member of the cohort can self-enrol as normal; whereas a non-member gets a message telling them they are not able to self-enrol.

{|
|[[File:cohortselfenrol.png|thumb|Restricting self enrolment to members of a particular cohort]]
|[[File:noncohortmember.png|thumb|Message seen by a user not in a cohort who is attempting to self-enrol]]
|}

===Sending a welcome message to new users===

If enabled, users receive the following message via email when they self-enrol in a course:

Welcome to {Course name}
If you have not done so already, you should edit your profile page so that we can learn more about you: {link to profile page}

If you want to send a different message, simply type it in the custom welcome message text box.

The following placeholders may be included in the message:

Course name {$a->coursename}
Link to user's profile page {$a->profileurl}
User email {$a->email}
User fullname {$a->fullname}

The welcome message may be sent from the [[Course contacts|course contact]], the [[Keyholder]] or from the default no-reply address. If the course contact is chosen, and there is more than one user with the role, then the welcome message is sent from the first user to be assigned the role of course contact.

Note: An admin can customise the message for the whole site by editing the ''welcometocoursetext'' language string. See [[Language customisation]] for further details.

==Admin settings==
The self enrolment plugin may be enabled or disabled throughout the site in ''Administration > Site administration > Plugins > Enrolments > Manage enrol plugins.''

===Shared settings for all courses===
The page ''Administration > Site administration > Plugins > Enrolments > Self enrolment.'' contains options for defaults that admin can set:
* Require an enrolment key - if this box is ticked then all courses with self-enrolment enabled will need to have an enrolment key. The setting won't save until the teacher adds a key - something to be aware of as this can cause confusion:)
* Use password policy - tick this box if you want enrolment keys set by teachers to follow the password policy of the site.
* Show hint - tick this box if you are prepared to allow the first letter of a key to be given as a "hint"
* Enrolment expiry action - specifies what happens when user enrolments reach expiration date. Please note that option "Unenrol user from course" purges grades, group memberships, preferences and other user related data from the courses.
* Hour to send enrolment expiry notifications - specify hour for sending expiration notifications.

===Default enrolment settings in new courses===
These can be set in ''Administration > Site administration > Plugins > Enrolments > Self enrolment'' but teachers in individual courses can alter them to suit their needs:
* Add instance to new courses - if admin selects this, then any new course created will include the self enrolment plugin
* Enable self enrolments- if this is enabled then users by default can self enrol into a course.
* Use group enrolment keys - the setting for group enrolment keys in a course will be set to "yes" by default
* Default role assignment - normally, when users self enrol, they have the student role. If necessary that role can be changed by default here - for example - if your Moodle has a dedicated role you wish to use instead.
* Enrolment duration - this sets the default enrolment length for new courses (but again, may be altered by the course teacher.)
* Notify before enrolment expires - specifies if teacher or optionally students should be notified before the expiration.
* Notification threshold - specify how many days should be users notified before the enrolment expiration.
* Unenrol inactive after- this sets the default time after which a student will be unenrolled if they haven't accessed the courses. (Teachers may change this)
* Max enrolled users - adding a number here will specify the maximum number of users who can self-enrol into new courses. Teachers in the course can change this. If it is left at 0, there will be no maximum.
* Send course welcome message- if this box is checked then newly enrolled users will receive a welcome message by default.

==Self enrolment method options==
One course may contain multiple self enrolment methods. User may be enrolled once in each instance only.

* Custom instance name - specify custom enrolment method name.
* Enable existing enrolments - if disabled all users enrolled via this plugin can not access course.
* Allow new enrolments - disable if you do not want to allow students to self enrol in the future.
* Enrolment key - specify key required for enrolment.
* Use group enrolment keys - optionally use group keys for enrolment too.
* Default assigned role - specify role to be assigned to users during enrolment, this can be changed manually after enrolment.
* Enrolment duration - specify enrolment length, this can be manually after user enrolment.
* Notify before enrolment expires - specifies if teacher or optionally students should be notified before the expiration.
* Notification threshold - specify how many days should be users notified before the enrolment expiration.
* Unenrol inactive after- specify time after which a student will be unenrolled if they haven't accessed the courses.
* Max enrolled users - adding a number here will specify the maximum number of users who can self-enrol into this course.
* Only cohort members - optionally restrict this enrolment method to members of specified cohort.
* Send course welcome message- if this box is checked then newly enrolled users will receive a welcome message by default.
* Custom welcome message - specify custom message if necessary.

==Self enrolment capabilities==

*[[Capabilities/enrol/self:config|Configure self enrol instances]]
*[[Capabilities/enrol/self:manage|Manage enrolled users]]
*[[Capabilities/enrol/self:unenrol|Unenrol users from course]]
*[[Capabilities/enrol/self:unenrolself|Unenrol self from the course]]

[[de:Selbsteinschreibung]]
[[es:Auto inscripción]]

MoodleDocs:Privacy policy

2018-06-18T15:52:01Z

Tsala: link update

The privacy notice for Moodle Docs is available on moodle.org: [https://moodle.org/admin/tool/policy/view.php?policyid=1 Privacy notice].

error/local hub/freshmoodleregistrationerror2

2018-05-18T14:00:50Z

Tsala: email support@moodle.org

You are trying to register a site with a URL that was previously used by another registered site. A request to register this url has already been sent to the site administrator of this other site. This administrator (probably you) need to confirm the new registration.

As with any problem registering or updating your registration, if you need help, please email support@moodle.org.

Privacy

2018-05-18T09:40:43Z

Tsala: /* Privacy settings */ updated list default

{{Security}}
==Privacy settings==

===Digital age of consent verification===
{{New features}}[[File:age and location verification.png|thumb|Age and location verification]]
In Moodle 3.4.2 onwards, a 'Digital age of consent verification' may be enabled in 'Privacy settings' in the Site administration. The default digital age of consent, and the age in any country where it differs from the default, may be specified. Country codes are as specified in [https://en.wikipedia.org/wiki/ISO_3166-2 ISO 3166-2].

*, 16
AT, 14
ES, 14
US, 13

In the above list the default digital age is 16.
[[File:digital minor message.png|thumb|Digital minor message]]
If self-registration AND 'Digital age of consent verification' are both enabled, when a new user clicks the 'Create new account' button, they will be prompted to enter their age and country. If the user's age is lower than the age of consent for their country, they will see a message prompting them to ask their parent/guardian to contact the support contact (as specified in 'Support contact' in the Site administration).

==Policy settings==

* A site policy may be enabled by entering the URL in 'Policy settings' in the Site administration. The URL can point to any type of file anywhere online that can be accessed without a log in to your Moodle. It is not recommended that a [[Page resource|page resource]] is used as a site policy, since the site header will be repeated in the iframe (see MDL-30486).
* It is recommended that the site policy is on the same domain as Moodle to avoid the problem of Internet Explorer users seeing a blank screen when the site policy is on a different domain.
* The site policy will be displayed in a frame. You can view it via the URL ''<nowiki>yourmoodlesite.org/user/policy.php</nowiki>''.
* If [[Email-based self-registration]] is enabled on the site, a link to the site policy is displayed on the signup page.
* When a site policy URL is set, all users will be required to agree to it when they next log in before accessing the rest of the site.
* A site policy for guests may also be enabled. Guest users will need to agree to it before accessing a course with [[Guest access]] enabled.

(In versions of Moodle prior to 3.4.2, the the Site policy URL and Site policy URL for guests settings were located in 'Site policies'.)

==Forcing users to log in==

In [[Site policies]] in the Site administration:

* Force users to login by checking the ''forcelogin'' checkbox
* Keep "Force users to login for profiles" enabled to keep anonymous visitors and search engines away from user profiles

==Enrolment key usage==

If [[Self enrolment]] is used, in the Self enrolment settings in the Site administration:

* Enforce enrolment key usage by ticking the 'Require enrolment key' checkbox
* Enforce enrolment key complexity by ticking the 'Use password policy' checkbox
* Disable the [[Enrolment key|enrolment key]] hint leaving the 'Show hint' checkbox unticked

==Hiding user fields==

Increase student privacy by hiding user fields which would normally appear on users' profile pages, and in some cases on the course participants page.

The ''hiddenuserfields'' setting is in [[User policies]] in the Site administration.

User fields which may be hidden are:<br />
Description, city/town, country, web page, ICQ number, Skype ID, Yahoo ID, AIM ID, MSN ID, first access, last access, last IP address and my courses.

==See also==
* [[Data privacy plugin]] The Data Privacy plugin forms part of Moodle’s privacy feature set and will assist sites to become GDPR compliant. It requires Moodle 3.4.2 or later and will be integrated in the Moodle 3.5 release in May 2018.
* [[GDPR]] - GDPR stands for General Data Protection Regulation and refers to the European Union regulation for data protection for all individuals within the European Union
* [https://moodle.org/mod/forum/discuss.php?d=233702 Student Privacy] forum discussion

==Any further questions?==

Please post in the [http://moodle.org/mod/forum/view.php?id=7301 Security and Privacy forum] on moodle.org.

[[Category:Privacy]]

[[de:Datenschutz in Moodle]]
[[es:Privacidad]]

MoodleDocs:Overview

2018-05-18T07:07:40Z

Tsala: redirect to latest version wiki

#redirect [[:en:MoodleDocs:Overview]]

Awards

2018-05-18T07:06:08Z

Tsala: pointer to latest version wiki

#redirect [[:en:Awards]]

Creating SCORM Content

2018-05-18T07:05:28Z

Tsala: pointer to latest version wiki

The up-to-date list of tools for creating SCORM content is available in the latest Moodle Docs wiki: [[:en:Creating SCORM Content|Creating SCORM Content]].

MediaWiki:Noarticletext

2018-05-18T07:03:58Z

Tsala: updated text pointing to latest version wiki

{{Main page}}
This page does not exist. You can [[:en:{{NAMESPACE}}:{{PAGENAME}}|check whether it exists in the documentation for the latest stable version of Moodle]] or [[Special:Search/{{PAGENAME}}|search for this page title]] in other pages.

You are also welcome to [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} create it] yourself :-)

==See also==

*[[MoodleDocs:Guidelines for contributors]]

MediaWiki:MoodleDocsVersionLinks

2018-05-17T06:29:47Z

Tsala: 3.5 link

3.4 docs: /34/en/{{FULLPAGENAMEE}}
3.5 docs: /35/en/{{FULLPAGENAMEE}}
3.3 docs: /33/en/{{FULLPAGENAMEE}}
3.1 docs: /31/en/{{FULLPAGENAMEE}}

Data Protection Officer role

2018-05-01T06:13:12Z

Tsala: /* Role set-up */ click to select the DPO

A Data Protection Officer can respond to data requests and manage the data registry.

Note: This role requires the [[Data privacy plugin]] to be installed on the site. The Data privacy plugin requires Moodle 3.4.2 or later and will be integrated in the Moodle 3.5 release in May 2018.

==Role set-up==

# Go to 'Define roles' in the Site administration.
# Click the button "Add a new role".
# Set the role archetype to Guest.
# Give the role a name such as 'Data Protection Officer', short name and description.
# For context types where this role may be assigned, tick system.
# Enter dataprivacy in the filter box, then allow the 3 dataprivacy capabilities 'Manage data registry', 'Manage data requests' and 'Make data requests for children'.
# Allow more capabilities as follows: moodle/site:configview, moodle/category:viewhiddencategories, moodle/course:viewhiddencourses, moodle/course:view, moodle/course:viewhiddenactivities.
# Click the button "Create this role".

Next

# Go to 'Privacy settings' in the Site administration.
# Click to select the Data Protection Officer in the Data Protection Officer role mapping setting.
# Save changes.

==Role assignment==

# Go to 'Assign system roles' in the Site administration.
# Choose the Data Protection Officer role to assign.
# Select the user in the Potential users list, and use the left-facing arrow button to add them to the Existing users list.

[[Category: Privacy]]
[[Category:Roles]]

[[es:Rol de Oficial de Protección de Datos]]
[[de:Datenschutzbeauftragter-Rolle]]

MoodleDocs:Overview

2018-04-25T05:30:14Z

Tsala: 3.5 en link

==English==

[https://docs.moodle.org/35/en/ 3.5 EN documentation]<br />
[https://docs.moodle.org/34/en/ 3.4 EN documentation]<br />
[https://docs.moodle.org/33/en/ 3.3 EN documentation]<br />
[https://docs.moodle.org/32/en/ 3.2 EN documentation]<br />
[https://docs.moodle.org/31/en/ 3.1 EN documentation]<br />

Also:<br />
[https://docs.moodle.org/dev/ Developer documentation]

==Català (Catalan)==

[https://docs.moodle.org/2x/ca/ 2.x CA documentation]<br />
[https://docs.moodle.org/19/ca/ 1.9 CA documentation]

==Deutsch (German)==

[https://docs.moodle.org/34/de/ 3.4 DE documentation]<br />
[https://docs.moodle.org/33/de/ 3.3 DE documentation]<br />
[https://docs.moodle.org/32/de/ 3.2 DE documentation]<br />
[https://docs.moodle.org/31/de/ 3.1 DE documentation]<br />

==Español (Spanish)==

[https://docs.moodle.org/all/es/ ES documentation]

==Euskara (Basque)==

[https://docs.moodle.org/all/eu/ EU documentation]

==Français (French)==

[https://docs.moodle.org/3x/fr/ 3.x FR documentation]<br />
[https://docs.moodle.org/2x/fr/ 2.x FR documentation]

==Hrvatski (Croatian)==

[https://docs.moodle.org/all/hr/ HR documentation]

==Íslenska (Icelandic)==

[https://docs.moodle.org/all/is/ IS documentation]

==日本語 (Japanese)==

[https://docs.moodle.org/2x/ja/ 2.x JA documentation]<br />
[https://docs.moodle.org/19/ja/ 1.9 JA documentation]

==Polski (Polish)==

[https://docs.moodle.org/2x/pl/ 2.x PL documentation]

==Português Brasileiro (Brazilan Portuguese)==

[https://docs.moodle.org/all/pt_br PT_BR documentation]

==Suomi (Finnish)==

[https://docs.moodle.org/3x/fi/ 3.x FI documentation]<br />
[https://docs.moodle.org/2x/fi/ 2.x FI documentation]

==中文 (Chinese)==

[https://docs.moodle.org/all/zh/ ZH documentation]

==See also==

* [[MoodleDocs:Read-only archives]]

Creating custom roles

2018-04-23T11:43:52Z

Tsala: /* Example custom roles */ DPO

{{Roles}}
==Creating a new role==

To create a custom role:
#Go to ''Administration > Site administration > Users > Permissions > Define roles''.
#Click the "Add a new role" button.
#If desired, select an existing role or upload a preset, otherwise click the continue button.
#Give the role a Short name e.g. 'Parent'.The short name is necessary for other plugins in Moodle that may need to refer to the role (e.g. when uploading users from a file or setting enrolments via an enrolment plugin).
#You must provide a full name for all custom roles. If you need to name the role for multiple languages you can use [[Multi language content|multi-lang syntax]] if you wish.
#Give the role a description (optional).
#Select an appropriate role archetype (see below for further information).
#Select the contexts where the role may be assigned e.g. 'User' for Parent role.
#Set permissions as required.
#Scroll to the top or bottom of the page and click the "Create this role" button.

{|
|-
| [[Image:addinganewrole26.png|thumb|Adding a new role and setting context types]]
| [[Image:permissions125.png|thumb|Choose "Allow" where required]]
| [[Image:permissions225.png|thumb|Extra options with "Show advanced" enabled]]
|-
|}

==Role archetypes==

A role archetype

* Is a hard-coded template for a role
* Is used during upgrades when adding defaults for new capabilities - no archetype = no new capabilities during upgrade
* Is used during when resetting a role to determine the defaults - no archetype = reset removes all capabilities

There is no need to set a role archetype for custom roles used for overrides or if the site admin wants to specify new capabilities manually after upgrading.

The archetypes (which relate directly to the built-in roles) are:
* Manager
* Course creator
* Teacher (editing)
* Teacher (non-editing)
* Student
* Guest
* Authenticated user
* Authenticated user on frontpage

==Creating a duplicate role==

To create a duplicate role:
#Go to ''Administration > Site administration > Users > Permissions > Define roles''.
#Click the "Add a new role" button.
#Select existing role as a template
#Give a name and set permissions for your new role; scroll down and click "Create this role".

==New role considerations==

A new role is not automatically listed in course descriptions even if was created by copying a role that is listed, such as Teacher. If you want the new role to appear in the course listing, you must set it explicitly via ''Administration > Site administration > Appearance > Courses>Course Contacts"

==Testing a new role==
''Administration > Switch role to''
Use the "Switch role to" link to see what another role will see in that context.

Since switching roles confines you to those roles you can assign in a course context, this method is only useful for testing course-scoped capabilities (i.e. it will not be useful for testing permissions that apply outside the course context, like moodle/user:edit).

''Tip:'' You can always create test user and assign the new role to them. Then logout as admin and login as the test user. This is really the best way to test a new role.

==Example custom roles==

*[[Parent role|Parent]] - for providing parents/mentors/tutors with permission to view certain information about their children/mentees/tutees
*[[Demo teacher role|Demo teacher]] - for providing a demonstration teacher account with a password which can't be changed
*[[Forum moderator role|Forum moderator]] - for providing a user with permission in a particular forum to edit or delete forum posts, split discussions and move discussions to other forums
*[[Forum poster role]] - a highly restricted custom role which may be given to a visitor account to enable them to post in forums in a guest access course.
*[[Calendar editor role|Calendar editor]] - for enabling a user to add site or course events to the calendar
*[[Blogger role|Blogger]] - for limiting blogging to specific users only
*[[Quiz user with unlimited time role|Quiz user with unlimited time]] - for allowing a user unlimited time to attempt a quiz which has a time limit set
*[[Question creator role|Question creator]] - for enabling students to create questions for use in quizzes
*[[Question sharer]] - for allowing teachers to share questions between courses
*[[Course requester role]] - for restricting users who can make course requests
*[[Feedback template creator]] - for allowing teachers to save as "Public" a Feedback template.
*[[Grading forms publisher]] - for allowing teachers to share Advanced grading forms with others
*[[Grading forms manager]] - for allowing teachers to share Advanced grading forms with others and to delete templates others have created.
*[[Grade viewer]] - for allowing users to view but not edit grades.
*[[Gallery owner role]] - may be used to provide editing capabilities (add and edit gallery images) to users on individual Lightbox Galleries.
*[[Course tagger]] - for allowing users other than managers and editing teachers to tag courses.
*[[Competency reviewer]] - for allowing teachers to review competencies.
*[[Learning plan supervisor]] for allowing teachers to create learning plans for their own students.
*[[Learning plan viewer]] for allowing teachers to view the learning plans of their own students.
*[[Roles_FAQ#How_can_I_allow_a_.22test.22_Student_user_to_see_courses_that_are_hidden.3F|Student tester ]] - a clone of the default [[Student role]] with the ability to see hidden courses set to Allow.
*[[Data Protection Officer role|Data Protection Officer]] - A Data Protection Officer can respond to data requests and manage the data registry

==Uploading users to a system role==

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 the CSV file

==See also==
* [https://github.com/3-bits/moodle-role_sepe SEPE] Spanish government supervisor who can access all Moodle courses without being able to change anything.

Using Moodle forum discussions:
* [http://moodle.org/mod/forum/discuss.php?d=66782 What happens if a user has multiple roles in a course?]
* [http://moodle.org/mod/forum/discuss.php?d=90140 logged in: what role am I?]
* For more information, Ask questions and get answers on the [http://moodle.org/mod/forum/view.php?id=6826 "Roles and Permissions"] forum.

[[Category:Site administration]]

[[de:Neue Rollen anlegen]]
[[es:Crear roles personalizados]]
[[fr:Création_de_rôles_personnalisés]]
[[ja:カスタムロールの作成]]

DPO

2018-04-23T11:42:57Z

Tsala: redirect

#REDIRECT [[Data Protection Officer role]]

Data privacy

2018-04-23T06:50:16Z

Tsala: Example categories

{{Infobox plugin
|type = Admin tools
|entry = https://moodle.org/plugins/tool_dataprivacy
|tracker = https://tracker.moodle.org/issues/?jql=component%20%3D%20Privacy
|discussion =
|maintainer = Moodle HQ
}}

The Data privacy plugin provides the workflow for users to submit subject access requests and for the site administrator or Data Protection Officer (DPO) to process these requests.

The Data Privacy plugin forms part of Moodle’s privacy feature set and will assist sites to become GDPR compliant. It requires Moodle 3.4.2 or later and will be integrated in the Moodle 3.5 release in May 2018.

==Data Protection Officer role==

After installing the data privacy plugin, the first thing to do is to create a [[Data Protection Officer role]] and assign it.

(If there is nobody on the site with the role of Data Protection Officer i.e. nobody with the capability to manage data requests, then a site admin can respond to data requests and manage the data registry.)

==Data requests==
[[File:requesting data.png|thumb|Requesting data]]
Any user can send a message to the Data Protection Officer via the 'Contact Data Protection Officer' link on their profile page.

In addition, they can request a copy of all of their personal data or request that their personal data should be deleted as follows:

# Go to your profile page (via the user menu).
# Click the link 'Data requests' then click the 'New request' button.
# Select 'Export all of my personal data' or 'Delete all of my personal data' as appropriate.
# Save changes.
[[File:Request approved.png|thumb|Request approved]]
The DPO will then receive a data request notification.

If the user has requested a copy of all of their personal data, once the request is approved, they will receive a notification to inform them that their personal data may be downloaded from their Data requests page.

If the user has requested that their personal data should be deleted, once the request is approved, they will receive an email to inform them and they will no longer be able to log in to the site.

==Responding to data requests==
[[File:viewing a data request.png|thumb|Viewing a data request]]
The DPO can respond to data requests as follows:

# Go to 'Data requests' in the Site administration (or follow the link in the data request notification).
# In the Actions dropdown, select View, Approve, or Deny as appropriate.

==Data registry==
[[File:data registry.png|thumb|Data registry]]
The DPO can set purposes (why the organisation is processing data) with retention periods and categories for data stored in Moodle in the data registry.

A default purpose and retention period may be set for course categories, courses, activity modules and blocks.

===Example categories===

* Administrative: Civil status, identity, identification data, images …
* Personal life (lifestyle, family situation, etc.)
* Economic and financial information (income, financial situation, tax situation, etc.)
* Connection data (IP address, logs, etc.)
* Educational Data (Assessed Coursework, exam scripts etc)
* Records of Education Attainment (Results of exams, assessments, qualifications awarded etc)
* Location data (travel, GPS data, GSM, etc.)

===Data registry set-up===

To add purposes and categories:

# Go to 'Data registry' in the Site administration.
# In the Edit menu select Categories.
# On the 'Edit categories' page, click the + button to add a new category.
# Enter a category name and description then click the Save button.
# Go to 'Data registry' again and in the Edit menu select Purposes.
# On the 'Edit purposes' page, click the + button to add a new purpose.
# Enter a purpose name, description and retention period then click the Save button.

To set default categories and purposes:

# In 'Data registry' in the Site administration click the 'Set defaults' button.
# Select a default category and purpose for the site, and for users, course categories, courses, activity modules and blocks as required.
# Save changes.

==Capabilities==

* [[Capabilities/tool/dataprivacy:managedataregistry|Manage data registry]]
* [[Capabilities/tool/dataprivacy:managedatarequests|Manage data requests]]
* [[Capabilities/tool/dataprivacy:makedatarequestsforchildren|Make data requests for children]]

==See also==

* [[GDPR for administrators (Moodle 3.4.2+)]]
* [https://gdprdemo.moodle.net/ Moodle GDPR sandbox demo site] for exploring all the [[Policies plugin]] and Data privacy plugin functionality

[[Category: Privacy]]

[[es:Plugin de privacidad de datos]]
[[de:Schutz persönlicher Daten]]

Privacy officer

2018-04-19T11:58:35Z

Tsala: redirect edit

#REDIRECT [[Data Protection Officer role]]

Privacy officer role

2018-04-19T11:57:49Z

Tsala: redirect edit

#REDIRECT [[Data Protection Officer role]]