Translations by Mitsuhiro Yoshida

**Institution expiry date**: Set the expiry date for this institution by selecting the year, month and day from the drop-down menus when taking the check mark off the "Not specified" check box. Institutions do not expire by default.

When you clicked the *Edit access* button |edit_access| on the *Share* page for institution pages and collections, place a tick in the check box *Allow copying* under *Advanced options*.

**Do partial string match with institution shortname**: Check this check box to treat the value in "Institution value to check against attribute" like a regular expression.

**Locked fields**: Put a check mark into each check box for which users are not allowed to change the value. Disabled check boxes are for profile fields which are locked in the institution settings for "No institution". These profile fields are locked at the site level and cannot be unlocked for individual institutions.

**Institution expiry date**: Set the expiry date for this institution by selecting the year, month and day from the drop-down menus when taking the check mark off the "Not specified" check box. Institutions do not expire by default.

If your site has added custom pages to the menu, e.g. like `MyPortfolio.school.nz <http://myportfolio.school.nz>`_ where you have a number of additional informational pages, you can now edit their content from the *Edit site pages* screen. In order to do so, a server administrator needs to make `changes on the backend <https://bugs.launchpad.net/mahara/+bug/999464>`_.

Select which site pages shall appear in the footer on each page. You can change the text of "Terms and conditions", "Privacy statement" and "About" in :ref:`Edit site pages <edit_site_pages>`.

**Membership expires**: If you wish, specify the date when the user will be removed from this institution automatically. If you click the "Not specified" check box, no end date will be set. The date displayed in the greyed out date boxes is always the current one when "Not specified" is chosen.

If this setting is on, it must NOT be possible to self register on the site for ANY institution - otherwise users could simply pick usernames of people's accounts they wished to steal. That is why you should not see the registration check boxes in any institution if you have this feature turned on.

**Membership expires**: If you wish, specify the date when the user will be removed from this institution automatically. If you click the "Not specified" check box, no end date will be set. The date displayed in the greyed out date boxes is always the current one when "Not specified" is chosen.

**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:`Edit site pages <edit_site_pages>`.

**Institution expiry date**: Set the expiry date for this institution by selecting the year, month and day from the drop-down menus when taking the check mark off the "Not specified" check box. Institutions do not expire by default.

If your site has added custom pages to the menu, e.g. like `MyPortfolio.school.nz <http://myportfolio.school.nz>`_ where you have a number of additional informational pages, you can now edit their content from the *Edit site pages* screen. In order to do so, a server administrator needs to make `changes on the backend <https://bugs.launchpad.net/mahara/+bug/999464>`_.

**Sync groups stored as user attributes**: Tick this check box if each LDAP user record has an attribute which indicates a group the user should be in. This setting will cause the LDAP sync cron to create a group for each unique value in the specified user attribute (or in those listed in the "Acceptable group names" field), and place each user in the appropriate group (or groups, if they have multiple values for the attribute).

**Process nested group**: Tick this check box if your groups can contain other groups as members. If enabled, the sync process will recursively include the members of these nested groups into the parent group.

**Member attribute is a dn?** Tick this check box if if each entry in the "Group member attribute" field is a "distinguished name". Disable this setting if each entry in "Group member attribute" field is a username only.

**Sync groups stored as LDAP objects**: Tick this check box if your groups are stored as standalone records in LDAP. Example:

**Auto-create missing groups**: Tick this check box if you want to have new groups in your LDAP directory created automatically in Mahara.

**Membership expires**: If you wish, specify the date when the user will be removed from this institution automatically. If you click the "Not specified" check box, no end date will be set. The date displayed in the greyed out date boxes is always the current one when "Not specified" is chosen.

**Account expires**: Choose the date on which the user's login is automatically disabled. The default setting is that the date is not specified. You always see the current date in the greyed out date fields. You can set an automatic account expiry date for all users in the :ref:`account settings of the site configuration <config_site_account_settings>`.

If your site has added custom pages to the menu, e.g. like `MyPortfolio.school.nz <http://myportfolio.school.nz>`_ where you have a number of additional informational pages, you can now edit their content from the *Edit site pages* screen. In order to do so, a server administrator needs to make `changes on the backend <https://bugs.launchpad.net/mahara/+bug/999464>`_.

**Send weekly updates**: Enable this check box if you wish so send regular updates about your site to the project. These updates are based on changes in your site and include only anonymous updates.

When you clicked the *Edit access* button |edit_access| on the *Share* page for institution pages and collections, place a tick in the check box *Allow copying* under *Advanced options*.

**Port number**: Enter the port number that the remote application is listening at. You probably will not need to change this unless you are connecting to a ``https`` service or your remote application is running on a non-standard port. This field is required.

**Do partial string match with institution shortname**: Check this check box to treat the value in "Institution value to check against attribute" like a regular expression.

**Match username attribute to remote username**: This box is selected by default and needs to stay selected. It matches the user attribute value to the remote username field assigned to a given user (not the internal Mahara username). Only if you have the :ref:`experimental feature of "usersuniquebyusername" <usersuniquebyusername>` turned on can you deselect this check box. We do not recommend this unless you are very experienced and have control over all applications in question.

**We auto-create users**: This is unselected by default and needs to stay unchecked if the option "Match username attribute to remote username" is enabled. Check this box to create user accounts on Mahara automatically when a user authenticates successfully but does not yet have an account. Only if you have the :ref:`experimental feature of "usersuniquebyusername" <usersuniquebyusername>` turned on can you select this check box. We do not recommend this unless you are very experienced and have control over all applications in question.

**Institution value to check against attribute**: Enter the value that will be checked against the institution attribute value as passed from the IdP. If the institution regex check box "Do partial string match with institution shortname" is selected, this value can be a `regular expression <http://en.wikipedia.org/wiki/Regular_expression>`_ that will be used to check against the institution attribute value. This field is required.

**Locked fields**: Put a check mark into each check box for which users are not allowed to change the value. Disabled check boxes are for profile fields which are locked in the institution settings for "No institution". These profile fields are locked at the site level and cannot be unlocked for individual institutions.

**Institution expiry date**: Set the expiry date for this institution by selecting the year, month and day from the drop-down menus when taking the check mark off the "Not specified" check box. Institutions do not expire by default.

**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:`Edit site pages <edit_site_pages>`.

If this setting is on, it must NOT be possible to self register on the site for ANY institution - otherwise users could simply pick usernames of people's accounts they wished to steal. That is why you should not see the registration check boxes in any institution if you have this feature turned on.

**Auto-create users in cron**: Tick this check box if you want new users in your LDAP directory to get an account automatically.

Select which site pages shall appear in the footer on each page. You can change the text of "Terms and conditions", "Privacy statement" and "About" in :ref:`Edit site pages <edit_site_pages>`.

Select **None** to clear your selections from the check boxes.

Select the users whose authentication method and remote username you want to change by either putting a check mark in the check boxes or clicking on *All* to select all users on that page.

Select **None** to clear your selections from the check boxes.

Select the users whose authentication method and remote username you want to change by either putting a check mark in the check boxes or clicking on *All* to select all users on that page.

Select **All** to mark all file types.

Use the *up arrow* and *down arrow* to move a specific authentication method up or down in the list.

**Enable group categories**: Tick this check box to enable group categories for the entire site.

Select **None** to clear your selections from the check boxes.

Select **All** to mark all file types.

In order to delete a plugin completely, you must delete the code and all database tables that pertain to the plugin.

Click the check box to enable comment ratings.

**Update user info in cron**: Tick this check box if you wish for user information to be updated via the cron if they changed in the LDAP record.

Select which site pages shall appear in the footer on each page. You can change the text of "Terms and conditions", "Privacy statement" and "About" in :ref:`Edit site pages <edit_site_pages>`.

Select the users whose authentication method and remote username you want to change by either putting a check mark in the check boxes or clicking on *All* to select all users on that page.