Note: You are currently viewing documentation for Moodle 3.2. Up-to-date documentation for the latest stable version of Moodle is probably available here: Messaging settings.
Messaging settings for all users
- Users can decide how they want to be notified of new messages and event notifications by editing their messaging preferences page, which they can access either from the Preferences link in the user menu or from the gear icon in the messaging/notifications menus. See Messaging and Notifications for more information.
- Which options they see there depend on what has been enabled by the administrator. For example, the mobile option is only available if the site is enabled for the mobile app.
Enabling / disabling messaging site wide
The personal messaging system in Moodle is enabled by default. It may be disabled by a site administrator from 'Advanced features' in Site administration.
Messaging system default settings are set in 'Message outputs' in Site administration.
There are four default types of output methods for messaging: web, Jabber, email and mobile.
By default web and email are both enabled, though email will only work of course if the site has been properly configured to deliver email. Jabber and Mobile notifications are off by default and need to be configured first.
Jabber must be configured before use.
(Could someone with working settings fill this out with example?)
- Host - The server to connect to to send jabber message notifications - full hostname (e.g. jabber.org)
- Server - XMPP host ID (can be left empty if the same as Jabber host)
- Username - The user name to use when connecting to the Jabber server
- Password - The password to use when connecting to the Jabber server
- Port - defaults to 5222
The administrator can configure the site to push messages to mobile devices. Moodle pushes messages to a messaging server, which then pushes it to Apple or Google depending on the platform the target device is using (iOS or Android).
The default messaging server is a free Airnotifier server maintained by moodle.com which registered sites may use for testing (be aware that all your messages will go via this server). To connect to this, click 'Request access key' and then add it to the Airnotifier access key field. Alternatively, you may install your own private Airnotifier server and use that instead. See https://github.com/dongsheng/airnotifier for details.
Users will need to connect at least once with the latest version of the mobile app to register their phones with the site.
Default message outputs
You can specify the default outputs for each type of message that Moodle can send in 'Default message outputs' in Site administration.
You can also set to what degree each type of message is enabled, and whether users are able to change these default settings in their profiles:
- Disallowed - This particular type of message is not allowed at all and users will not see any settings related to them. Message of the chosen type will never be delivered.
- Permitted - Users are permitted or allowed to change the settings. When the user account is created, the new user will inherit the settings the administrator sets here, but will be allowed to change them afterward in their Messaging settings. Messages will be delivered as the user sets them on their own Messaging settings page.
- Locked - Users are not permitted or allowed to change these settings. When the user account is created, the new user will inherit the settings the administrator sets here and will never be allowed to change them. Messages will be delivered for all users as you set them on this page.
You can set whether each of these will be sent when the user is online through the messaging system interface available to users in their profiles, and/or whether each output is sent via email.
Ordering of messaging settings
Because users might have many different messaging options, they are ordered into different components - for example, activities, system, enrolments etc.
List of message types
Except for Personal messages between users, which refers to the interaction messaging tool on a user profile, the other messages are generated by events in Moodle. These are set in the system by the Administrator in Site administration > Plugins > Message outputs > Default message outputs.
|Assignment notifications||Student has submitted an assignment||Teacher|
|Warning when your quiz attempt becomes overdue||See Quiz settings||Student|
|Available update notifications||Notice of new releases of Moodle code||Site administrators|
|Backup notifications||Automated backup schedule run completed||Site administrators|
|Badge creator notifications||Notify creator of a badge when it is awarded to someone||Any badge creator (typically Teacher or Manager role)|
|Badge recipient notifications||Notify recipient of a badge when it is awarded to them||Any badge recipient (typically Student role)|
|Comment posted on a learning plan||?||?|
|Comment posted on a competency||?||?|
|Confirmation of your own quiz submissions||Notice your quiz was successfully submitted||Student|
|Course creation request approval notification||Notice a requested course has been approved||Defined in Site admin > Courses > Course request > Course request notification|
|Course creation request notification||Notice a course has been requested - See Course request||Defined in Site admin > Courses > Course request > Course request notification|
|Course creation request rejection notification||Notice a requested course has been rejected||Defined in Site admin > Courses > Course request > Course request notification|
|Subscribed forum digests||Sets default for this for user profiles||Authenticated users|
|Important errors with the site||Important errors - See also Debugging||Site administrators|
|Manual enrolment expiry notifications||Notice if Manual enrolment about to expire||Manual enrolees|
|Self enrolment expiry notifications||Notify users when their enrolment expires||Enroller only, or Enroller & Enrolled user|
|Lesson essay graded notification||Notify students a teacher has graded a Lesson essay question||Student|
|Personal messages between users||Using the Messaging interface tool||Authenticated Users|
|Message to confirm that an inbound message came from you||See Incoming mail configuration||Authenticated Users|
|Feedback reminder||Feedback non-respondent reminder message||Student feedback activity non-responders|
|Warning when an inbound message could not be processed||See Incoming mail configuration||Authenticated Users|
|Confirmation that a message was successfully processed||See Incoming mail configuration||Authenticated Users|
|Notices about minor problems||Site administrators|
|Notification of rule subscriptions||Notifications from Event monitoring rules||Event rule subscribers|
|Subscribed forum posts||Default for forum subscription handling||Anyone subscribed to a forum|
|Feedback notifications||Notices from setting Enable notification of submissions||Teacher, Feedback administrator|
|Notification of quiz submissions||Message that student has submitted a quiz||Teacher|
Roles and Messaging capabilities
The following capabilities can be applied as permissions to make custom changes to roles affecting messaging.
- course:bulkmessaging - Send a message to many people
- site:readallmessages - Read all messages on site
- site:sendmessage - Send messages to any user
- user:editownmessageprofile - Edit own user messaging profile
- user:editmessageprofile - Edit user messaging profile
All email messages and notifications go to the email address set in a user's profile. The administrator can optionally allow users to choose to have notifications sent to a different email address. This is off by default and can be enabled in Site administration > Advanced features > Notification email override.
Users can then enter their alternative email address under Preferences/User account/Notification preferences: Click on the gear icon next to "Email" in the table header and enter the alternative email.
Note: The 'messagingallowemailoverride' setting does not affect failed log in notifications as they do not go through the messaging system, and will therefore still go to the original email specified.