Browsing Yiddish translation

168.

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

169.

The parameter is ``?override=true``

170.

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

171.

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

172.

insecuredataroot: Share the same dataroot with another Mahara

173.

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

174.

You can enforce checking that files that are served have come from dataroot. You would only want to turn this on if you were running more than one Mahara against the same dataroot. If you are doing that, make sure you create separate dataroots for each installation, but symlink the artefact directory from all of them to one of them, and turn on 'insecuredataroot' on all the ones for which you created symlinks.

175.

isolatedinstitutions: Separate institutions entirely

176.

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

177.

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