config_site.rst 63.8 KB
 Kristina Hoeppner committed Apr 06, 2012 1 2 .. include:: /shortcuts.rstext  Kristina Hoeppner committed Jan 06, 2012 3 .. index::  Kristina Hoeppner committed Oct 20, 2012 4  pair: Administration; Configure site  Kristina Hoeppner committed Oct 21, 2012 5  single: Site administrator; Configure site  Kristina Hoeppner committed Jan 06, 2012 6 7 8 9 10 11  .. _configure_site: Configure site ----------------  Kristina Hoeppner committed Oct 16, 2012 12 *Administration → Configure site*  Kristina Hoeppner committed Apr 06, 2012 13   Kristina Hoeppner committed Oct 20, 2012 14 .. note::  Kristina Hoeppner committed Oct 21, 2012 15  *Configure site* is only accessible by site administrators.  Kristina Hoeppner committed Oct 20, 2012 16   Kristina Hoeppner committed Jan 06, 2012 17 18 19 20 21 In *Configure site* you can: * set general parameters for your Mahara site * edit site pages * determine the display of certain menu items  Kristina Hoeppner committed Oct 16, 2012 22 * allow networking with Moodle or another Mahara  Kristina Hoeppner committed Oct 20, 2012 23 24 * create and share site pages and collections * upload site files  Kristina Hoeppner committed Jan 06, 2012 25   Kristina Hoeppner committed Apr 21, 2012 26 .. index::  Kristina Hoeppner committed Oct 21, 2012 27 28  pair: Administration; Site options single: Site administrator; Site options  Kristina Hoeppner committed Apr 21, 2012 29   Kristina Hoeppner committed Jan 06, 2012 30 31 32 33 34 .. _site_options: Site options ~~~~~~~~~~~~~~~~~~  Kristina Hoeppner committed Oct 16, 2012 35 *Administration → Configure site → Site options*  Kristina Hoeppner committed Apr 06, 2012 36   Kristina Hoeppner committed Oct 20, 2012 37 In *Site options* you can set global options that will apply by default throughout the entire site.  Kristina Hoeppner committed Jan 06, 2012 38 39  .. note::  Kristina Hoeppner committed Apr 06, 2012 40  One or more fields may be disabled if overridden by a setting in your config.php file.  Kristina Hoeppner committed Jan 06, 2012 41   Kristina Hoeppner committed Jan 08, 2012 42 43 When you are done editing one or more settings, click the *Update site options* button at the bottom of the page.  Kristina Hoeppner committed Apr 06, 2012 44 .. index::  Kristina Hoeppner committed Oct 21, 2012 45 46  pair: Administration; Site settings single: Site administrator; Site settings  Kristina Hoeppner committed Jun 12, 2012 47  single: Drop-down site navigation  Kristina Hoeppner committed Apr 06, 2012 48   Kristina Hoeppner committed Jan 06, 2012 49 50 51 52 53 .. _site_settings: Site settings ^^^^^^^^^^^^^^^^^^^  Kristina Hoeppner committed Oct 20, 2012 54 .. figure:: /images/administration/site_settings.*  Kristina Hoeppner committed Jan 06, 2012 55 56 57 58  :alt: Site settings Site settings  Kristina Hoeppner committed Oct 20, 2012 59 #. **Site name**: Choose a name for your Mahara instance. It appears in certain places around the site, e.g. in the title bar of the browser and in emails sent from the site. Therefore, it should not be too long.  Kristina Hoeppner committed Jan 06, 2012 60 #. **Language**: Set the default language for your site. If you have multiple language packs installed, you see a drop-down menu. Otherwise, the standard language, English, is displayed.  Kristina Hoeppner committed Jan 17, 2016 61 62 63 64  .. note:: You can install more language packs _. More information about the language packs _ is on the wiki.  Kristina Hoeppner committed Jan 06, 2012 65 #. **Country**: The country selected is the default for country selections throughout your Mahara installation, e.g. in :ref:contact information .  Kristina Hoeppner committed Oct 20, 2012 66 #. **Theme**: Mahara comes with a number of themes that you can use. Choose one from the drop-down menu to make it the default theme for your site. If you have :ref:institutions  set up, they can :ref:choose their own theme . You can search for community-contributed themes _ on the Mahara wiki.  Kristina Hoeppner committed Jan 17, 2016 67 68 69 #. **Drop-down navigation**: If set to "Yes", the main Mahara navigation uses a drop-down menu for its subnavigation. #. **Show homepage / dashboard information**: If set to "Yes", information about Mahara and how it is used is displayed on the homepage for logged-out and on the *Dashboard* for registered users. Registered users can disable this for their own dashboard. See also :ref:Quick links . #. **Send weekly updates?**: If set to "Yes", your site sends weekly updates to mahara.org _ with some statistics about your site. See also :ref:Register your Mahara site .  Kristina Hoeppner committed Jan 06, 2012 70   Kristina Hoeppner committed Apr 21, 2012 71 .. index:: Gravatar  Kristina Hoeppner committed Oct 21, 2012 72 73  pair: Administration; User settings single: Site administrator; User settings  Kristina Hoeppner committed Jun 12, 2012 74 75  single: Logged-in profile page access single: Staff report access  Kristina Hoeppner committed Nov 25, 2012 76 77 78  single: Staff statistics access setting single: Device detection single: Responsive design  Kristina Hoeppner committed Jun 02, 2013 79 80  single: Masquerading: Require reason single: Masquerading: Notify user  Kristina Hoeppner committed Apr 06, 2012 81   Kristina Hoeppner committed Jan 06, 2012 82 .. _user_settings:  Kristina Hoeppner committed Feb 14, 2016 83 .. _staff_report_access:  Kristina Hoeppner committed Aug 01, 2012 84 .. _staff_statistics_access:  Kristina Hoeppner committed Mar 24, 2013 85 86 .. _masquerading_reason_setting: .. _masquerading_notification_setting:  Kristina Hoeppner committed May 11, 2014 87 .. _profile_completion_siteadmin:  Kristina Hoeppner committed Oct 27, 2014 88 .. _export_to_queue:  Kristina Hoeppner committed Jul 15, 2015 89 .. _anonymous_feedback:  Kristina Hoeppner committed Jan 06, 2012 90 91 92 93  User settings ^^^^^^^^^^^^^^^^^^  Kristina Hoeppner committed Oct 20, 2012 94 .. figure:: /images/administration/user_settings.*  Kristina Hoeppner committed Jan 06, 2012 95 96 97 98  :alt: User settings User settings  Kristina Hoeppner committed Apr 06, 2012 99 #. **Users can choose page themes**: If this setting is enabled, users can select a theme for their portfolio page. The page is displayed with this theme to other users. Thus, the institution or site theme can be overwritten.  Kristina Hoeppner committed Apr 27, 2015 100 #. **Display remote avatars**: If allowed, users' default profile pictures will be their Gravatar _ pictures (:ref:remote avatar ). Users will need an account with Gravatar for this to work.  Kristina Hoeppner committed Apr 07, 2013 101 102  .. note::  Kristina Hoeppner committed Mar 28, 2016 103  If you use your own avatar server to provide profile pictures for your users, you can use that instead of Gravatar for the default profile pictures. In order to do so, you need to add the :ref:remote avatar base URL  to your config.php.  Kristina Hoeppner committed Apr 07, 2013 104   Kristina Hoeppner committed Apr 27, 2015 105 #. **Users can hide real names**: If allowed, users who have set a :ref:display name  may choose to be searchable only by their display name and will not be found in searches by their real name. In the administration section of the site, users are always searchable by their real names. An administrator (site and institution) always sees the display name, first and last name and username.  Kristina Hoeppner committed Apr 17, 2017 106 #. **Never display usernames**: :index:If set  to "Yes", ordinary users cannot search for others using their username in "Search users" on the :ref:Dashboard  or via :ref:Find people . They will also not be able to see the username of any other user. These restrictions do not apply to staff and administrators. Additionally, Clean URLs (if activated) for profile pages will be generated using display names (if provided) or real names, rather than usernames.  Kristina Hoeppner committed Jan 17, 2016 107 #. **Show users in public search**: If allowed, :index:usernames can appear in public search results . In addition, this feature needs to have the value  \$cfg->publicsearchallowed = true; set in your config.php file and requires a search plugin that allows public search, e.g. Elasticsearch.  Kristina Hoeppner committed May 11, 2014 108 109 110 111  .. note:: When you change this setting, you need to re-index the search index for the change to take effect.  Kristina Hoeppner committed Jul 15, 2015 112 #. **Anonymous comments**: :index:If allowed , logged-out users / users without a login can leave comments on public pages or pages they can access via a secret URL.  Kristina Hoeppner committed Jan 17, 2016 113 #. **Profile access for all registered users**: If this option is set to "No", profile pages are initially viewable by all registered users, but the owner is allowed to restrict access to their institution only if they wish. Enable this option if you want to make sure all users can see each others' profile pages. Profiles of institution members will always be visible to other members of the same institution.  Kristina Hoeppner committed Oct 22, 2017 114 115 116 117 118 119 120 #. **Access reports for staff**: :index:If  set to "Yes", site and institution staff will have :ref:access to user reports . The following reports are available to them: * Masquerading sessions (if logging of these is turned on) * Portfolio access * User details #. **All reports for institution staff**: If set to "Yes", institution staff will have access to all reports in their institutions. This is normally restricted to administrators and site staff.  Kristina Hoeppner committed Jan 17, 2016 121 122 123 #. **Users can disable device detection**: If allowed, users can disable mobile device detection in their :ref:account settings . This allows them to be more flexible in what they can view and do on a mobile device such as a smartphone or tablet. #. **Require reason for masquerading**: If set to "Yes", administrators will be required to enter a reason for :ref:masquerading as other users . This will be logged, and if the setting "Notify users of masquerading" is enabled, included in the notification to the user about the masquerading. This setting needs :ref:logging  to be turned on. #. **Notify users of masquerading**: If set to "Yes", users will be notified :ref:when an administrator masqueraded as them . The notification will include who, when and - if enabled under "Require reason for masquerading" - why. This setting needs :ref:logging  to be turned on.  Kristina Hoeppner committed Oct 22, 2017 124 #. **Show profile completion**: If set to "Yes", :index:a progress bar with tips  about what to complete in the user profile will be displayed in the sidebar to users. They can disable it in their :ref:account settings .  Kristina Hoeppner committed May 11, 2014 125 126  .. seealso::  Kristina Hoeppner committed Oct 22, 2017 127  Administrators can configure the items that count towards profile completion in *Administration → Institutions →* :ref:Profile completion .  Kristina Hoeppner committed Apr 06, 2012 128   Kristina Hoeppner committed Apr 27, 2015 129 #. **Export to queue**: :index:If allowed , the export queue will handle the exporting of user portfolios via Leap2A for better server load management.  Kristina Hoeppner committed Oct 12, 2014 130 131 132 133  .. note:: **This feature is still experimental.** Turning this feature on will export individual portfolios in *Portfolio → Export* via the export queue. That means that the export is made when there are enough system resources available. The user exporting a portfolio will receive an email when the export is ready for download.  Kristina Hoeppner committed Aug 19, 2015 134 #. **Multiple journals**: If allowed, :index:all users  will have multiple journals per default. They can still change that setting in their personal account settings.  Kristina Hoeppner committed Apr 27, 2015 135   Kristina Hoeppner committed Apr 21, 2012 136 .. index::  Kristina Hoeppner committed Oct 21, 2012 137 138  pair: Administration; Search settings single: Site administrator; Search settings  Kristina Hoeppner committed Apr 21, 2012 139   Kristina Hoeppner committed Jan 06, 2012 140 141 142 143 144 145 146 .. _search_settings: Search settings ^^^^^^^^^^^^^^^^^^ Mahara comes with a search plugin that allows you to search for users and pages. If you install another search plugin, you will be able to select which one to use for your site.  Kristina Hoeppner committed Oct 20, 2012 147 .. figure:: /images/administration/search_settings.*  Kristina Hoeppner committed Jan 06, 2012 148 149 150 151  :alt: Search settings Search settings  Kristina Hoeppner committed Oct 20, 2012 152 153 .. seealso:: You can configure the internal search plugin in the :ref:administration of the search plugin .  Kristina Hoeppner committed Jan 06, 2012 154   Kristina Hoeppner committed Oct 22, 2017 155 156 157 158 159 Elasicsearch is another search plugin that is supported by Mahara out of the box. The search server will need to be installed separately though. Elasticsearch is useful for fulltext search and is required for |new in Mahara 17.10| advanced reporting. .. note:: You need to choose the Elasticsearch plugin if you turn on :ref:"Event log reporting" .  Kristina Hoeppner committed Apr 21, 2012 160 .. index:: Public group, Group category  Kristina Hoeppner committed Oct 21, 2012 161 162  pair: Administration; Group settings single: Site administrator; Group settings  Kristina Hoeppner committed Apr 21, 2012 163   Kristina Hoeppner committed Jan 06, 2012 164 165 166 167 168 169 170 .. _group_settings: Group settings ^^^^^^^^^^^^^^^^^^^^ Mahara cannot only be used for individual work but also to work collaboratively in groups. Some settings are available in that area.  Kristina Hoeppner committed Oct 20, 2012 171 .. figure:: /images/administration/group_settings.*  Kristina Hoeppner committed Jan 06, 2012 172 173 174 175  :alt: Group settings Group settings  Kristina Hoeppner committed Apr 06, 2012 176 #. **Create groups**: You decide whether administrators, administrators and staff or everyone can create groups. The default setting is the most permissive "everyone" because Mahara is user-centered and gives the individual users a great deal of control over what they want to do. If you choose to limit the group creation to administrators (and staff), these need to be contacted to set up groups. There is no internal group request system.  Kristina Hoeppner committed Oct 20, 2012 177 #. **Create public groups**: Choose whether everyone or only administrators can create :ref:public groups . These are groups for which you do not need to be a member of the group or even have a login for Mahara to view the group homepage, discussion forums (and member listing if the group administrator allowed that).  Kristina Hoeppner committed Jan 17, 2016 178 #. **Allow group categories**: If allowed, site administrators can create categories for users to assign to their groups. These categories can be used to filter groups in :ref:My groups  and :ref:Find groups .  Kristina Hoeppner committed Jan 06, 2012 179   Kristina Hoeppner committed Oct 16, 2012 180 .. seealso::  Kristina Hoeppner committed Oct 20, 2012 181  Group categories are managed by site administrators in the :ref:groups area  of the administration.  Kristina Hoeppner committed Oct 16, 2012 182   Kristina Hoeppner committed Apr 21, 2012 183 .. index:: Multiple institutions; Institution expiry; Auto-suspend expired institutions  Kristina Hoeppner committed Oct 21, 2012 184 185  pair: Administration; Institution settings single: Site administrator; Institution settings  Kristina Hoeppner committed Apr 21, 2012 186   Kristina Hoeppner committed Jan 07, 2012 187 188 .. _institution_settings:  Kristina Hoeppner committed Jan 06, 2012 189 Institution settings  Kristina Hoeppner committed Jan 07, 2012 190 ^^^^^^^^^^^^^^^^^^^^^^^^  Kristina Hoeppner committed Jan 06, 2012 191 192 193  You can use Mahara with multiple institutions and separate them for administrative purposes, e.g. user management and permissions, and to give them a different theme.  Kristina Hoeppner committed Oct 20, 2012 194 .. figure:: /images/administration/institution_settings.*  Kristina Hoeppner committed Jan 06, 2012 195 196 197 198  :alt: Institution settings Institution settings  Kristina Hoeppner committed Jan 17, 2016 199 200 201 202 203 204 #. **Confirm registration**: :index:If set to "Yes", administrators  cannot make the *Confirm registration* setting optional when :ref:configuring an institution . This prevents institution administrators from disabling this setting when it is required site-wide to not allow user accounts to be created without administrator approval. #. **Users allowed multiple institutions**: If allowed, users can be members of several institutions at the same time. Thus, a user who belongs to two or more institutions only needs one account. .. note:: While this is a convenient setting for people who need to be institution administrators in multiple institutions and cannot receive site administrator permissions, it is recommended that users can only belong to one institution.  Kristina Hoeppner committed Oct 16, 2012 205 #. **Warning time for institution expiry**: If set, a notification will be sent to site and institution administrators this amount of time before an institution is due to expire and be suspended. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, institutions will not expire by default.  Kristina Hoeppner committed Jan 17, 2016 206 #. **Auto-suspend expired institutions**: If set to "Yes", this option will allow Mahara to automatically suspend an institution that has expired automatically. This means that users of that institution will not be able to log in until the institution has been unsuspended.  Kristina Hoeppner committed Jan 07, 2012 207   Kristina Hoeppner committed Apr 21, 2012 208 .. index:: Default account lifetime, Default account inactivity time, Session lifetime, Warning time for inactivity / expiry  Kristina Hoeppner committed Oct 21, 2012 209 210  pair: Administration; Account settings single: Site administrator; Account settings  Kristina Hoeppner committed Oct 20, 2013 211 212  single: Account settings; Default registration expiry lifetime single: Account settings; Override user account lifetime  Kristina Hoeppner committed Apr 21, 2012 213   Kristina Hoeppner committed Jan 07, 2012 214 215 216 217 218 .. _config_site_account_settings: Account settings ^^^^^^^^^^^^^^^^^^^^^^  Kristina Hoeppner committed Oct 20, 2012 219 .. figure:: /images/administration/account_settings.*  Kristina Hoeppner committed Jan 07, 2012 220 221 222 223 224  :alt: Account settings Account settings #. **Session lifetime**: For security reasons, after a specified period of inactivity, a user will be logged off the site automatically. This field specifies this time in minutes. The default value is 1440 minutes (24 hours).  Kristina Hoeppner committed Jun 02, 2013 225 #. **Default registration expiry lifetime**: As site administrator you can decide when :ref:pending registrations  that require approval expire. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, pending registrations will not expire by default. The default value is 2 weeks.  Kristina Hoeppner committed Jan 07, 2012 226 #. **Default account lifetime**: If set, user accounts will expire after this amount of time from when they were created. When a user account is expired, the user cannot log in. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, accounts will not expire by default.  Kristina Hoeppner committed Dec 24, 2013 227 #. **Override user account lifetime**: Choose for which accounts a :index:change in the default account lifetime  shall take effect:  Kristina Hoeppner committed Oct 20, 2013 228 229 230 231 232 233 234 235  * Only for newly created users * For new users and users without an account lifetime already set (excluding site administrators) * For all user accounts (excluding site administrators) .. note:: Site administrators are always excluded from a change in the account lifetime as they should always have access to the system.  Kristina Hoeppner committed Jan 07, 2012 236 237 238 #. **Default account inactivity time**: If set, users who do not log in for this amount of time will be considered "inactive" and will not be able to log in anymore. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, users are not set to "inactive" by default. #. **Warning time for inactivity / expiry**: If set, a warning message will be sent to users this amount of time before their accounts are due to expire or become inactive. This time may be specified in days, weeks, months, years or "No end date". If the latter is chosen, users do not receive a warning before their account expires or they are flagged as having an inactive account.  Kristina Hoeppner committed Apr 21, 2012 239 .. index:: Virus checking, ClamAV, Anti-spam, External resources in HTML  Kristina Hoeppner committed Oct 21, 2012 240 241  pair: Administration; Security settings single: Site administrator; Security settings  Kristina Hoeppner committed May 11, 2014 242  single: Spam protection; reCAPTCHA  Kristina Hoeppner committed Apr 21, 2012 243   Kristina Hoeppner committed Jan 07, 2012 244 245 246 247 248 .. _security_settings: Security settings ^^^^^^^^^^^^^^^^^^^^^  Kristina Hoeppner committed Oct 20, 2012 249 .. figure:: /images/administration/security_settings.*  Kristina Hoeppner committed Jan 07, 2012 250 251 252 253  :alt: Security settings Security settings  Kristina Hoeppner committed Mar 28, 2015 254 #. **Virus checking**: If you want all files that are uploaded by users to be run through the ClamAV virus scanner, you should turn the virus checking option on. You have to have ClamAV _ installed on your server.  Kristina Hoeppner committed Mar 28, 2016 255 #. **Path to ClamAV**: For security reasons, the :index:path to ClamAV  on your server needs to be provided in the :ref:config file . You see the path here if you provided that config value.  Kristina Hoeppner committed Oct 20, 2012 256 #. **Anti-spam**: There are three levels of anti-spam protection available for publicly visible forms such as the contact and registration forms. A form submission is never silently rejected. Rather, an error message is displayed asking the user to try again if the submission is classified as spam. The three choices are:  Kristina Hoeppner committed Jan 07, 2012 257 258 259  * **None**: No anti-spam checks are performed on form submissions. * **Simple**: Some basic checks are performed. Form submissions with email addresses that are not well-formed or that have an excessive number of URLs are rejected.  Kristina Hoeppner committed Mar 04, 2012 260  * **Advanced**: Performs additional checks to determine whether email addresses are real or contain URLs that are blacklisted. This requires an Internet connection.  Kristina Hoeppner committed Jan 07, 2012 261   Kristina Hoeppner committed Jan 17, 2016 262 263 264 #. **Spamhaus URL blacklist**: If set to "Yes", URLs will be checked against the Spamhaus DNSBL. The Spamhaus Project _ provides a URL blacklist that is free for non-commercial, low-traffic use. A professional use datafeed service is also available but not supported in Mahara. Please read the Spamhaus DNSBL usage terms _ before enabling this option. #. **SURBL URL blacklist**: If set to "Yes", URLs will be checked against the SURBL DNSBL. SURBL _ provides a URL blacklist that is free for organizations with fewer than 1000 users. A professional use datafeed service is also available, but not supported in Mahara. Please read the SURBL usage terms _ before enabling this option. #. **Disable external resources in user HTML**: Turning this option on will prevent users from embedding external resources such as images from remote sites into their forum posts and other HTML content. YouTube videos and other media can also not be embedded. It is however a good thing to do from a security standpoint since it does neutralise a few clever phishing attacks. See the HTML Purifier documentation _ for more details.  Kristina Hoeppner committed Mar 28, 2016 265 #. **reCAPTCHA on user registration form**: If set to "Yes", :index:people who register themselves on the site  are required to fill in a reCAPTCHA _ test. This is a spam protection instrument.  Kristina Hoeppner committed Mar 28, 2015 266 267 #. **reCAPTCHA site key**: Enter the site key for your site's reCAPTCHA account. #. **reCAPTCHA secret key**: Enter the secret key for your site's reCAPTCHA account.  Kristina Hoeppner committed Jan 07, 2012 268   Kristina Hoeppner committed Apr 21, 2012 269 .. index::  Kristina Hoeppner committed Oct 21, 2012 270 271  pair: Administration; Proxy settings single: Site administrator; Proxy settings  Kristina Hoeppner committed Apr 21, 2012 272   Kristina Hoeppner committed Jan 07, 2012 273 274 275 276 277 .. _proxy_settings: Proxy settings ^^^^^^^^^^^^^^^^^^  Kristina Hoeppner committed Oct 20, 2012 278 .. figure:: /images/administration/proxy_settings.*  Kristina Hoeppner committed Jan 07, 2012 279 280 281 282  :alt: Proxy settings Proxy settings  Kristina Hoeppner committed Jan 17, 2016 283 #. **Proxy address**: If your site uses a proxy server to access the Internet, specify the proxy in hostname:portnumber notation.  Kristina Hoeppner committed Jan 07, 2012 284 285 286 #. **Proxy authentication model**: Select your proxy's authentication model (none or basic [NCSA]), if appropriate. #. **Proxy credentials**: Enter the credentials required for your proxy to authenticate your web server in username:password format.  Kristina Hoeppner committed Apr 21, 2012 287 .. index:: System mail address  Kristina Hoeppner committed Oct 21, 2012 288 289  pair: Administration; Email settings single: Site administrator; Email settings  Kristina Hoeppner committed Jun 12, 2012 290  single: Default notification method  Kristina Hoeppner committed Apr 06, 2012 291   Kristina Hoeppner committed Jan 07, 2012 292 293 294 295 296 .. _email_settings: Email settings ^^^^^^^^^^^^^^^^  Kristina Hoeppner committed Oct 20, 2012 297 .. figure:: /images/administration/email_settings.*  Kristina Hoeppner committed Jan 07, 2012 298 299 300 301 302 303  :alt: Email settings Email settings #. **SMTP host**: If you want to force Mahara to use a specific SMTP server instead of the system one, enter its hostname here, e.g. smtp.example.com. It is possible to specify more than one host by separating them with semicolons, e.g. smtp1.example.com;smtp2.example.com, but keep in mind that all other settings, e.g. authentication credentials and port numbers, will apply to all listed servers. It is not possible to specify different credentials for each server in this list. This feature is useful when SMTP host authentication is not required or you list different frontends for the same mail server in which case other settings will work. #. **SMTP port**: If your SMTP server uses a port number different from 25, you may specify it here. When encryption is enabled, the default ports are 465 for SSL and 587 for TLS. You only need to specify a port number if it is different from these. Check the correct settings with your mail service provider.  Kristina Hoeppner committed Jan 17, 2016 304 305 #. **User**: If your SMTP server requires authentication, enter the username here. #. **Password**: If your SMTP server requires authentication, enter the password here.  Kristina Hoeppner committed Jan 07, 2012 306 #. **SMTP encryption**: If your SMTP server supports encryption, enable it here.  Kristina Hoeppner committed Apr 06, 2012 307 308 #. **System mail address**: This email address is the address that emails are sent from Mahara.  Kristina Hoeppner committed Oct 12, 2014 309 310 311 312 313 .. index:: pair: Administration; Notification settings .. _notification_settings:  Kristina Hoeppner committed Nov 24, 2014 314 Notification settings  Kristina Hoeppner committed Oct 12, 2014 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You can set the default options for new users to receive notifications. Users can override these settings on their own *Settings → Notifications* page. The options you have are: * **Email**: Sends an email to your primary email address once the notification was created. In some cases, the cron needs to run first in order for the notification to be sent. * **Email digest**: Sends one email per day for all the notifications that you set to "Email digest". .. note:: If you select either of the email options, notifications will still arrive in the user's inbox, but they will be marked as read automatically. * **Inbox**: All notifications are only sent to your system inbox that you can reach in the top right corner next to the "Logout" button. * **None**: If you use this option, you will not get a notification for the selected notification type. Use this setting wisely as you may miss important notifications. .. note:: You cannot set "System messages" and "Messages from other users" to "None". .. figure:: /images/administration/notification_settings.* :alt: Notification settings Notification settings  Kristina Hoeppner committed Mar 22, 2015 338 #. **Contact us**: Only site administrators see this notification type. These are messages sent via the "Contact us" form that can be accessed in the footer of the site if the site administrators :ref:`decided to display this link