Browsing Kirghiz translation

37.

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

38.

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

39.

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

40.

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

41.

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

42.

**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 account settings.

43.

Administrators can configure the items that count towards profile completion in *Administration → Institutions →* :ref:`institution administration <profile_completion>`.

44.

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

45.

**This feature is still experimental.** Turning this feature on will export individual portfolios in *Portfolio → Export* via the export queue. That means that the export is made when there are enough system resources available. The user exporting a portfolio will receive an email when the export is ready for download.

46.

**Multiple journals**: If allowed, :index:`all users <single: User settings; Allow multiple journals for everyone per default>` will have multiple journals per default. They can still change that setting in their personal account settings.