8.5. Institutions

Administration → Institutions

You can use Mahara as multi-tenanted instance. That means that several different institutions can share one Mahara installation. All users from these different institutions can:

  • share portfolio pages with each other
  • give feedback on each other’s pages
  • work collaboratively in groups across institution boundaries

In Administration you can set up as many institutions as you wish. Institution administrators can only administer their users and their institutions but not make any changes to site settings.

You can also set up institutions for different parts of your organisation to use different themes, have different default settings and / or authentication methods.

8.5.1. Overview

Administration → Institutions → Institutions (site administrator)

Administration → Institutions → Settings (institution administrator)

You see an overview of all institutions that exist on this Mahara installation (site administrator) or that you have access to as institution administrator.

Note

Institution administrators who manage only one institution do not see this page, but immediately the settings for their only institution.

Overview page for institutions

Overview page for institutions

  1. Search: Search for a particular institution by its name and then click the Search button.
  2. Institution: Institutions are listed alphabetically. If you click the institution’s name, you are taken to the contacts page.
  3. Members: Number of registered members in this institution.
  4. Maximum: Maximum allowed members in this institution.
  5. Staff: Number of institution members with staff rights.
  6. Administrators: Number of institution members with institution administrator rights.
  7. Click the Edit button edit to change institution settings.
  8. Click the Delete button delete to delete an institution. You can only delete an institution when there are no members in it.
  9. Click the Add institution button when you want to create a new institution. This button is only visible to site administrators.
  10. Click the Edit members button when you want to add or remove members from an institution.
  11. Click the Edit staff button when you want to add or revoke staff rights for an institution member.
  12. Click the Edit administrators button when you want to add or revoke institution administrator rights for an institution member.

Note

The institution “No institution” is the default “institution”. It cannot be deleted as it is the standard Mahara site.

8.5.2. Add an institution

Note

Only site administrators can add institutions. However, once an institution exists, institution administrators can change many of the settings.

When you want to add an institution by clicking the Add button on Administration → Institutions → Institutions, you need to provide some basic information for the new institution. You can change all settings except the Institution name later on.

Add a new institution

Add a new institution

  1. Institution name: This field is required. It is the unique identifier of this institution in the database. It must be one word without numbers and symbols.

  2. Institution display name: This field is required. It is the name that all users see throughout the site to identify this institution.

  3. 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 you specify an expiry date for this institution, once the warning time for institution expiry has been reached, site and institution administrators will receive a otification about this institution’s impending expiry.
    • If the auto-suspend expired institutions option is set, then once the expiry date has been reached, this institution will be automatically suspended, and users of this institution will no longer be able to log in.
    • The warning time for institution expiry and the auto-suspend expired institutions options can be found in the institution settings under Administration → Configure site → Site options.
  4. Registration allowed: Check this box when you want to allow self-registration of new users. As institution administrators, you will be asked to confirm that users can join your institution. If you decline, their new account will be associated with “No institution” unless you have the Confirm registration option clicked. When you do not allow registration, nobody can register a new account, ask to join your institution or leave it without your permission.

  5. Confirm registration: Check this box if you want to control that no new accounts are created unless the administrator approves the registration. You receive a notification about pending registrations when a new user wants to register.

  6. Default membership period: You can set how long users will remain associated with this institution per default. Choose an option from the drop-down menu and then specify the number of days, weeks, months or years. After this length of time, the users will be removed from the institution. Users will receive a notification before this time reminding them that they will be removed soon. However, that does not mean that they will lose their account. They will still have that and be associated with “No institution”.

  7. Logo: You can upload an image that will be displayed to your institution’s members in place of the standard header logo.

  8. Theme: Use the drop-down menu to choose the theme that you wish to use for this institution. All pages in that institution will receive that theme. When users from other institutions view portfolio pages that were created in this institution, they will see this institution’s theme on these pages. If Site default is selected, when a site administrator changes the site default theme, the theme for the users of this institution will change, too. You can install more themes in the theme folder on the server. Check out the community-contributed themes. If users are allowed to have page themes, these pages are not affected by theme changes. Mahara also has a configurable theme which allows you to create a theme on the fly.

  9. Show online users: If the site administrator allowed the “Online users” side block, you can decide which group of users you want to have displayed for this institution:

    • None: The side block is not displayed to institution members.
    • Institution online: Only institution members are displayed in the side block.
    • All: All users on the site are displayed in the side block
  10. new in Mahara 1.7 Require license information: If you check this box, your institution members will need to choose a license for each artefact they upload or create. They can set a default license in their account settings. You only see this option if the site administrator turned License metadata in the general site settings.

  11. new in Mahara 1.7 Default license: You can choose a default license for your institution members’ content. They can overwrite this default license in their account settings. You only see this option if the site administrator turned License metadata on in the general site settings. If the site administrator allowed custom licenses, you can enter one using the drop-down menu option “Other license (enter URL)”. This license can then also be used by your institution members.

    Note

    If you are not sure which default license to choose, please consult your organisation’s lawyer or a copyright lawyer.

  12. Default quota: You can set the amount of file quota new users registering with this institution shall have.

  13. Update user quota: If you check this box, the default quota you choose above will be applied to all existing institution members.

  14. Allow institution public pages: Put a check mark into this box if you want to allow users belonging to this institution to create portfolio pages that are accessible to the public rather than only to logged-in users. If you allow public pages, users can also create secret URLs for their pages. Otherwise they cannot.

  15. Maximum user accounts allowed: Specify the maximum number of accounts that can be created in this institution. If you leave this field blank, there is no limit to the number of accounts.

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

    Note

    Locking profile fields such as first name, last name and display name can be beneficial for institutions that wish to always identify their users by their real names and not allow users to choose nicknames.

  17. Click the Submit button to save your changes and create this institution.

  18. Click the Cancel button to abort the creation of this institution.

8.5.2.2. Use the configurable theme

If you do not want to use one of the built-in themes of Mahara or one of the community-contributed themes, you can either build your theme from scratch or use the configurable theme in conjunction with the logo upload.

Note

The configurable theme is only a display theme. That means that users of the institution in which it is in use see the theme applied to the site and their pages. However, when users from another institution browse the portfolio pages of users from this institution, they do not see the configurable theme, but their own theme.

You can change the configurable theme directly on the institution settings page.

Options for the configurable theme

Options for the configurable theme

In order to change any of the colours, either provide the hexadecimal color code or choose the colour from the colour picker that becomes available as soon as you click in one of the colour fields.

  1. Theme: Choose the “Configurable Theme” from the drop-down menu and the “Custom theme configuration” options become visible.
  2. Background: Background colour for the entire site, esp. visible in the header and footer.
  3. Text on background: The text that is displayed on the background colour, e.g. in the header and footer.
  4. Link: The link colour on any pages unless it is in the sidebar or navigation.
  5. Headings: The heading colour for all headings except in the sidebar.
  6. Sidebar background: The background colour of any sidebar. It should form a good contrast to the heading colour of the sidebar as that is always white.
  7. Sidebar content background: The colour of the inside of a sidbar.
  8. Sidebar link: The colour of a link inside a sidebar.
  9. Navigation background: The colour of the top navigation bar.
  10. Navigation text: The colour of the text / links in the main navigation bar.
  11. Sub navigation background: The colour of the secondary navigation and the highlighted section in the main navigation bar.
  12. Sub navigation text: The colour of the text / links in the secondary navigation and the highlighted section in the main navigation bar.
  13. Row background: The colour of the background anywhere rows appear.
  14. Colour picker: Either type in the hexadecimal colour code directly into the colour field or use the cross and arrow from the colour picker to decide on your new colour.
  15. Reset colours: If you want to go back to a blank slate of the configurable theme, place a check mark in this box to get back to the original colours of the configurable theme.
  16. Click the Submit button at the bottom of the page to make your changes.

Note

If you do not see the theme changes immediately when you are logged in as institution member, you may have to clear your browser cache.

Example of the configurable theme

Example of the configurable theme

The numbers on the example page refer to the configurable theme options above.

8.5.3. Edit an institution

Administration → Institutions → Institutions → Click the Edit button next to an institution

Once you have created your institution, you can edit its settings, suspend or delete the institution. You will have to choose at least one authentication method for this institution so that user accounts can be created.

Note

Only site administrators can add, edit and delete authentication methods for an institution and suspend it. An institution can only be deleted if there are no members in it.

You can add multiple authentication methods to your institution and thus allow various entry points for your users. You should set up at least one authentication method. Otherwise, nobody can log in to this institution.

Before you can use the IMAP, LDAP, SAML or XML-RPC authentication methods, you must install their extensions on your server.

Plugins available for authentication in an institution

Plugins available for authentication in an institution

  1. Once your institution is created, the settings include an additional option, Authentication plugin. You see all authentication methods that are already in use for this institution listed.
  2. From the drop-down menu choose one of the authentication methods that are available:
  3. Click the Add button to see the configuration screen for an external authentication method before it is added.

Warning

Be careful when choosing the “None” authentication method. This allows anyone to log in. It should only be used for testing purposes.

8.5.3.1. IMAP authentication

You can use this authentication method to receive the login information for your users from your IMAP server.

Set up IMAP authentication

Set up IMAP authentication

  1. Authority name: Enter a descriptive name to help you identify this authority. Preferably, choose a short name. This field is required.
  2. Hostname or address: Specify the hostname in URL form. This field is required.
  3. Port number: Specify the port under which your IMAP server can be reached. The default is 143. This field is required.
  4. Protocol: Select the IMAP protocol you are using by selecting it from the drop-down menu. This setting is required:
    • IMAP
    • IMAP / SSL
    • IMAP / SSL (self-signed certificate)
    • IMAP / TLS
  5. Password-change URL: If your users can only change their password in one central space, provide the URL here.
  6. Click the Submit button to enable this authentication method or click the Cancel button to abort your changes.

8.5.3.2. LDAP authentication

Use this authentication method to authenticate against an LDAP server so that your users can log in with their usual login and password.

Set up LDAP authentication

Set up LDAP authentication

  1. Authority name: Enter a descriptive name to help you identify this authority. Preferably, choose a short name. This field is required.
  2. Host URL: Specify hosts in URL form, e.g. ldap://ldap.example.com. Separate multiple servers with ; for failover support. This field is required.
  3. Contexts: List the contexts where users are located. Separate different contexts with ;, e.g. ou=users,o=org;ou=other,o=org. This field is required.
  4. User type: Select from the drop-down menu how users are stored in the LDAP directory. This field is required. You can choose between:
    • Novell Edirectory
    • posixAccount (rfc2307)
    • posixAccount (rfc2307bis)
    • sambaSamAccount (v. 3.0.7)
    • MS Active Directory
    • default
  5. User attribute: Enter the attribute used to search for users. It is often cn. This field is required.
  6. Search subcontexts: Select “Yes” if you want to search for the users also in subcontexts. This setting is required.
  7. Distinguished name: If you want to use bind-user to search users, specify it here. It should look something like cn=ldapuser,ou=public,o=org. Leave this blank for anonymous bind.
  8. Password: Enter the password for the “distinguished name”.
  9. LDAP version: Choose the LDAP version you are using from the drop-down menu. This setting is required.
  10. TLS encryption: Check this box if you use this encryption mechanism.
  11. Update user info on login: Check this box to update the first name, last name and email address with the corresponding LDAP values at each login. Enabling this option may prevent some MS ActiveDirectory sites / users from subsequent Mahara logins.
  12. We auto-create users: Check this box to create user accounts on Mahara automatically when a user authenticates successfully but does not yet have an account.
  13. LDAP field for first name: Enter the name of the field in the LDAP record that contains the user’s first name.
  14. LDAP field for surname: Enter the name of the field in the LDAP record that contains the user’s last name.
  15. LDAP field for email: Enter the name of the field in the LDAP record that contains the user’s email address.
  16. LDAP field for student ID: Enter the name of the field in the LDAP record that contains the user’s student ID.
  17. LDAP field for display name: Enter the name of the field in the LDAP record that contains the user’s display name.
  18. Click the Submit button to enable this authentication method or click the Cancel button to abort your changes.

8.5.3.3. Persona authentication

Persona is a project of the Mozilla Identity Team. 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.

Configure the Persona authentication

Configure the Persona authentication

  1. 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.
  2. Click the Submit button to enable this authentication method or click the Cancel button to abort your changes.

Warning

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.

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

Note

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.

8.5.3.4. SAML authentication

Choose this authentication method for your institution when you have a SAML 2.0 Identity Provider Service set up for your organisation that allows you to use the same login for multiple applications.

SAML 2.0 authentication

SAML 2.0 authentication

  1. Institution attribute (contains ”...”): Enter the attribute that will be passed from the Identity Provider (IdP) that shows which institution the user belongs to. This usually directly correlates to the LDAP attribute (the signin service of the IdP), e.g. eduPersonOrgDN. This field is required.

  2. 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 that will be used to check against the institution attribute value. This field is required.

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

  4. User attribute: Enter the name of the attribute passed by the IdP that contains the username. This field is required.

  5. 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 experimental feature of “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.

    Warning

    By default, SAML authentication instances have the “Match username attribute to remote username” setting selected. If that setting were unchecked, someone with control over any SAML identity provider could gain control over any user account on that Mahara site by setting the username attribute accordingly. In other words, administrators of one institution could control users in other institutions. You would only be able to deselect this setting if you set the “usersuniquebyusername” variable to “true” in config.php. However, you should not do that on a Mahara instance to which multiple SAML providers connect and you are not in control of all usernames that are created.

    See also

    If you deselect “Match username attribute to remote username”, you get an error message which talks about the config setting for “usersuniquebyusername”. Please refer to the experimental feature of the “usersuniquebyusername” variable for more information.

  6. Allow users to link own account: Check this box if you want to allow users to link their own internal Mahara account to the authenticated SAML account. This depends on the “Match username attribute to remote username” option being enabled. If this setting is turned on when users try to log in via SSO and their username as well as the email for example match an internal username, they can link their accounts. That would allow them to log in either via the SSO login or via the regular login box into the same account and avoid account duplication.

  7. Update user details on login: Check this box to update the first name, last name and email address with the corresponding IdP values passed through at each login.

  8. 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 experimental feature of “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.

  9. SSO field for first name: Enter the name of the attribute passed by the IdP that contains the user’s first name.

  10. SSO field for surname: Enter the name of the attribute passed by the IdP that contains the user’s last name.

  11. SSO field for email: Enter the name of the attribute passed by the IdP that contains the user’s email address.

  12. Click the Submit button to enable this authentication method or click the Cancel button to abort your changes.

8.5.3.5. XML-RPC / MNet authentication

Use the XML-RPC authentication for connecting a Mahara instance to a Moodle or an other Mahara installation for sharing login information. With Moodle 2 that does not only mean that you can log in to Mahara via Moodle, but also that you can transfer certain activities into your Mahara portfolio from Moodle.

A Moodle site can only be connected to Mahara once no matter how many institutions you have set up. Every XML-RPC authentication instance in Mahara must have its own unique remote wwwroot and must be associated with a single institution.

Note

You must have networking enabled in order to use this authentication method.

Set up MNet authentication

Set up MNet authentication

  1. Authority name: Enter a descriptive name to help you identify this authority. Preferably, choose a short name. This field is required.

  2. WWW root: Enter the web address of the root of the remote application, e.g. http://example.com. This field is required.

  3. Site name: Enter the name to present to your users to identify the remote site. If you enable SSO, they may click on this name to start a session at the remote site. This field is required.

  4. Application: Choose the application on the other end. You can choose between “Mahara” and “Moodle”.

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

  6. Parent authority: If you set a parent authority from the already existing authentication methods, users will be able to log in using that authority as well as MNet. For example, you could set up SAML authentication and have that be the parent of this MNet authority. That means that users will be able to log in by clicking the SSO login button using their SSO credentials as well as via MNet from their Moodle. You do not have to set a parent authority. If you do not, users using MNet will only be able to access Mahara via MNet, i.e. log in to Moodle or the other Mahara first.

    Note

    If you choose a Parent authority, ensure that all the users are associated with this authentication method instead of the MNet one. Otherwise, they will not be able to log in via the parent authentication method. If the remote username for MNet and the other authentication method is already the same, you just need to change the authentication method. If they are not yet the same, you need to update the user details together with changing their authentication method.

  7. Wrong login box message: Enter a message to display when a user tries to log in via Mahara’s login form but is not allowed to if you have not set up a parent authority.

  8. SSO direction: Choose your SSO direction from the drop-down menu:

    • They SSO in: Enable this option to allow users from the remote site to roam to your Mahara site without having to enter their username and password. This is the most commonly used setting.
    • We SSO out: Enable this option to allow your users to roam from Mahara to the remote site without having to enter their username and password there.
  9. Update user info on login: Enable this option to bring over user data from the remote site upon login and update your Mahara user record with any changes. The following fields, when filled in on Moodle, are filled in Mahara:

    • first name (always carried over)
    • last name (always carried over)
    • email address (always carried over)
    • profile picture
    • description (introduction on Mahara)
    • city
    • country
    • language
    • HTML editor setting
  10. We auto-create users: Check this box to create user accounts on Mahara automatically when a user authenticates successfully but does not yet have an account.

  11. We import content: Not all network-enabled applications support this, but if they do, e.g. Moodle 2.x, this will allow users of the remote site to import content to Mahara. It depends on the option “They SSO in” from “SSO direction” and it is sensible to also have “We auto-create users” set.

  12. Click the Submit button to enable this authentication method or click the Cancel button to abort your changes.

See also

Refer to the comprehensive guide about setting up Mahoodle, the combination of Mahara and Moodle, for step-by-step instructions on how to set everything up on the Moodle side and on Mahara. The guide explains the steps for both Moodle 1.9 and Moodle 2.x.

8.5.3.6. Order of authentication methods

If you have set up multiple authentication methods in one institution, you can decide on the order in which they are checked.

Order of authentication methods

Order of authentication methods

  1. Use the up arrow and down arrow to move a specific authentication method up or down in the list.
  2. Delete a particular authentication method by clicking on the Delete link [x].

Note

You cannot delete an authentication method when there are still users who require it to log in. Before deleting an authentication method, you have to move the users to another authentication method.

8.5.3.7. Suspend institution

A site administrator can suspend an institution at any time.

Suspend an institution

Suspend and institution

Click the Suspend institution button to make an institution (temporarily) unavailable to its users.

8.5.4. Members

Administration → Institutions → Members

You can add and remove members from one institution in bulk. As site administrator, you can always add members to an institution. As institution administrator, you can only invite users to become members.

You can filter users to display fewer and add to or remove them more easily from your institution:

  • People who have requested institution membership
  • People who have not requested institution membership
  • People who have left a given institution
  • People who are already institution members
  • People who have been invited

Note

You can double-click a name and it will be moved to the other side. This goes for all functionalities that are similar to this one here.

8.5.4.1. People who have requested institution membership

If your institution allows self-registration, users who are not already members of your institution can request to join it.

Institution administrators receive notifications about membership requests. Site administrators only receive notifications about users wanting to join “No Institution”.

Accept or decline institution membership requests

Accept or decline institution membership requests

  1. Users to display: Choose People who have requested institution membership.
  2. Institution: Choose from the drop-down menu to which institution you wish to add users. If there is only one institution, its name will be displayed without the drop-down menu.
  3. Users who have requested membership: Select the users you wish to add to the institution.
  4. Search: You can also search for users in the search box if there are too many names listed.
  5. Add the users by clicking the right-arrow button right-arrow.
  6. Users to be added / rejected: If you put users into the box for users to be added / rejected by accident, you can remove them from that list by clicking on them.
  7. Then click the left-arrow button left-arrow, and they are removed from the list.
  8. When you have all the members you wish to add to the institution, click the Add members button.
  9. Alternatively, if you wish to decline users membership, you can select them and then send a general denial by clicking the Decline requests button.

8.5.4.2. People who have not requested membership yet

An admin can also take the initiative and invite or add users to an institution.

Invite or add users to become institution members

Invite or add users to become institution members

  1. Users to display: Choose People who have not requested membership yet.
  2. Institution: Choose from the drop-down menu to which institution you wish to invite users. If there is only one institution, its name will be displayed without the drop-down menu.
  3. Non-members: Select the users you wish to invite to the institution.
  4. Search: You can also search for users in the search box if there are too many names listed.
  5. Add the users to the list Users to be invited by clicking the right-arrow button right-arrow.
  6. If you put a person into the box for users to be invited by accident, you can remove them from that list by clicking on them.
  7. Then click the left-arrow button left-arrow, and they are removed from the list.
  8. When you have all the members you wish to invite to the institution, click the Invite users button. The users receive a notification and can accept or decline the institution membership invitation.
  9. Alternatively, you can click the Add members button as site administrator and add users directly to the institution without asking them first.

8.5.4.3. People who have left a given institution

An administrator can filter users by the previous institution to which they were attached in order to find them more quickly.

Note

This is only of importance for a multi-tenanted Mahara instance with at least 2 institutions.

Invite / add users who had left an institution

Invite or add users to become institution members when they had left an institution

  1. Users to display: Choose People who have left a given institution. “Left” is interpreted loosely, it also means when an administrator removed them from an institution.
  2. Previous institution: Choose the institution from which you want to add users. The users must have left it first to be listed here.
  3. Institution: Choose from the drop-down menu to which institution you wish to invite users. If there is only one other institution, its name will be displayed without the drop-down menu.
  4. Users who have left institution [name of the institution]: Select the users you wish to invite or add to the other institution.
  5. Search: You can also search for users in the search box if there are too many names listed.
  6. Add the users to the list Users to be invited by clicking the right-arrow button right-arrow.
  7. If you put a person into the box for users to be invited by accident, you can remove them from that list by clicking on them.
  8. Then click the left-arrow button left-arrow, and they are removed from the list.
  9. When you have all the members you wish to invite to this institution, click the Invite users button. The users receive a notification and can accept or decline the institution membership invitation.
  10. Alternatively, you can click the Add members button as site administrator and add users directly to the institution without asking them first.

Note

Mahara keeps track of the last institution of a user via an invisible tag.

8.5.4.4. People who are already institution members

You can remove users from an institution, e.g. if they are no longer students at a school or university, but should still have an account on Mahara or when they are just switching institutions on the same Mahara instance.

Remove users from an institution

Remove users from an institution

  1. Users to display: Choose People who are already institution members.
  2. Institution: Choose from the drop-down menu which institution’s members you wish to display. If there is only one institution, its name will be displayed without the drop-down menu.
  3. Current members: Select the users you wish to remove from the institution.
  4. Search: You can also search for users in the search box if there are too many names listed.
  5. Add the users to the list Users to be removed by clicking the right-arrow button right-arrow.
  6. If you put a person into the box for users to be removed by accident, you can remove them from that list by clicking on them.
  7. Then click the left-arrow button left-arrow, and they are removed from the list.
  8. When you have all the members you wish to remove from your institution, click the Remove users button.

8.5.4.5. People who have been invited

An administrator can uninvite users from an institution.

Uninvite users from joining your institution

Uninvite users from joining your institution

  1. Users to display: Choose People who have been invited.
  2. Institution: Choose from the drop-down menu which institution’s members you wish to display. If there is only one institution, its name will be displayed without the drop-down menu.
  3. Invited users: Select the users you wish to univite from joining the institution.
  4. Search: You can also search for users in the search box if there are too many names listed.
  5. Add the users to the list Users to be uninvited by clicking the right-arrow button right-arrow.
  6. If you put a person into the box for users to be uninvited by accident, you can remove them from that list by clicking on them.
  7. Then click the left-arrow button left-arrow, and they are removed from the list.
  8. When you have all the users you wish to uninvite from the institution, click the Revoke invitations button.

8.5.5. Institution staff

You can give users staff rights in an institution in which they are members. The staff role will allow them to create course groups for example. This page allows you to do that in bulk for many users at once.

See also

You can also give staff rights on the user account settings page.

Give users institution staff rights

Give users institution staff rights.

  1. Institution: Choose the institution from the drop-down menu for which want to give staff rights to members.
  2. Institution members: Select the institution members who shall get staff rights.
  3. Search: You can also search for users in the search box if there are too many names listed.
  4. Add the users to the list Institution staff by clicking the right-arrow button right-arrow.
  5. If you put a user into the institution staff list by accident or want to remove existing staff members and return them to normal membership status, select them.
  6. Then click the left-arrow button left-arrow, and they are removed from the list.
  7. When you have all the members you wish to have as staff in the institution, click the Submit button.

8.5.6. Institution administrators

You can give users administrator rights in an institution in which they are members. The administrator role will allow them to manage users in their own institution. This page allows you to do that in bulk for many users at once.

See also

You can also give admin rights on the user account settings page.

Give users institution admin rights

Give users institution admin rights.

  1. Institution: Choose the institution from the drop-down menu for which want to give admin rights to members.
  2. Institution members: Select the institution members who shall get admin rights.
  3. Search: You can also search for users in the search box if there are too many names listed.
  4. Add the users to the list Current admins by clicking on the right-arrow button right-arrow.
  5. If you put a user into the institution admin list by accident or want to remove existing admin members and return them to normal membership status, select them.
  6. Then click on the left-arrow button left-arrow, and they are removed from the list.
  7. When you have all the members you wish to have as admins in the institution, click the Submit button.

8.5.7. Admin notifications

Administration → Users → Admin notifications

The Admin notifications page lists all users with institution and site administrator access on your site. It shows their selected notification preferences for all admin notifications. There should be at least one administrator receiving each type of message generated.

Note

Institution administrators only see admin notifications for their own institutions.

Admin notifications are:

  • Contact us
  • Objectionable content
  • Repeat virus upload
  • Virus flag release
Overview of the admin notification types

Overview of the admin notification types

8.5.8. Institution pages

Administration → Institutions → Pages

You can create pages for your entire institution. Although you could always create pages under a regular user account that other users could copy into their own portfolio, the advantage of institution pages is that new members in the institution can receive a copy upon joining the institution.

Create institution pages

Create institution pages

  1. Institution: Click on the institution in the drop-down menu for which you want to create or edit institution pages.
  2. Search: If you have a lot of institution pages, you can search for a particular one here. You can search in the title, description and tags or only in tags.
  3. Click the Create page button to start a new institution page.
  4. Click the Copy page button to start a new page from a copy of an already existing one. This does not have to be an institution page but can be any page that you are allowed to copy.
  5. View an institution page that you have already created.
  6. Click the Edit button edit to change an existing institution page.
  7. click the Delete button delete to delete an institution page.

Note

Creating and editing an institution page is very similar to creating and editing a portfolio page. However, not all blocks are available when editing an institution page in the page editor due to the different context. Please refer to the overview of blocks for a list of all the blocks that you can use in an institution page.

8.5.9. Institution collections

Administration → Institutions → Collections

You can create collections for your entire institution. Although you could always create collections under a regular user account that other users could copy into their own portfolio, the advantage of institution collections is that new members in the institution can receive a copy upon joining the institution.

Create institution collections

Create institution collections

  1. Institution: Click on the institution in the drop-down menu for which you want to create or edit institution collections.
  2. Click the New collection button to start a new institution collection.
  3. Click the Copy a collection button to start a new collection from a copy of an already existing one. This does not have to be an institution collection but can be any collection that you are allowed to copy.
  4. Click on the collection title to go to the first page of the collection.
  5. View the description of this collection.
  6. Click on any title of a page within a collection to jump directly to it.
  7. Click the Manage button manage to move pages within a collection, add to or delete pages from a collection.
  8. Click the Edit button edit to change the title and description of a collection.
  9. Click the Delete button delete to delete the collection. The pages will still exist.

Note

Creating and editing an institution collection is very similar to creating and editing a portfolio collection.

8.5.10. Share institution pages and collections

Administration → Institutions → Share

You can see a list of all institution pages and collections for a specific institution.

Share institution pages and collections

Share institution pages and collections

  1. Institution: Select the institution from the drop-down menu for which you want to see the institution pages and collections.
  2. Collections: All institution collections for that institution are listed here.
  3. Pages: All institution pages for that institution are listed here.
  4. Access list: View the access permissions for the pages and collections.
  5. Click the Edit access button edit_access to change the permissions of who can view and copy a page or collection.
  6. Click the Edit Secret URL button edit to define a secret URL for a page or collection.

Sharing an institution page or collection is very similar to sharing a portfolio page or collection. The only difference is that you can allow new institution members to receive a copy of an institution page or collection immediately upon joining the institution.

Setting for copying an institution page for new institution members

Setting for copying an institution page for new institution members

  1. 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.
  2. Once you have put a check mark into that box, the line Copy for new institution members appears, and you can place a check mark into that box if you wish all new institution members to receive that page or collection automatically upon joining that institution.
  3. Click the Save button at the bottom of the page to save your changes.

8.5.11. Institution statistics

Administration → Institutions → Institution statistics

The type of statistics you have available for institutions are very similar to the site statistics. You can view statistics for each institution individually and for example use the CSV download options to

  • compare the institution statistics to the site statistics
  • compare institutions with each other

Note

All institution administrators have access to their institution(s)’ statistics at any time. If the site administrator set the staff statistics access correctly, institution staff will also be able to see the statistics for their institution(s).

8.5.11.1. Institution information

You have access to basic information about individual institutions. Choose the one you would like to see from the institution drop-down menu before proceeding.

Basic information about an institution

Basic information about an institution

You can view information about:

  1. Growth of your number of users and pages over time in a graph
  2. Institution created: Date when your institution went live
  3. Users: Number of
    • registered users, i.e. everybody who has an account
    • active users, i.e. users that have at least logged in once and have done something
  4. Pages: Number of pages and average pages per user with pages
  5. Disk usage: The amount of disk space your institution uses, i.e. the total amount of space occupied by files

8.5.11.2. Users

You can see basic information about an institution’s users to keep track of them.

Daily user statistics per institution

Daily user statistics per institution

On the Users tab of the institution statistics, you see information about

  1. the average user in this institution:
    • average number of friends with the name of the person with most friends
    • average number of pages with the author of the most pages
    • average amount of file quota used with the user who has used most
  2. daily user statistics with information about how many users
    • logged in
    • were created
    • existed in total on a specific day
  3. link to download the daily user statistics as CSV file

8.5.11.3. Pages

You can view statistics about an institution’s pages in the Pages tab.

Statistics about pages

Statistics about pages

The information that you can view is:

  1. The most frequently used blocks in portfolio pages.
  2. A graph shows the distribution of profile, group and portfolio pages.
  3. Most popular pages: The most popular pages are sorted in descending order with links to the pages and the owner.
  4. Export statistics in CSV format: Download the cumulative statistics about the pages and number of views as well as comments as CSV file.

8.5.11.4. Content

The Content tab in the institution statistics holds information about

  • artefacts
  • blocks
  • general site information
Statistics for the current week for all artefacts etc.

Statistics for the current week for all artefacts etc.

  1. Name: The statistics item itself, e.g. artefact, block or other general item on institution level. It is linked to the Historial data statistics for an overview of the changes over time.
  2. Modified: This column shows the number of updates to an artefact etc. during the current week.
  3. Total: This column shows the total number of instances of the statistics items.
  4. Export statistics in CSV format: Download the cumulative statistics about all the statistics shown for the week as CSV file.

Note

The number of total content statistics will vary because only when an artefact or block etc. was used, will the statistics be created for that type.

8.5.11.5. Historical data

The Historical data tab in the institution statistics holds historical data over time about a particular content item that you have clicked on in the Content tab. Changes are saved per default on a weekly basis. However, whenever you run the cron manually, a new statistics will be created as well. You can also download the statistics as CSV file.

Historical data for individual content items

Historical data for individual content items

  1. Historical statistics for field: Display of the artefact or other item that you are looking at.
  2. Date: Display of the date when the statistics were created.
  3. Modified: Display of the number of modifications from the previous date to the next one when the statistics were created.
  4. Total: Total number of instances of this statistical item at the time the statistics were run.
  5. Export statistics in CSV format: Download the cumulative statistics for this particular item as CSV file.

Note

When you click on the Historical data tab without choosing an item to look at in particular beforehand, the number of users are displayed as that is a statistics that is available on all sites.

8.5.12. Files

Administration → Institutions → Files

The files area in an institution holds all files that are uploaded by administrators as institution files. The uploading process works like the one in the personal files area.

Institution files area

Institution files area

8.5.13. Pending registrations

Administration → Institutions → Pending registrations

When you turn on Confirm registration for an institution in the institution settings, no user account in this institution is created without the administrator knowing it. If a user is rejected, no account is created. If the option Confirm registration is not turned on, a user account is created in the “No institution” institution but not in the actual institution.

Below follows the process for self-registration with Confirm registration turned on.

8.5.13.1. Self-register for an internal account

When users try to self-register for your institution, they must provide certain details.

Note

The fields for email, first and last name can appear in a different order if you have chosen the advanced spam protection settings.

User self-registration for an institution

User self-registration for an institution

  1. First name: Type your first name.
  2. Last name: Provide your last name.
  3. Email address: Provide your email address.
  4. Institution: Select the institution for which you want to register. There is an indicator whether the institution you wish to register for requires administrator approval.
  5. Registration reason: If administrator approval is required, you can provide a reason why you want to join.
  6. If the site administrator requires users who self-register to agree to the terms and conditions, the “Registration agreement” of the site, you must read through them below and then make your choice.
  7. Click the Register button.
  8. The administrators of that institution and the site administrator receive a notification about the pending registration. They then review pending registrations.
  9. You will receive an email which includes a link to confirm your email address. You must click that link within 24 hours. If you do not, you will have to start the registration process again from the beginning.

8.5.13.2. Self-register with a Persona account

The self-registration process with administrator approval also works for users who wish to use Persona. It needs to be set up as authentication method, and potential users go about in a very similar way.

User self-registration for an institution with a Persona account

User self-registration for an institution with a Persona account

Instead of clicking the link Register, users who have a Persona account can use that to register for an institution that allows for Persona authentication.

  1. Click the Persona button persona-button.
  2. Sign in to your Persona account.
  3. Follow the registration steps.

8.5.13.3. Review pending registrations

As administrator, you can view pending registrations for your institutions on the Pending registrations page in Administration → Institutions → Pending registrations.

Pending registration page

Pending registrations page

  1. Institution: Choose the institution for which you want to view the pending registrations.
  2. Pending registration: You see a list of all registration requests that include the names of the requesters and their email addresses.
  3. Registration reason: The reason for registration is displayed.
  4. Click the Approve button when you want to approve this registration request. You will have to confirm your approval on the next page. The person self-registering receives an email with a link to complete the registration process.
  5. Click the Deny button when you do not want this person to register for your institution and receive an account.

When you approve users, you can decide whether they should receive staff rights immediately. For example, this helps to give all teachers at a school staff access rights upon their self-registration.

Approve pending registrations

Approve pending registrations

  1. Institution staff: Place a check mark in this check box if the user shall have staff access rights.
  2. Click the Approve button when you want to approve this registration request.
  3. Click the Cancel button to abort the approval process.

When you deny a person access to your institution, you can also provide a reason.

Reason for denying institution membership for a self-registering user

Reason for denying institution membership for a self-registering user

  1. Denial reason: Write your reason for denying institution membership that might help the person to know why you do not want to give them access.
  2. Click the Deny button to send a notification to the person’s email address with the reason for the denial.
  3. Click the Cancel button to be taken back to the page with all pending registrations.

8.5.13.4. Complete self-registration

When users are accepted as members in an institution via this process, they must still complete the registration process. This is necessary to provide information in all required fields besides a password and a username.

Complete the self-registration for an institution

Complete the self-registration for an institution

  1. New username: Choose your new username. A default username is suggested, but you can provide a different one. If your suggested username is already taken, the system will let you know after you submit your information.
  2. New password: Choose a password for your account. This field is required.
  3. Confirm password: Re-type the new password. This field is required.
  4. Click the Submit button to complete your registration. You will be taken to your Dashboard.

Table Of Contents

Previous topic

8.4. Groups

Next topic

8.6. Extensions

Languages

Some of these may be incomplete.