Commit 5e998862 authored by Kristina Hoeppner's avatar Kristina Hoeppner
Browse files

admin/config_site: Update screenshots for new features

To include the new settings for the "Reports"
section.
parent 52716509
......@@ -111,15 +111,20 @@ User settings
#. **Anonymous comments**: :index:`If allowed <single: Feedback; Anonymous feedback>`, logged-out users / users without a login can leave comments on public pages or pages they can access via a secret URL.
#. **Profile access for all registered users**: If this option is set to "No", profile pages are initially viewable by all registered users, but the owner is allowed to restrict access to their institution only if they wish. Enable this option if you want to make sure all users can see each others' profile pages. Profiles of institution members will always be visible to other members of the same institution.
#. **Staff report access**: :index:`If <single:Configure site; Staff report access>` set to "Yes", institution staff will have :ref:`access to the reports page for users in their institutions <user_reports>`. This page is normally restricted to administrators and lists extra user information including page access lists.
#. **Staff statistics access**: If set to "Yes", institution staff will have access to the statistics for users in their institutions. This is normally restricted to administrators and site staff.
#. **Access reports for staff**: :index:`If <single:Configure site; Staff report access>` set to "Yes", site and institution staff will have :ref:`access to user reports <People_reports>`. The following reports are available to them:
* Masquerading sessions (if logging of these is turned on)
* Portfolio access
* User details
#. **All reports for institution staff**: If set to "Yes", institution staff will have access to all reports in their institutions. This is normally restricted to administrators and site staff.
#. **Users can disable device detection**: If allowed, users can disable mobile device detection in their :ref:`account settings <general_account_options>`. This allows them to be more flexible in what they can view and do on a mobile device such as a smartphone or tablet.
#. **Require reason for masquerading**: If set to "Yes", administrators will be required to enter a reason for :ref:`masquerading as other users <login_as>`. This will be logged, and if the setting "Notify users of masquerading" is enabled, included in the notification to the user about the masquerading. This setting needs :ref:`logging <logging_settings>` to be turned on.
#. **Notify users of masquerading**: If set to "Yes", users will be notified :ref:`when an administrator masqueraded as them <login_as>`. The notification will include who, when and - if enabled under "Require reason for masquerading" - why. This setting needs :ref:`logging <logging_settings>` to be turned on.
#. **Show profile completion**: If set to "Yes", :index:`a progress bar with tips <single: Profile completion activation>` about what to complete in the user profile will be displayed in the sidebar to users. They can disable it in their :ref`account settings <general_account_options>`.
#. **Show profile completion**: If set to "Yes", :index:`a progress bar with tips <single: Profile completion activation>` about what to complete in the user profile will be displayed in the sidebar to users. They can disable it in their :ref:`account settings <general_account_options>`.
.. seealso::
Administrators can configure the items that count towards profile completion in *Administration → Institutions →* :ref:`institution administration <profile_completion>`.
Administrators can configure the items that count towards profile completion in *Administration → Institutions →* :ref:`Profile completion <profile_completion>`.
#. **Export to queue**: :index:`If allowed <single: Use export queue for personal portfolio export (experimental)>`, the export queue will handle the exporting of user portfolios via Leap2A for better server load management.
......@@ -147,6 +152,11 @@ Mahara comes with a search plugin that allows you to search for users and pages.
.. seealso::
You can configure the internal search plugin in the :ref:`administration of the search plugin <plugin_search>`.
Elasicsearch is another search plugin that is supported by Mahara out of the box. The search server will need to be installed separately though. Elasticsearch is useful for fulltext search and is required for |new in Mahara 17.10| advanced reporting.
.. note::
You need to choose the Elasticsearch plugin if you turn on :ref:`"Event log reporting" <logging_settings>`.
.. index:: Public group, Group category
pair: Administration; Group settings
single: Site administrator; Group settings
......@@ -408,16 +418,10 @@ Mahara logs a number of events. These can now be collected in the database as we
#. **Log events**: Decide which events you wish to log in the database. Events are generated every time the user does something significant on the site, such as editing a page. This log is kept in the ``event_log`` table in the database.
* **None**: Nothing is logged in the database.
* **Masquerading**: Only masquerading sessions are logged. This setting needs to be turned on if you wish to report on administrator masquerading.
* **Masquerading**: Only masquerading sessions are logged. This setting needs to be turned on if you wish to :ref:`report on administrator masquerading of users <masquerading_report>`.
* **All**: All events that can be logged in the database are logged.
.. note::
No matter which logging setting you choose, all events are still logged in the access log.
#. **Event log expiry**: Decide for how long you wish to keep your database log. If you selected to log all events, the table can grow quite quickly especially on an active site. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, the event log is not deleted by default.
.. seealso::
A report of masquerading sessions is available in the :ref:`"User reports" <user_reports>` section if you turned on logging of masqueraded session or all logging.
#. |new in Mahara 17.10| **Event log reporting**: :index:`If <single: New in Mahara 17.10; Logging for advanced reporting>` set to "Yes", you can report over a number of activities on the site in the :ref:`"Reports" section <reports>` that require events to be logged.
The table ``event_log`` contains the data that can be logged:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment