Translations by Masayuki Kuwada

**Password**: If your SMTP server requires authentication, enter the password here.

**SMTP encryption**: If your SMTP server supports encryption, enable it here.

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.

**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.

**Virus flag release**: Only site administrators see this notification type. This notification lets site administrators know when files were released by the virus scanner. :ref:`Virus checking <security_settings>` must be turned on.

**Allow public pages**: If set to "Yes", users can create portfolio pages that are accessible to the public rather than only to registered users.

**Log events**: Decide which events you wish to log in the database. Events are generated every time the user does something significant on the site, such as editing a page. This log is kept in the ``event_log`` table in the database.

**Event log expiry**: Decide for how long you wish to keep your database log. If you selected to log all events, the table can grow quite quickly especially on an active site. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, the event log is not deleted by default.

**event**: action being carried out, e.g. beginning of a masqueradin session, saving of an artefact, deleting of a page or artefact, update user information, placing a block onto a page

**data**: additional information about the action, e.g. the ID of a block that is updated

Here you can edit the content of some pages around the site and the pages linked to in the footer:

Institutions can change the content of these pages on their :ref:`static institution pages <static_institution_pages>` to their liking and do not have to go with the content from the entire site.

All pages come with default text that you can change entirely. Every page must contain some text. You can use the visual editor to style your page.

**Page name**: Choose the page you want to edit from the drop-down menu.

**Page text**: Change the text in the editor window. You cannot leave this field empty.

The *Links and resources* menu appears to all users on most pages in the side bar. You can decide which links or files are available to everybody - also those without a login - and which ones only logged-in users shall see.

Provide the full URL to the link including ``http://`` or ``https://``.

You can also link to files that you have uploaded to the :ref:`site files area <site_files>`.

If you wish to display your links and resources in a specific order, map that order out before you add the links and files because you cannot change the order afterwards.

You have control over which links are displayed in the footer on each page.

Click the *Save changes* button to save your choices.

In order to use networking site-wide with any institution, you need to:

Click the *Delete this key* button if you want to generate a new key for your Mahara site, e.g. when you copied the database from another site or the other instance doesn't recognize it properly.

Depending on which site you wish to connect, you may need to provide some of the other information on the page, in particular the *WWW root* and the *public key*.

You can consult the `comprehensive guide for setting up a Mahoodle <https://wiki.mahara.org/index.php?title=System_Administrator%27s_Guide/Moodle%2F%2FMahara_Integration>`_ when connecting Mahara and Moodle.

You set up MNet for an institution when you :ref:`edit the authentication method XML-RPC <mnet>`.

.. image:: images/administration/licenses.* :alt: Available licenses on the site

Click the *Edit* button |edit| to change properties of a license. You can change the display name, acronym and the license icon, but not its URL. If you want to change the latter, you will need to create a new license.

**Display name**: Choose a name for your license that will be displayed around the site, e.g. on the details page of an artefact and in the drop-down menu in which users and institution administrators choose their defaul license. This field is required.

**Acronym**: If the license you want to add also has a commonly known acronym, you can enter it.

**Icon**: If the license you add has a logo that you want to display next to the icense, e.g. on the details page of an artefact, you can link it here.

This can be a http://... or https://... URL to an image elsewhere on your site or anywhere on the Internet.

Click the *Save* button to keep your changes to the license.

You cannot change the URL of the license. If you have a mistake in the URL, you will need to delete the license entirely and add it correctly.

Changing this page template is useful if you want to have all new pages use a specific layout instead of the built-in three-column layout. You could also place a block onto the template that any new page should have.

You cannot delete the dashboard, group homepage, profile and page templates.

You see how many entries you have in each journal.

Click the *Edit* button |edit| to make changes to your journal title, description or tags.

When you click the *Delete* button, you receive a confirmation message whether you really want to delete the journal or not. :index:`If you used the journal or an entry of it in a page <single: Confirmation message before deleting journal that is in use>`, Mahara lets you know so you can decide whether to delete the journal or not. Once you agree to delete the journal, your journal and all its content are removed permanently.

You share site pages and site collections like any other pages and collections.

When you want to allow copying, you have a few more options available than on regular pages or collections.

Click the *Import skin(s)* button to import skins that others have shared online.

Click the *Export* button |export| to export only this one skin.

The process of creating and editing a site skin is very similar to creating and editing :ref:`skins in your portfolio <create_skin>`.

You can install additional fonts to be used with :ref:`page skins <skins>`. Currently, you cannot use these fonts anywhere else.