9.3. Users

Administration → Users

In the Users menu of the administration site administrators can:

  • search for users
  • change settings for individual users
  • suspend and delete users
  • make users site staff or administrators
  • check the administrator notification settings
  • add and update users manually or by CSV
  • view reports

In the Users menu of the administration institution administrators can:

  • search for users
  • change settings for individual users
  • suspend and delete users
  • check the administrator notification settings for their institution’s administrators
  • add and update users manually or by CSV
  • view reports

9.3.2. User account settings

Administration → Users → User search → Click on a username

On the Account settings page of a user in the administration area, you can perform a number of actions to manage the user’s account. However, you cannot change personal information about this user, e.g. name or email, from this page. This can only be done in the Content area of the user’s account or via the Add users by CSV page.

User account settings

Overview of the user account settings page

  1. Log in as this user.
  2. Change site account settings.
  3. Change institution settings.
  4. Suspend this user.
  5. Delete this user.

9.3.2.1. Log in as

As administrator you have the power to log in as any user that you manage and masquerade as them.

Note

Site administrator can log in as any user while institution administrators can only perform this action for users who are members of their institution(s).

It is a great function for troubleshooting a user account because you see everything as the user would without having to know the password.

Warning

This function can be misused by administrators because you can make changes to the user’s portfolio and artefacts as well as participate in groups while logged in as that user. Users should be aware of this function and that an administrator can enter their account.

Sites should have clear policies around the use of this function so that the privacy of users and their portfolios and collaborative work is protected. Therefore, there should also not be many users within an institution who have administrator rights.

Log in as another user

Log in as another user

  1. Click on the user’s name to go to this user’s profile page. You can then click the Log in as ... link to become that user.
  2. Click the Log in as button to become that user. You see a red bar at the top of the browser window telling you that you are masquerading as that user.
Stop masquerading as another user

Stop masquerading as another user

When you want to return to your own account again, click the Become [your name] again link at the top of the browser window.

When the site administrator enabled the logging of all or just masquerading events, administrators may be required to provide a reason for the masquerading and a notification about this may be sent to the users.

Provide a reason for masquerading as another user

Provide a reason for masquerading as another user

  1. Write why you are masquerading as this user. This reason may be sent to the user if the site administrator demands that.
  2. Click the Continue button to log in as that user.
  3. If the site administrator decided to have users notified of the masquerading, you would see the screen notice “The user has been notified of this masquerading session.”

When the site administrator decided to send notifications to users when an administrator logs into their account, the users receive this notification in their inbox. Depending on their notification settings, it can also be delivered via email.

Notification a user receives when an administrator masquerades

Notification a user receives when an administrator masquerades

  1. Activity type: The masquerading notification is a system message. If you receive a lot of notifications, you can filter for just them.
  2. The system message “An administrator logged in as you” contains the name of the administrator and the time when the administrator started masquerading. If the site administrator requires a reason to be sent for the masquerading, it is displayed as well.
  3. The name of the administrator who logged in as you is linked to the profile page for you to easily contact that administrator.

9.3.2.2. Change site account settings

You can view and change a number of settings for a user’s account.

Note

Depending on the authentication method that is associated with this user, you may not be able to edit all settings.

Site account settings of a user

Site account settings of a user

  1. Change username: Give the user a different username. This field is not available when the account is managed by an external authentication method.

  2. Reset password: Change the password for this user account. This field is not available when the account is managed by an external authentication method.

  3. Force password change on next login: Check this box if the user shall change the password upon the next login. This field is not available when the account is managed by an external authentication method.

  4. Site staff: Check this box if the user shall become a staff member for the entire site.

  5. Site administrator: Check this box if the user shall have full administrative rights for the entire site.

  6. Disable email: Check this box to disable the sending of emails for this user. If email is disabled, notifications and messages can only be viewed in the internal inbox. You can set up your Mahara site so that emails are disabled automatically if they are bounced back.

    Warning

    When the email address is disabled, users cannot reset their passwords themselves as no email can be sent.

  7. Account expires: Tick the checkbox if you want to specify an account expiration date. Once done, the date picker is activated for you to enter a date. Choose the date on which the user’s login will be disabled automatically. 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 account settings of the site configuration.

  8. File quota: Change the storage allowance for a user’s personal files area. Institution administrators may not be able to update the quota if the site administrator disallowed that. The default value as set in the files configuration in the plugin administration.

  9. Quota used: You can see how much this user has already used of their allocated quota.

  10. Spammer probation status: This setting controls whether the user is considered to be on probation as a possible spammer.

    Note

    This feature is only available on sites that have the 2 following values in their config.php file:

    • $cfg->probationenabled = true;: This setting decides that users can get a probation status.
    • $cfg->probationstartingpoints = 2;: This setting determines how many probation points a newly self-registered user has per default.

    Newly self-registered users - no matter whether the institution requires explicit administrator confirmation or not - start out with a certain number of “probation points” on their account. While they have any probation points, they are considered a probationary user and cannot create public pages in their portfolio or post links or images to potentially public content such as comments, wall posts or forum posts.

    Each time a probationary user makes a post in a forum, and the post is replied to by a non-probationary user, the probationary user loses one probation point. When the number of points reaches zero, they are no longer on probation.

    Probation points have no effect on users who have staff or administrator status.

  11. Authentication method: Choose the authentication method for this user. A site administrator can set up the authentication methods in the institution administration. Depending on the authentication method that you have chosen, you may have to provide a remote username to allow the user to log in.

    Note

    The field Username for external authentication is only displayed if an authentication method is chosen that requires a remote username. This allows administrators to see if a remote username has been supplied or not.

  12. Tags: A user can be tagged by an administrator. The tag of the institution to which the user belonged prior to joining a new institution is not displayed to avoid its deletion.

  13. Click the Save changes button when you are done editing the settings.

9.3.2.3. Change institution settings

You can view and change settings regarding a user’s membership in institutions. Depending on the site settings for institutions, a user may be added to more than one institution.

Institution settings for a user

Institution settings for a user

  1. Institution: Choose the institution to which you want to add this user from the drop-down menu.
  2. Click the Add user to institution button to make this user a member of this institution.
  3. Membership expires: Tick the checkbox if you want to specify the date when the user will be removed from this institution automatically. Once done, the date picker is activated for you to enter a date. Choose the date on which the user’s login will be disabled automatically. 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 institution membership expiry date for all users in your institution in the settings for your institution.
  4. ID number: Provide an optional identifier for this user in this institution. This field is not editable by the user.
  5. Institution staff: Check this box if you want to give this user staff rights in this institution. This will allow them to create controlled groups for example.
  6. Institution admin: Check this box if you want to make this user an administrator of this institution. This will allow them to manage all users in this institution for example.
  7. Click the Update button to save your changes.
  8. Click the Remove user from this institution button to disassociate this user from this institution. The user’s account will not be deleted. The user will only not be associated with this institution anymore.

9.3.2.4. Suspend user

Suspend a user if they do not follow the terms and conditions of the site and behave inappropriately. Suspended users cannot log in, but all their content is still available.

Suspend a user

Suspend a user

  1. Reason: Provide a reason for your suspension. This is particularly useful when you are not the only administrator and / or need to remember after some time why you suspended this user.
  2. Click the Suspend user button to disallow the user from logging in.
Suspension notice on the user account settings page

Suspension notice on the user account settings page

You can unsuspend a user from this page or together with other users on the Bulk actions page.

Suspended user tries to log in

Suspended user tries to log in and gets suspension message

When a user has been suspended, the suspension message appears on the user’s account settings page stating the reason and the date for the suspension and giving the administrators the possibility to unsuspend the user by clicking the Unsuspend user button.

When the user tries to log in, they will see the suspension message and the reason. They can then contact an administrator via the “Contact us” form for further action.

9.3.2.5. Delete user

Users can delete their own accounts in their account settings if self-registration is allowed to by their institution. Administrators can also delete user accounts at any time.

Delete a user account

Delete a user account

Click the Delete user button to delete this user account permanently. This action cannot be undone. As this is a permanent action, you see a confirmation pop-up window that you will have to acknowledge.

Warning

When you delete a user account, all personal data is wiped from the system. This applies to everything that is in a user’s Content and Portfolio area. This action cannot be undone. The user’s contributions in groups, e.g. forum messages, uploaded files and pages created in a group, are still available, but are made anonymous by changing the name to “Deleted user” as author where an author is shown.

Note

If an account was deleted by accident - either by a user or by an administrator - swift action may result in recovery of (most of) the data from a backup file. This requires access to the server’s backups and the backend of Mahara. More information is available on the wiki under Restoring a deleted user.

9.3.3. Suspended and expired users

Administration → Users → Suspended and expired users

A list of all suspended and expired users is available in the sub-menu Suspended and expired users. Here you can unsuspend / reactivate or delete them.

Note

Site administrators see all users whereas institution administrators only see users who are members of their institution(s).

List of all suspended and expired users

List of all suspended or expired users

  1. Show: Select whether you wish to see suspended or expired users.
  2. Select the user(s) for which you want to perform the same action.
  3. Click the Unsuspend users button to reinstate the accounts for all selected users.
  4. Click the Delete users button to delete all selected users in bulk. This action cannot be undone and all personal information of these users will be deleted (see delete user).
  5. Click the Reactivate expired users button if you want to allow these users access to their accounts again.

Warning

When you delete a user account, all personal data is wiped from the system. This applies to everything that is in a user’s Content and Portfolio area. This action cannot be undone. The user’s contributions in groups, e.g. forum messages, uploaded files and pages created in a group, are still available, but are made anonymous by changing the name to “Deleted user” as author where an author is shown.

9.3.4. Site staff

Administration → Users → Site staff

Note

Site staff is only accessible by site administrators.

On this page you can choose which users receive site staff rights. Potential staff members - any user on the site - are listed on the left while existing site staff members are listed on the right.

Site staff users

Give site staff rights

  1. Potential staff: Select the users you wish to make site staff. You can select multiple users at once using Ctrl and Shift click.
  2. Search: If you have too many users on your site and you cannot see / find the users you want, you can search for them here.
  3. Add the potential staff members to the right-hand side - Current staff - by clicking the right-arrow button right-arrow.
  4. Current staff: If you want to remove an existing or accidentally added site staff member, you can remove the user from the list on the right-hand side by clicking on the user.
  5. Then click the left-arrow button left-arrow, and the user is removed from the list.
  6. When you have chosen all members you wish to make site staff, click the Submit button.

Note

You can also double-click a name and it will be moved to the other side.

9.3.5. Site administrators

Administration → Users → Site administrators

Note

Site administrators is only accessible by site administrators.

Site administrators have powerful rights. They can make far-reaching changes and also log in as other users. Be careful whom you give these rights. One site administrator is needed for each site. The total number of site administrators should be kept small.

Site admins

Give site admin rights

  1. Potential administrators: Select the users you wish to make site administrators. You can select multiple users at once using Ctrl and Shift click.
  2. Search: If you have too many users on your site and you cannot see / find the users you want, you can search for them here.
  3. Add the potential site admin to the right-hand side - Current administrators - by clicking the right-arrow button right-arrow.
  4. Current administrators: If you want to remove an existing or accidentally added site administrator, you can remove the user from the list on the right-hand side by clicking on the user.
  5. Then click the left-arrow button left-arrow, and the user is removed from the list.
  6. When you have chosen all members you wish to make site administrators, click the Submit button.

Note

You can also double-click a name and it will be moved to the other side.

9.3.6. new in Mahara 1.10 Export queue

Administration → Users → Export queue

This feature is experimental.

The export queue is available for the following exports:

  • When group administrators or tutors release portfolios in groups that allow the archiving of submitted pages, these submissions will be placed into the export queue and only released once the export completed successfully.
  • If the site administrator enabled the feature to queue Leap2A exports, Leap2A exports that users initiate via Portfolio → Export are also queued, and once completed, the users receive a notification.

See also

The export queue requires that cron runs.

Export queue for Leap2A exports

Export queue for Leap2A exports

  1. User search: Type the user’s name if you only want to see results for a particular user in the queue.

  2. Institution: Select the institution if you only want to see the queued portfolios for a particular institution. If you are an institution administrator for only one institution, you only see results for your institution.

  3. Click the Go button to initiate the filtering.

  4. In the results table you see the profile picture of the user.

  5. First name: Displays the first name of the user. This is the default column for sorting results.

    Note

    Click on the other headings of the table that are links to sort the table differently.

  6. Last name: Displays the last name of the user.

  7. Display name: Shows the display name of the user.

  8. Username: Clicking on the username, you are taken to the user’s administration settings page instead of their profile page as you would with the other names.

  9. Export content: Brief description of what is being exported.

  10. Status: Displays the status of the export. Only pending and failed exports are shown.

  11. Export: Tick the checkboxes in this column if you wish to re-run an export that has failed. You can select all checkboxes by clicking the All link or remove all checkboxes by clicking the None link.

  12. Click the Archive button to export all selected failed exports.

  13. Delete: Tick the checkboxes in this column if you wish to delete any pending or failed exports. You can select all checkboxes by clicking the All link or remove all checkboxes by clicking the None link.

  14. Click the Delete button to delete all selected exports.

9.3.7. Add user

Administration → Users → Add user

You can add users to your site (site administrator) or your institution (institution administrator) by creating accounts for them manually one by one.

Add a user manually

Add a user manually

  1. Click the Create new user from scratch radio button if you want to create an empty account. Provide the first name, last name and email address for this user.
  2. Click the Upload Leap2A file radio button if you want to import a user from another Mahara instance or a system that supports the Leap2A standard. Such a user could have exported their portfolio from another Mahara instance.
  3. Username: Give the new user a username. It may contain letters, numbers and most common symbols. It must be from 3 to 236 characters in length. Spaces are not allowed.
  4. Password: Choose a password for the account. The password must be at least six characters long.
  5. Site staff: Check this box if the new user should have site staff rights. Only site administrators see this option.
  6. Site administrator: Check this box if the new user should have site administrator rights. Only site administrators see this option.
  7. Institution: Choose the institution of which the user should be a member.
  8. File quota: Review the allocated file quota. You may change it here for this user if you are allowed to.
  9. Institution administrator: Check this box if the new user should have institution administrator rights in the chosen institution.
  10. General account options: Expand this menu to see default account options that you may choose to change while creating this user. These are the general account options a user can change on the Settings page.
  11. Click the Create user button.
  12. The user will receive an email with the account details.

Note

You can only define the default account settings for a user account, but not force the user to keep them forever. You could only do that by customising the system on the code level.

9.3.8. Add and update users by CSV

Administration → Users → Add users by CSV

You can use this function to upload new users in bulk via a CSV file (comma-separated file) and to update existing users. The first row of your CSV file should specify the format of your data. For example, it should look like this:

username,password,email,firstname,lastname,studentid

For new users, this row must include:

  • username
  • password
  • email
  • firstname
  • lastname

If you want to update existing users, you do not need to set a password and can leave that field off entirely.

Note

You can mix new and existing accounts in your CSV file. When you add a new user, the password field must be present. If you do not wish the password to be changed for existing accounts, leave that field empty for these accounts.

new in Mahara 1.10 If your site or institution has locked fields or fields that are mandatory, then you do not have to include them as fields in your CSV upload.

Here is the full list of additional fields that you can add in your CSV file upload.

  • address - Street address
  • blogaddress - URL to the blog
  • businessnumber - Work phone number
  • city - City
  • country - Country
  • faxnumber - Fax number
  • homenumber - Home phone number
  • industry - Industry is displayed in the profile
  • introduction - Introduction is displayed in the profile
  • mobilenumber - Mobile phone number
  • occupation - Occupation is displayed in the profile
  • officialwebsite - Official website
  • personalwebsite - Personal website
  • preferredname - Display name
  • remoteuser - Remote username for external authentication
  • studentid - Student ID is displayed in the profile
  • town - Town

Your CSV file could look for example like the following:

username,email,firstname,lastname,studentid,preferredname,remoteuser, password
"percy","percy@pearle.net","Percy","Pearle","","","percy.pearle","mahara1"
"petra","petra@petterson.net","Petra","Petterson","","","petra.petterson","mahara1"
"polly","polly@potter.net","Polly","Potter","","","polly.potter","mahara1"
"admin","admin@mahara.school","Admin","User","","","","mahara1"
"jamesj","james@jetts.com","James","Jetts","","","","mahara1"

When you have created your CSV file, you are ready to upload it.

Add users by CSV file

Add users by CSV file

  1. Institution: Choose the institution and the authentication method for the user accounts that you upload and / or change.
  2. File quota: If you wish, you can set a different file quota for all accounts in the CSV file. Institution administrators can only do so if the site administrator allowed it.
  3. CVS file: You must upload a CSV file by clicking the Browse button and then selecting it from the files area on your computer.
  4. Force password change: If you select this option, users need to change their password before they can log in for the first time.
  5. Email users about their account: If you select this option, users will receive an email with their account information. This is in particular good for internal accounts. For user accounts that are managed for example by Moodle or through LDAP, you do not have to select this option because the users should already know their login information.
  6. Update users: Select this option if your CSV file contains changes for existing users.
  7. General account options: Expand this menu to see default account options that you may choose to change while creating or updating users. These are the general account options a user can change on the Settings page.
  8. Click the Add users by CSV button to upload and / or change users.

Note

Depending on your server settings and / or the size of your installation, you may not be able to upload all user accounts at once. You may wish to upload them in bunches of 100 instead.

9.3.9. Change the authentication method and remote username in bulk

After you have successfully invited or added new members into your institution, you can change their authentication method. That can be useful if the authentication method differs from the one in the previous institution and you want to link the new accounts to a remote username using:

  • LDAP directory
  • Moodle accounts via MNet
  • Single sign-on through an IdP provider

Note

The change in the authentication method for existing accounts should be done before users try to log in with their new credentials to avoid the creation of a second account for these users.

You can change the authentication method for multiple users at once to save you time manually updating each user. Changing the authentication method usually also entails changing the remote username (a.k.a. username for external authentication). Therefore, these two are dealt with together to describe the work flow better.

Find users in an institution to change their remote username

Find users in an institution to change their remote username

  1. Go to Administration → Users → User search.
  2. Filter for users by specific characteristics, e.g. if you only wish to display users who have not logged in yet.
  3. From the drop-down menu choose the institution in which the members are whose authentication method and remote username you want to change / add.
  4. Click the Go button to limit your results to these institution members.
  5. Change the Results per page if you wish to see more than 10 users per page.
  6. Select the users whose authentication method and remote username you want to change by either putting a check mark in the checkboxes or clicking on All to select all users on that page.
  7. Click the Get reports button to proceed to the next step. You are taken to the User reports page.
User reports page

User reports page

Update the CSV file

Update the CSV file with remote username and password

Update user accounts in bulk

Update user accounts in bulk

  1. Export users in CSV format: Click the Download link so that you get a CSV file which contains all necessary information for you to change the users’ remote username in bulk. This is necessary if their internal Mahara username is not the same as the one they use to authenticate on your system that is linked to Mahara or if they already have a remote username that would be incorrect for your institution.

  2. Open the CSV file in your preferred spreadsheet software. In the column remoteuser, add or change the username that your users have when authenticating in your regular system that you have connected to Mahara. You may also change other fields, e.g. their name, email address etc. If you want to add a new user directly in this CSV file, you can do so as well.

    Note

    You must provide a password for this new user. All other users do not need to have a value in the password field. If you only want to update existing users, you can leave the password field entirely off.

  3. Go to Administration → Users → Add users by CSV.

  4. Institution: Choose the correct institution and authentication method for which you want to update your users. This allows you to switch all users in the CSV file from one authentication method to another.

  5. CSV file: Choose the CSV file from your computer that you had updated.

  6. Update users: Put a check mark here because you want to update existing user accounts.

  7. General account options: You can make changes to the default account options for all the users, e.g. give them multiple journals by default, change their interface language etc.

  8. Click the Add users by CSV button to start the user update. This process may take a little while depending on how many users you are changing.

  9. You receive a report on the page upon the successful completion of the upgrade. If the upgrade fails, error messages help you to resolve the problem. No users are updated until all errors are resolved.

Note

If you intend to update more than 100 users at the same time, you may run into problems, and the server may reject your CSV file as the update process is a very memory intense one. If that is the case, you would have to split your CSV file into smaller ones with fewer users in them.

You can check that the accounts had their remote usernames added:

  1. Go to Administration → Users → User search.
  2. Select the institution in which the members are whom you want to check.
  3. Click the Go button to limit your user results to this institution.
  4. Select the users for whom you want to check the remote usernames.
  5. Click the Get reports button to proceed to the next step. You are taken to the User reports page.
  6. You see the remote username in the last column.

See also

If you only want to change the authentication method of certain users but do not have to worry about a remote username or updating any other information, you can change the authentication method directly on the bulk actions screen.