Translations by Masayuki Kuwada

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

Adding and editing site pages and collections is very similar to :ref:`creating <create_page>` and :ref:`editing <page_editor>` a portfolio page or collection. However, not all blocks are available when editing a site page in the :ref:`page editor <page_editor>` due to the different context. Please refer to the :ref:`overview of blocks <blocks_in_context>` for a list of all the blocks that you can use in a site page.

The administration in Mahara is reserved for site and institution administrators. Configuration settings and functionalities that are only available to site administrators with full privileges are marked as such.

.. image:: images/newin19point10.* :alt: new in Mahara 19.10

.. image:: images/administration/external/revoke_submission.* :alt: revoke submission

.. image:: images/group/plan_select_template.* :alt: select plan template

.. image:: images/buttons/tinymce_link.* :alt: tinymce link

.. image:: images/buttons/tinymce_anchor.* :alt: tinymce anchor

.. image:: images/buttons/tinymce_toggle_toolbars.* :alt: tinymce toggle toolbars

.. image:: images/buttons/resizing.* :alt: resize arrows

.. image:: images/page_instructions.* :alt: page instructions

.. image:: images/pages_overview_tag_search_only.* :alt: search tags only

.. image:: images/objectionable_material_shared_page.* :alt: portfolio accessed revoked

Delete certain groups in bulk

and / or delete only groups associated with a certain institution.

Delete certain users in bulk

When a large site is indexed or re-indexed so that Elasticsearch can display results, this process can take a very long time because the indexing happens on cron runs. If the batch that was indexed finished before the end of the cron though, there is a lag between the next batch starting up again. The ``fast_index`` CLI script starts the next batch indexing right after the previous one finished.

Typically, if you want to update a language pack, you need to download the entire language pack manually and place it into the appropriate folder. This is cumbersome, especially when you want to update the language packs during minor point updates.

Using CLI, you can speed up the process.

**Install or update language packs** for your instance of Mahara by listing the language codes.

The language codes that are used are the official international ones used for the `Mahara language packs <https://langpacks.mahara.org/>`_.

The ``config.php`` file sits in the ``/htdocs`` directory of your site. If you want to view all possible variables and their default values, you can find them in ``/htdocs/lib/config-defaults.php``. You can overwrite any default values by placing the variable in your ``config.php`` file.

A configuration variable needs to be written in the correct syntax in order to function. In Mahara, this is done the following way: ``$cfg->variable = value;``.

**variable =**: Here you see the variable that is to be set. Generally, it consists of one word, or words are joined together with underscores. The variable cannot contain any spaces.

**value;**: The value that the variable takes is displayed. The values can be different things, for example:

When you enable developer mode, the following two changes are made automatically for your site:

``debug.css`` will be included on each page. You can edit this file to add debugging CSS at your discretion.

directorypermissions: Permissions to use in dataroot

externallogin: Login via another site

``$cfg->externallogin = 'URL';``

You can overwrite the normal Mahara login page by providing an external one. This is useful if all people with access to the site shall log in via a different system and should be redirected there automatically.

Be careful when you have multiple institutions turned on. If at least one institution does not log in via the same external login page, you cannot use this setting as people in that institution would not be able to log in to Mahara at all since they can never get to the login page that they need.

:index:`If <single: Override external login>` you use the external login, you may need to override it at times, e.g. for troubleshooting the external authentication method or when it is not reachable. You can add a parameter at the end of the Mahara URL. You are then taken to the normal Mahara login screen.

The parameter is ``?override=true``

For example, https://mahara.example.com/admin/users/search.php **?override=true**

It doesn't matter what value you add. You can use "true" or "1" or anything else.

isolatedinstitutions: Separate institutions entirely

``$cfg->isolatedinstitutions = false;`` (default) or ``$cfg->isolatedinstitutions = true;``

If you have a multi-tenanted Mahara instance but do not want people from the individual institutions to communicate on the site or share groups, you can turn on "Isolated institutions".

This can be beneficial when you set up a large site for several organisations and need to adhere to privacy regulations that don't allow people from one organisation to contact people from other organisations.

See the section :ref:`"Isolated institutions" <isolated_institutions>` for more information.

Print the values of function and method arguments when printing a backtrace. This can be useful for debugging, but it is a security risk because function parameters may include sensitive data such as passwords and private keys. Though arguments whose names suggest that they contain passwords, will still be blanked out even if this feature is enabled.

log targets: Destination for log information

Typically, the noreply address is one that is not monitored as people are not supposed to reply to it.

``$cfg->openbadgedisplayer_source = '{"shortname":"url","shortname":"url"}';``