Translations by Mitsuhiro Yoshida

**Small page headers**: If checked, a small header and site navigation block are displayed when viewing or editing portfolio pages instead of the standard header. This option gives more space for the portfolio content itself. The small page header is visible at all times when you are on a portfolio page.

**Access to site files**: :index:`If checked, logged-in users will have access to site files in subfolders <single: Access to site files in subfolders>` of the folder "public". By default, only files directly in the folder "public" are accessible to them.

`Persona <https://persona.org/>`_ is a project of the `Mozilla Identity Team <http://identity.mozilla.com/>`_. It allows people to have one login across multiple sites without having to divulge the password to these sites. All they need to log in to a Persona-enabled site is their email address.

**Users can hide real names**: If checked, users who have set a :ref:`display name <about_me>` 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.

**reCAPTCHA on user registration form**: If checked, :index:`people who register themselves on the site <single: reCAPTCHA>` are required to fill in a `reCAPTCHA <http://recaptcha.org/>`_ test. This is a spam protection instrument.

**Show profile completion**: If checked, :index:`a progress bar with tips <single: Profile completion activation>` about what to complete in the user profile will be displayed in the sidebar to users. They can disable it in their account settings.

**Show homepage / dashboard information**: If enabled, information about Mahara and how it is used is displayed on the homepage for logged-out and on the *Dashboard* for registered users. Registered can disable this. See also :ref:`Quick links <dashboard_quick_links>`.

**Registration agreement**: If checked, you force users to agree to the "Terms and Conditions" before registration. You should edit your site's "Terms and Conditions" page before enabling this option. You can do so under :ref:`Static pages <edit_site_pages>`.

**Users can hide real names**: If checked, users who have set a :ref:`display name <about_me>` 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.

**Download folders as zip files**: If you tick the checkbox, you can download the contents of a folder displayed in a *Folder* block as zip file. Thus, it is very easy for a viewer to grab all files at once and download them to their computer.

**Contact us**: Only site administrators see this notification type. These are messages sent via the "Contact us" form that can be accessible in the footer of the site.

Users with a Persona account can go through the regular work flow of registering their accounts if the administrator allowed the registration for their institution (and requires the confirmation of accounts).

**Virus checking**: If you want all files that are uploaded by users to be run through the ClamAV virus scanner, you should select the virus checking option. You have to have `ClamAV <http://www.clamav.net/>`_ installed on your server.

**Small page headers**: If checked, a small header and site navigation block are displayed when viewing or editing portfolio pages instead of the standard header. This option gives more space for the portfolio content itself. The small page header is visible at all times when you are on a portfolio page.

*Skins* is an **experimental feature** in Mahara 1.8 for theming pages. While you can change a lot of style elements, changing all of them is not advised depending on the theme that is underlying your page.

The self-registration process with administrator approval also works for users who wish to use `Persona <https://www.persona.org/>`_. It needs to be set up as authentication method, and potential users go about in a very similar way.

If users have internal accounts and later link the email addresses they use to a Persona account, they can also log in with their Persona credentials when the site administrator allowed the Persona authentication in their institution.

The normal registration work flow and the potential confirmation of accounts does not come into play when you allow the auto-creation of accounts as this is an external authentication that is then considered to be trusted. We recommend you do not use the auto-creation of accounts unless you a sure that only trusted people can register. Otherwise, anybody with a Persona account could register on your site. This option could be used when your site is only available in an intranet or you want to allow anybody to register.

`Persona <https://persona.org/>`_ is a project of the `Mozilla Identity Team <http://identity.mozilla.com/>`_. It allows people to have one login across multiple sites without having to divulge the password to these sites. All they need to log in to a Persona-enabled site is their email address.

**We auto-create users**: Place a check mark in this box if you wish to allow new users to register for your institution automatically using their Persona credentials.

**Require reason for masquerading**: If checked, administrators will be required to enter a reason for :ref:`masquerading as other users <login_as>`. 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 <logging_settings>` to be turned on.

**Notify users of masquerading**: If checked, users will be notified :ref:`when an administrator masqueraded as them <login_as>`. The notification will include who, when and - if enabled under "Require reason for masquerading" - why. This setting needs :ref:`logging <logging_settings>` to be turned on.

**Users can disable device detection**: If checked, users can disable mobile device detection in their :ref:`account settings <general_account_options>`. This allows them to be more flexible in what they can view and do on a mobile device such as a smartphone or tablet. This setting is part of the responsive design changes to Mahara.

**Show users in public search**: If checked, :index:`usernames can appear in public search results <Administration; Show users in public search>`. 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.

**Staff report access**: If enabled, institution staff will have :ref:`access to the reports page for users in their institutions <user_reports>`. This page is normally restricted to administrators and lists extra user information including page access lists.

**Auto-suspend expired institutions**: If set, 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.

**Enable Spamhaus URL blacklist**: If enabled, URLs will be checked against the Spamhaus DNSBL. The `Spamhaus Project <http://www.spamhaus.org>`_ 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 <http://www.spamhaus.org/organization/dnsblusage.html>`_ before enabling this option.

**Users can hide real names**: If checked, users who have set a :ref:`display name <about_me>` 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.

**Enable SURBL URL blacklist**: If enabled, URLs will be checked against the SURBL DNSBL. `SURBL <http://www.surbl.org>`_ 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 <http://www.surbl.org/usage-policy.html>`_ before enabling this option.

**Logged-in profile access**: If this option is unchecked, profile pages are initially viewable by all logged-in users, but the owner is allowed to restrict access to a smaller group 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.

**Send weekly updates?**: If checked, your site sends weekly updates to `mahara.org <http://mahara.org>`_ with some statistics about your site. See also :ref:`Register your Mahara site <mahara_registration>`.

**Display remote avatars**: If checked, users' default profile pictures will be their `Gravatar <http://gravatar.com>`_ pictures (:ref:`remote avatar <remote_avatar>`). Users will need an account with Gravatar for this to work.

**Users allowed multiple institutions**: If checked, 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.

**Allow public profiles**: If checked, users can set their profile pages to be accessible to the public rather than only to logged-in users. However, only logged-in users can use interactive features such as the wall. If the option "Allow public pages" is chosen, "Allow public profiles" is automatically selected.

**License metadata**: If checked, users can choose under which license they want to make their content available. They can set a default license in their :ref:`account settings <account_settings>` and then decide for each artefact individually as well. This setting can be overwritten by an institution administrator in the institution settings.

**Anonymous comments**: If checked, logged-out users / users without a login can leave comments on public pages or pages they can access via a secret URL.

**License metadata**: If checked, users can choose under which license they want to make their content available. They can set a default license in their :ref:`account settings <account_settings>` and then decide for each artefact individually as well. This setting can be overwritten by an institution administrator in the institution settings.

**Allow public profiles**: If checked, users can set their profile pages to be accessible to the public rather than only to logged-in users. However, only logged-in users can use interactive features such as the wall. If the option "Allow public pages" is chosen, "Allow public profiles" is automatically selected.

**Allow mobile uploads**: If checked, users have the option of setting authentication tokens in their :ref:`account settings <general_account_options>`. That allows them to upload content from their :ref:`mobile devices <mobile_mahara>`. You can enter more than one token in order to connect mutliple mobile devices.

**Users allowed multiple institutions**: If checked, 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.

**Allow public profiles**: If checked, users can set their profile pages to be accessible to the public rather than only to logged-in users. However, only logged-in users can use interactive features such as the wall. If the option "Allow public pages" is chosen, "Allow public profiles" is automatically selected.

**Allow mobile uploads**: If checked, users have the option of setting authentication tokens in their :ref:`account settings <general_account_options>`. That allows them to upload content from their :ref:`mobile devices <mobile_mahara>`. You can enter more than one token in order to connect mutliple mobile devices.

**Allow custom licenses**: If checked, users can enter any URL as license for their content. If not checked, users will be limited to the licenses configured by the site administrator.

**License metadata**: If checked, users can choose under which license they want to make their content available. They can set a default license in their :ref:`account settings <account_settings>` and then decide for each artefact individually as well. This setting can be overwritten by an institution administrator in the institution settings.

**Users allowed multiple institutions**: If checked, 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.

**Allow group categories**: If checked, site administrators can create categories for users to assign to their groups. These categories can be used to filter groups in :ref:`My groups <my_groups>` and :ref:`Find groups <find_groups>`.

**Allow public pages**: If checked, users can create portfolio pages that are accessible to the public rather than only to logged-in users.

**Search usernames**: If checked, usernames can be searched on as part of "Search users" on the :ref:`Dashboard <dashboard>` and via :ref:`Find friends <find_friends>`.

**Institutional override**: Check this box if you want to allow institution administrators to set user file quotas and have default quotas for each institution.

**Allow public profiles**: If checked, users can set their profile pages to be accessible to the public rather than only to logged-in users. However, only logged-in users can use interactive features such as the wall. If the option "Allow public pages" is chosen, "Allow public profiles" is automatically selected.