.. include:: /shortcuts.rstext .. index:: pair: Administration; People single: Site administrator; People management single: Institution administrator; People management .. _users: People ---------------- *Administration menu → People* In the *People* menu of the administration **site administrators** can: * search for people * change settings for individual people * suspend and delete accounts * make people site staff or administrators * check the administrator notification settings * add and update accounts manually or by CSV * view reports In the *People* menu of the administration **institution administrators** can: * search for people * change settings for individual people * suspend and delete accounts * check the administrator notification settings for their institution's administrators * add and update accounts manually or by CSV * view reports .. index:: pair: Administration; People search single: Account bulk actions single: Exact search single: Link profile picture and name to the profile in 'People search' .. _user_search: People search ~~~~~~~~~~~~~~~ *Administration menu → People → People search* .. note:: Site administrators can search for anybody on the entire site while institution administrators can only search among the members of their institution(s). Standard people search ^^^^^^^^^^^^^^^^^^^^^^ .. figure:: /images/administration/user_search.* :alt: People search People search #. **Search**: Enter your search term. The default text in the field shows you in which institution context you perform your search. Type the name, display name, username or email address or any partial thereof you wish to search for in the search field. :ref:`If you turned on the exact search `, you need to provide the correct name or email address and not a partial one. .. note:: :index:`Both ` primary and secondary email addresses are searchable. #. Use the drop-down arrow to choose a single institution in which to search for a person. #. Click the *Search* button to start your search. #. Click the :ref:`'Advanced options' ` link to make filtering options visible. #. **First name**: The first name links through to the person's profile page. #. Click the arrow to change the sort order of the column. All columns but the institution one are sortable. #. **Last name**: The last name links through to the person's profile page. #. **Display name**: The display name is shown. #. **Username**: This is the internal Mahara username. Click the username to go to this person's :ref:`account settings page `. #. **Emails**: The primary email address as well as :index:`all secondary email addresses ` are displayed. .. note:: Secondary email addresses are displayed in parentheses. #. **Institution**: The institution or institutions that a person belongs to are displayed. #. **Authentication**: The authentication method for this account is shown. #. **Last login**: The date and time of the last login is visible. #. Click the *All* button to select all accounts and click the *None* button to deselect all accounts. #. You can also tick the checkbox for an individual to select them. #. Accounts that are suspended or expired have the *Inactive account* icon |inactive user| next to their username. #. The number of search results are available. If there are more than ten accounts in the search results, you have a pager available to go to more results. #. Click the *Edit selected accounts* button to perform the :ref:`bulk actions ` to * suspend people * delete accounts * change the authentication method of accounts #. Click the *Get reports for selected accounts* button to * view :ref:`account reports ` * download account information for further actions .. index:: single: Filter by login date in 'People search' .. _user_search_advanced_options: Advanced search options ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You can combine any search and filter options. However, if you use too many, you may not yield any results. .. figure:: /images/administration/user_search_advanced.* :alt: Advanced search options Advanced search options #. **Search**: You see the institution context in which your search is performed. #. Use the drop-down arrow to choose a single institution in which to search for your a person. #. Click the *Search* button to filter results for this institution only. #. Click the :ref:`'Advanced options' ` link to make additional filtering options visible. #. **First name**: Filter the people you wish to display by the initial of their first name. Click the letter of the alphabet to narrow your search. #. **Last name**: Filter the people you wish to display by the initial of their last name. Click the letter of the alphabet to narrow your search. #. **Last login**: You have several options: * **Anybody**: Display anybody who fits any other search / filter criteria. * **People have logged in**: Display everybody who has logged in at least once. * **People have never logged in**: Display everybody who has never logged in. * **People have logged in since**: Display everybody who has logged in since a specified date and time. You can choose the date in a date field that is displayed once this option is chosen. * **People have not logged in since**: Display everybody who has not logged in since a specified date and time. You can choose the date in a date field that is displayed once this option is chosen. #. **Duplicate email addresses**: :index:`Tick this checkbox ` if you only want to display people whose email address is in the system twice so you can deal with them. .. note:: Normally, duplicate email addresses are not possible, but if a person imports a Leap2A file or if an external authentication method is used, duplicates can happen. #. **People with objectionable content**: Filter your results by those people who have objectionable content in one or more of their portfolios. .. index:: pair: Administration; Account bulk actions .. _bulk_actions: Account bulk actions ^^^^^^^^^^^^^^^^^^^^^^^^^^^ You can perform a number of bulk actions for accounts on the *Bulk actions* page: * Suspend them. * Change their authentication method. * Set spam probation points. * Delete them. .. index:: single: Account bulk actions; Suspend accounts .. _suspend_users: Suspend accounts __________________________ You can suspend accounts in bulk disallowing them to log into their accounts. Their portfolios will not be available any more to others. .. figure:: /images/administration/user_bulk_actions_suspend.* :alt: Account bulk actions: Suspend accounts Account bulk actions: Suspend accounts #. On the :ref:`People search ` page, select the accounts that you wish to suspend and click the *Edit* button. #. Make sure that you are on the *Suspend* tab. #. **Selected accounts**: Review the accounts you have selected. #. **Reason for suspension**: Provide a reason for suspending the accounts listed on this page. #. Click the *Suspend* button to prevent these account holders from accessing their accounts. .. note:: If you made a mistake or want to remove a temporary suspension, you can do so under :ref:`Suspended and expired accounts `. .. index:: single: Account bulk actions; Change authentication method .. _change_auth_method: Change authentication method _______________________________ You can change the authentication method for many accounts at once. .. figure:: /images/administration/user_bulk_actions_change_auth.* :alt: Account bulk actions: Change authentication method Account bulk actions: Change authentication method #. On the :ref:`People search ` page, select the accounts for whom you wish to change the authentication method and click the *Edit* button. #. Make sure that you are on the *Change authentication method* tab. #. **Selected accounts**: Review the accounts you have selected. #. Select the new authentication method from the drop-down menu. That includes choosing the correct institution and associated authentication method. #. Click the *Change authentication method* button to make the change. .. note:: You need to change or add a remote username for some authentication methods. You will need to do that in a separate step. For information on that, please see the instructions for :ref:`changing the authentication method and remote username `. .. index:: single: Account bulk actions; Set spam probation .. _set_spam_probation: Set spam probation _______________________________ You can change the spam probation points for many account holders at once. .. note:: This feature is only available on sites that have :ref:`spam probation ` turned on. Newly self-registered persons - 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 person 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 person makes a post in a forum, and the post is replied to by a non-probationary person, the probationary person loses one probation point. When the number of points reaches zero, they are no longer on probation. Probation points have no effect on persons who have staff or administrator status. .. figure:: /images/administration/user_bulk_actions_spam_probation.* :alt: Account bulk actions: Set spam probation Account bulk actions: Set spam probation #. On the :ref:`People search ` page, select the accounts for whom you wish to set probation points and click the *Edit* button. #. Make sure that you are on the *Set spam probation* tab. #. **Selected accounts**: Review the accounts you have selected. #. Select the number of probation points from the drop-down menu that you wish to give the selected accounts. #. Click the *Set* button to make the change. .. index:: single: Account bulk actions; Delete accounts .. _delete_users: Delete accounts _______________________________ You can delete many accounts at once. .. warning:: When you delete an account, **all personal data is wiped from the system**. This action cannot be undone. The person'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 account' as author where an author is shown. .. figure:: /images/administration/user_bulk_actions_delete_users.* :alt: Account bulk actions: Delete accounts Account bulk actions: Delete accounts #. On the :ref:`People search ` page, select the accounts that you wish to delete and click the *Edit* button. #. Make sure that you are on the *Delete accounts* tab. #. **Selected accounts**: Review the accounts you have selected. #. Click the *Delete* button. The accounts will be deleted along with their data. .. note:: Forum posts and comments that people have written or portfolio pages in which they were involved in groups are not deleted. However, their name is being removed. .. index:: pair: Administration; Account settings .. _user_account_settings: Account settings ~~~~~~~~~~~~~~~~~~~~~~~~ *Administration menu → People → People search →* Click on a username On the *Account settings* page of a person in the administration area, you can perform a number of actions to manage the account. However, you cannot change personal information about this person, e.g. name or email, from this page. This can only be done in the *Profile* area of the account or via the *Add people by CSV* page. .. figure:: /images/administration/user_account_settings.* :alt: Account settings Overview of the account settings page #. :ref:`Log in as this person `. #. :ref:`Suspend ` or :ref:`delete ` this person. #. :ref:`Change site account settings `. #. :ref:`Change institution settings `. .. index:: see: Masquerading; Log in as pair: Administration; Log in as single: Masquerading: Provide reason single: Masquerading: Masquerading notification .. _login_as: Log in as ^^^^^^^^^^^^^^ As administrator you have the power to log in as any person that you manage and masquerade as them. .. note:: Site administrator can log in as anybody while institution administrators can only perform this action for members of their institution(s). It is a great function for troubleshooting an account because you see everything as the person would without having to know the password. .. warning:: This function can be misused by administrators because you can make changes to the person's portfolio and artefacts as well as participate in groups while logged in as them. People 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 people and their portfolios and collaborative work is protected. Therefore, there should also not be many people within an institution who have administrator rights. .. figure:: /images/administration/login_as.* :alt: Log in as another person Log in as another person #. Click on the person's name to go to their profile page. You can then click the *Log in as ...* link to become that person from that screen. #. Click the *Log in as* link to become that person. You see a warning bar at the top of the browser window telling you that you are masquerading as that person. .. figure:: /images/administration/masquerading.* :alt: Stop masquerading as another person Stop masquerading as another person 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 :ref:`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 account holder. .. figure:: /images/administration/masquerading_reason.* :alt: Provide a reason for masquerading as another person Provide a reason for masquerading as another person #. Write why you are masquerading as this person. This reason may be sent to the person if the site administrator demands that. #. Click the *Continue* button to log in as that person. #. If the site administrator decided to have account holders notified of the masquerading, you would see the screen notice 'The person has been notified of this masquerading session.' When the site administrator decided to :ref:`send notifications to people when an administrator logs into their account `, the peoples receive this notification in their inbox. Depending on their :ref:`notification settings `, it can also be delivered via email. .. figure:: /images/administration/masquerading_notification.* :alt: Notification a person receives when an administrator masquerades Notification a person receives when an administrator masquerades #. **Activity type**: The masquerading notification is a system message. If you receive a lot of notifications, you can filter for just them. #. Click the bar to see the full text of the message. #. 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. #. The name of the administrator who logged in as you is linked to the profile page for you to find out more about them or send them a message. .. index:: pair: Administration; Suspend a person .. _suspend_user: Suspend a person ^^^^^^^^^^^^^^^^^^ Suspend a person if they do not follow the terms and conditions of the site and behave inappropriately. Suspended people cannot log in, but all their content is still available. .. figure:: /images/administration/suspend.* :alt: Suspend a person Suspend a person #. Click the link *Suspend or delete this person*. A pop-up windows becomes visible. #. **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 person. #. Click the *Suspend person* button to disallow them from logging in. .. figure:: /images/administration/suspension_notice.* :alt: Suspension notice on the person's account settings page Suspension notice on the person's account settings page When a person has been suspended, the suspension message appears on their account settings page stating the reason and the date for the suspension and giving the administrators the possibility to unsuspend the person by clicking the *Unsuspend person* button. You can unsuspend a person from this page or together with others on the :ref:`Bulk actions page `. .. figure:: /images/administration/suspension_reason.* :alt: Suspended person tries to log in Suspended person tries to log in and gets suspension message When the person 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. .. index:: pair: Administration; Delete account .. _delete_user: Delete account ^^^^^^^^^^^^^^^^^^^^ Peoples can delete their own accounts in their :ref:`account settings ` if self-registration is allowed by their institution. Administrators can also delete accounts at any time. .. figure:: /images/administration/delete_account.* :alt: Delete an account Delete an account #. Click the link *Suspend or delete this person*. A pop-up windows becomes visible. #. Click the *Delete account* button to delete this 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 an account, **all personal data is wiped from the system**. This action cannot be undone. The person'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 account' as author where an author is shown. .. note:: If an account was deleted by accident - either by a person themselves 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 account `_. .. index:: single: Display used file quota in admin area single: User tags single: Used account quota single: Disable bounced email addresses automatically single: Spam protection; Probation status for new self-registered people .. _site_account_settings: Change site account settings ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You can view and change a number of settings for an account. .. note:: Depending on the authentication method that is associated with this account, you may not be able to edit all settings. .. figure:: /images/administration/site_account_settings.* :alt: Site account settings of a person Site account settings of a person #. **Change username**: Give the person a different username. This field is not available when the account is managed by an external authentication method. #. **Reset password**: Change the password for this account. This field is not available when the account is managed by an external authentication method. #. The password strength indicator gives you an idea of how strong your password is in relation to the :ref:`password policy `. #. **Force password change on next login**: Change the switch to 'Yes' if the person shall change the password upon the next login. This option is not available when the account is managed by an external authentication method. #. **Primary email**: Displayed is the primary email address for this person. This email address is used for any notifications. You can change that email address here. .. note:: The previously used email address stays in the account as secondary email address until the person deletes it. #. **Account roles**: All roles possible to associate with an account can be displayed here either for the site or further down in the individual institution(s) in which the person is a member. The default built-in roles are: * **Site staff**: Change the switch to 'Yes' if the person shall become a staff member for the entire site. * **Site administrator**: Change the switch to 'Yes' if the person shall have full administrative rights for the entire site. .. seealso:: New account roles can be set via SAML for SSO accounts. #. **Disable email**: Change the switch to 'Yes' to disable the sending of emails for this account. 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, account holders cannot reset their passwords themselves as no email can be sent. #. **Last login**: The date and time when the person logged into Mahara for the last time is displayed. #. **Account expires**: Enter a date via the calendar if you want to set an expiry date. .. note:: The default setting is that the date is not specified. You can set an automatic account expiry date for everyone in the :ref:`account settings of the site configuration `. #. **File quota**: Change the storage allowance for a person'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 :ref:`files configuration ` in the plugin administration. #. **Quota used**: You can see how much this person has already used of their allocated quota. #. **Spammer probation status**: :index:`This setting controls ` whether the person is considered to be on probation as a possible spammer. See the :ref:`spam probation levels ` for more information. .. note:: This feature is only available on sites that have :ref:`spam probation ` turned on. #. **Authentication method**: Choose the authentication method for this person. A site administrator can set up the authentication methods in the :ref:`institution administration `. Depending on the authentication method that you have chosen, you may have to provide a *remote username* to allow the person to log in. .. note:: You only see the authentication methods that you are allowed to assign to the person based on their institution membership. :index:`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. #. **Tags**: A person can be tagged by an administrator. The :ref:`tag of the institution to which the person belonged prior to joining a new institution ` is not displayed to avoid its deletion. #. Click the *Save changes* button when you are done editing the settings. .. index:: pair: Administration; Change institution settings for a person .. _user_institution_settings: Change institution settings ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You can view and change settings regarding a person's membership in institutions. Depending on the :ref:`site settings for institutions `, a person may be added to more than one institution. .. figure:: /images/administration/user_institution_settings.* :alt: Institution settings for a person Institution settings for a person #. **Institution**: Choose the institution to which you want to add this person from the drop-down menu. .. note:: Only site administrators or institution administrators who have administrator permissions in more than one institution see this option. #. Click the *Add to institution* button to make this person a member of this institution. #. Click the *Institution settings* bar to see more details about the person in this institution. The bar shows the name of the institution. #. **Membership expires**: Click into the field to view the date picker and choose when you want to remove this person from this institution. They are removed from your institution on that date, but retain their account and can still log in. .. note:: The default setting is that the date is not specified. You can set an automatic institution membership expiry date for all members in your institution in the :ref:`settings for your institution `. #. **ID number**: Provide an optional identifier for this person in this institution. This field is not editable by the institution member. #. **Account roles**: While account roles have existed in Mahara for a long time, it is now possible to extend them. All account roles a person has in an institution can be set here. The default built-in roles are: * **Institution staff**: Change the switch to 'Yes' if you want to give this member staff rights in this institution. This will allow the them to create controlled groups for example. * **Institution administrator**: Change the switch to 'Yes' if you want to make this member an administrator of this institution. #. Click the *Update* button to save your changes. #. Click the *Remove from this institution* button to disassociate this person from this institution. The account will not be deleted. The person will only not be associated with this institution any more. .. index:: pair: Administration; Suspended and expired accounts single: View and reactivate expired accounts in bulk .. _suspended_users: Suspended and expired accounts ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ *Administration menu → People → Suspended and expired accounts* A list of all suspended and expired accounts is available in the sub-menu *Suspended and expired accounts*. Here you can unsuspend / reactivate or delete them. .. note:: Site administrators see all people whereas institution administrators only see people who are members of their institution(s). Suspended accounts ^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. figure:: /images/administration/suspended_users.* :alt: List of all suspended accounts List of all suspended accounts #. **Show**: Select to view **suspended** accounts. #. Basic details about each account are displayed to ensure that you are looking at the correct ones. That includes displaying the suspension reason. #. Select the account(s) for which you want to perform the same action. #. Click the *All* button if you want to select all suspended accounts or click the *None* button to reset your selection. #. Click the *Unsuspend people* button to reinstate the accounts for all selected accounts. #. Click the *Delete accounts* button to delete all selected accounts in bulk. **This action cannot be undone and all personal information of these people will be deleted** (see :ref:`delete accounts `). #. The total number of suspended accounts is shown. .. warning:: When you delete an account, **all personal data is wiped from the system**. This action cannot be undone. The person'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 account' as author where an author is shown. Expired accounts ^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. figure:: /images/administration/expired_users.* :alt: List of all expired accounts List of all expired accounts #. **Show**: Select to view **expired** accounts. #. Basic details about each account are displayed to ensure that you are looking at the correct ones. That includes the dates on which the accounts were expired. #. The total number of expired accounts is shown. #. Select the account(s) for which you want to perform the same action. #. Click the *All* button if you want to select all expired accounts or click the *None* button to reset your selection. #. Click the *Reactivate expired accounts* button if you want to allow these people access to their accounts again. #. Click the *Delete accounts* button to delete all selected accounts in bulk. **This action cannot be undone and all personal information will be deleted** (see :ref:`delete account `). .. warning:: When you delete an account, **all personal data is wiped from the system**. This action cannot be undone. The person'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 account' as author where an author is shown. .. index:: pair: Administration; Site staff single: Site administrator; Site staff single: Double-click action when moving accounts .. _staff_users: Site staff ~~~~~~~~~~~~~~~ *Administration menu → People → Site staff* .. note:: *Site staff* is only accessible by site administrators. On this page you can choose which peoples receive site staff rights. Potential staff members - anybody on the site - are listed on the left while existing site staff members are listed on the right. .. figure:: /images/administration/site_staff.* :alt: Site staff Give site staff rights #. **Search**: If you have too many people on your site and you cannot see the ones you want, you can search for them here. #. **Potential staff**: Select the people you wish to make site staff. You can select multiple persons at once using ``Ctrl`` and ``Shift`` click. #. Add the potential staff members to the right-hand side, 'Current staff', by clicking the *right-arrow* button |right-arrow|. #. **Current staff**: If you want to remove an existing or accidentally added site staff member, you can remove them from the list on the right-hand side by clicking on their name. #. Then click the *left-arrow* button |left-arrow|, and the person is removed from the list. #. When you have chosen all members you wish to make site staff or removed from the current staff list, click the *Submit* button. .. note:: You can also double-click a name and it will be moved to the other side. .. index:: pair: Administration; Site administrators single: Site administrator; Site administrators .. _site_admins: Site administrators ~~~~~~~~~~~~~~~~~~~~~~ *Administration menu → People → Site administrators* .. note:: *Site administrators* is only accessible by site administrators. Site administrators have powerful permissions. They can make far-reaching changes and also :ref:`log in as other person `. 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. .. figure:: /images/administration/site_admins.* :alt: Give site administrator rights Give site administrator rights #. **Search**: If you have too many people on your site and you cannot see the ones you want, you can search for them here. #. **Potential administrators**: Select the persons you wish to make site administrators. You can select multiple persons at once using ``Ctrl`` and ``Shift`` click. #. Add the potential site administrator to the right-hand side, 'Current administrators' by clicking the *right-arrow* button |right-arrow|. #. **Current administrators**: If you want to remove an existing or accidentally added site administrator, you can remove the person from the list on the right-hand side by clicking on their name. #. Then click the *left-arrow* button |left-arrow|, and the person is removed from the list. #. When you have chosen all members you wish to make site administrators or removed from the current site administrator list, click the *Submit* button. .. note:: You can also double-click a name and it will be moved to the other side. .. index:: pair: Administration; Export queue single: Site administrator; Export queue single: Institution administrator; Export queue .. _export_queue: Export queue ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ *Administration menu → People → 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 :ref:`queue exports `, exports that account holders initiate via *Main menu → Manage → Export* are also queued. Once completed, a notification is sent to download the export file within 24 hours. All available export formats are considered for the export since Mahara 20.04 and only one combined export made. .. seealso:: The export queue requires that `cron `_ runs. .. figure:: /images/administration/export_queue.* :alt: Export queue for exports Export queue for exports #. **Search**: Enter your search term. The default text in the field shows you in which institution context you perform your search. Type the name, display name or username or email address or any partial thereof you wish to search for in the search field. :ref:`If you turned on the exact search `, you need to provide the correct name or email address and not a partial one. #. Use the drop-down arrow to choose a single institution in which to search for a person. #. Click the *Go* button to start your search. #. In the results table you see the profile picture of the person. #. **First name**: Displays the first name of the person. 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. #. **Last name**: Displays the last name of the person. #. **Display name**: Shows the display name of the person. #. **Username**: Clicking on the username, you are taken to the person's account settings page instead of their profile page as you would with the other names. #. **Export content**: Brief description of what is being exported. #. **Status**: Displays the status of the export. Only pending and failed exports are shown. #. **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* button or remove all checkboxes by clicking the *None* button. #. Click the *Re-queue* button to re-run all selected failed exports. #. **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* button or remove all checkboxes by clicking the *None* button. #. Click the *Delete* button to delete all selected pending or failed exports. .. index:: pair: Administration; Add a person single: Site administrator; Add a person single: Institution administrator; Add a person single: Change default account settings upon account creation .. _add_user: Add a person ~~~~~~~~~~~~~~~~~~~~~~~ *Administration menu → People → Add a person* You can add people to your site (site administrator) or your institution (institution administrator) by creating accounts for them manually one by one. .. figure:: /images/administration/add_user.* :alt: Add a person manually Add a person manually #. Click the *Create new account from scratch* radio button if you want to create an empty account. Provide the first name, last name and email address for this person. #. Click the *Upload Leap2A file* radio button if you want to import an account from another Mahara instance or a system that supports the Leap2A standard. Such a person could have :ref:`exported ` their portfolio from another Mahara instance. #. **Username**: Give the new account holder 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. #. **Password**: Choose a password for the account. The password must be at least six characters long. #. The password strength indicator gives you an idea of how strong your password is in relation to the :ref:`password policy `. #. **Site staff**: Switch to 'Yes' if the new account holder should have site staff rights. Only site administrators see this option. #. **Site administrator**: Switch to 'Yes' if the new account holder should have site administrator rights. Only site administrators see this option. #. **Institution**: Choose the institution of which the person should be a member. You also select the authentication method directly here. .. note:: If an authentication method requires the use of a remote username, you can enter that on the next screen in the :ref:`account settings `. #. **File quota**: Review the allocated file quota. You may change it here for this person if you are allowed to. #. **Institution administrator**: Switch to 'Yes' if the new account holder should have institution administrator rights in the chosen institution. #. **General account options**: Click this link to see default account options that you may choose to change while creating this account. These are the :ref:`general account options ` a person can change on the :ref:`Settings ` page. .. note:: You can only define the default account settings for an account, but not force the person to keep them forever. You could only do that by customising the system on the code level. #. Click the *Create account* button. #. The person will receive an email with the account details. .. index:: pair: Administration; Add people by CSV pair: Administration; Update people by CSV single: Site administrator; Add people by CSV single: Site administrator; Update people by CSV single: Institution administrator; Add people by CSV single: Institution administrator; Update people by CSV single: Change default account settings upon account creation single: Update file quota in bulk .. _add_users_csv: Add and update people by CSV ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ *Administration menu → People → Add people by CSV* You can use this function to upload new accounts in bulk via a CSV file (comma-separated file) and to update existing accounts. 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** accounts, this row **must** include: * username * password * email * firstname * lastname .. note:: :index:`Mahara ` also accepts CSV files that have a semicolon as separator instead of a comma. If you want to **update** existing accounts, 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 account, 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. :index:`If ` your site or institution has :ref:`locked fields ` or fields that are :ref:`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 * **expiry** - Sets the date on which a person's login is disabled automatically. This needs to be a valid date in the future, e.g. * 2019-03-25 * 25 Mar 2019 * +3 months * **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. .. figure:: /images/administration/add_users_csv.* :alt: Add people by CSV file Add people by CSV file #. **Institution**: Choose the institution **and** the authentication method for the accounts that you upload and / or change. #. **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. #. **CVS file**: You must upload a CSV file by clicking the *Browse* button and then selecting it from the files area on your computer. #. **Force password change**: If you select this option, people need to change their password before they can log in for the first time. #. **Email people about their account**: Change the switch to 'Yes' and people will receive an email with their account information. This is in particular good for internal accounts. .. note:: For accounts that are managed by an external authentication method such as Moodle or LDAP, do not select this option because the account holders already know their login information. #. **Update accounts**: Change the switch to 'Yes' if your CSV file contains changes for existing accounts. .. note:: When you add a new email address for a person to update the account settings, this new email address becomes the primary email address. The previously used email address stays in the account as secondary email address until the account holder deletes it. #. **General account options**: Expand this menu to see default account options that you may choose to change while creating or updating accounts. These are the :ref:`general account options ` a person can change on the :ref:`Settings ` page. #. Click the *Add people by CSV* button to upload and / or change accounts. .. note:: Depending on your server settings and / or the size of your installation, you may not be able to upload all accounts at once. You may wish to upload them in bunches of 100 instead. :index:`A progress bar ` shows the percentage of the completed upload of your accounts. |add_user_csv_progressbar| .. index:: Authentication method pair: Administration; Change authentication method in bulk single: Site administrator; Change authentication method in bulk single: Institution administrator; Change authentication method in bulk single: Change authentication method single: Change remote username .. _change_authentication_method: Change the authentication method and remote username in bulk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ After you have :ref:`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** people try to log in with their new credentials to avoid the creation of a second account for them. You can change the authentication method for multiple accounts at once to save you time manually updating each account. 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. .. figure:: /images/administration/user_search_remoteusername.* :alt: Find accounts in an institution to change their remote username Find accounts in an institution to change their remote username #. Go to *Administration menu → People → People search*. #. Click the *Advanced options* link to show filter options. Select any that you want to use. #. If you want to look for a particular name, display name, username, email address, or any partial thereof, type it into the search field. :ref:`If you turned on the exact search `, you need to provide the correct name or email address and not a partial one. The default text in the field shows you in which institution context you perform your search. #. If your site has more than one institution, you can limit your search to a particular one. #. Click the *Search* button to see results. .. note:: If you have more than 10 results, change the *Results per page* to see more results per page. #. Select the persons 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 accounts on that page. #. Click the *Get reports for selected accounts* button to proceed to the next step. You are taken to the *Account details report* page. .. figure:: /images/administration/csv_download_users.* :alt: Account details reports page Account details reports page .. figure:: /images/administration/csv.* :alt: Update the CSV file Update the CSV file with remote username and password .. figure:: /images/administration/update_users_remoteusername.* :alt: Update accounts in bulk Update accounts in bulk #. Click the *Download* button so that you get a CSV file which contains all necessary information for you to change the 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. .. note:: You do not need to see the column 'Remote username' for the data to be in the CSV download. If you wish to see it on screen, click the *Configure report* button and select the 'Remote username' column. #. Open the CSV file in your preferred spreadsheet software. In the column *remoteuser*, add or change the username that your account holders 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 person directly in this CSV file, you can do so as well. .. note:: You must provide a password for a new account. All others do not need to have a value in the password field. If you only want to update existing accounts, you can leave the password field entirely off. You must remove the column 'lastlogin'. Mahara will produce an error if you leave it in the file. #. Go to *Administration menu → People → Add people by CSV*. #. **Institution**: Choose the correct **current** institution and authentication method for the accounts that you are updating. #. **File quota**: Choose a different file quota here if you want to update it for accounts you update. #. **CSV file**: Choose the CSV file from your computer that you had updated. #. **Force password change**: Switch this option to 'No' even if you have a password in your CSV file. Since it's assumed that the accounts you are updating or creating are external accounts, nobody will need or can use their Mahara password. #. **Email people about their account**: Switch this option to 'No' as you are only wanting to update the remote username. Therefore, it is assumed that they don't need to reset their password. #. **Update accounts**: Switch this option to 'Yes' because you want to update existing accounts. #. **General account options**: You can make changes to the default account options for everyone, e.g. give them multiple journals by default, change their interface language etc. This will overwrite any changes that the account holders may have made in their personal settings. #. Click the *Add people by CSV* button to start the update. This process may take a little while depending on how many accounts you are changing. #. 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 accounts are updated until all errors are resolved. .. note:: If you intend to update more than 100 accounts 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 accounts in them. You are now ready to update the authentication method for these accounts: #. Go to *Administration menu → People → People search*. #. Select the institution in which the members are whom you want to check. #. Click the *Search* button to see results. #. Select the accounts for whom you want to change the authentication method. #. Click the *Edit selected accounts* button to proceed to the next step. You are taken to the *Bulk actions page* page. #. You see the remote username in a column. #. Click the *Change authentication method* tab. #. Select the institution **and** authentication method to which you want to change the selected accounts. #. Click *Change authentication method* to make the change. .. seealso:: If you only want to change the authentication method of certain accounts but do not have to worry about a remote username or updating any other information, you can change the authentication method directly on the :ref:`bulk actions screen ` without the export of the account details.