<?php
/**************************************************************************
 *
 * LOVD DATABASE WEBSITE
 *
 * Created     : 2008-07-15
 * Modified    : 2008-07-16
 * For LOVD    : 2.0-08
 *
 * Access      : Public
 *
 * Programmer  : Ing. Ivo F.A.C. Fokkema <I.F.A.C.Fokkema@LUMC.nl>
 * Last edited : Ing. Ivo F.A.C. Fokkema <I.F.A.C.Fokkema@LUMC.nl>
 *
 *************/

define('ROOT_PATH', '../../../');
define('DOCS_PATH', ROOT_PATH . 'docs/');
require DOCS_PATH . 'inc-website-init.php';
require ROOT_PATH . 'inc-top.php';
?>

            <H3>LOVD Setup</H3>
            <H4>Authorized users</H4>
            <H5>Locking users from the system</H5>

            As a manager, you can lock curators out of the system. The database administrator can also lock managers. A user is automatically locked if the wrong password is used three times to log into his/her account, provided this security setting is enabled (see <A href="<?php echo DOCS_PATH; ?>lovd_setup/lovd_system_settings.php">LOVD system settings</A>), but this lock can also be enabled by clicking the "Lock user" link below the user's detailed view. If the user is already locked, the link is named "Unlock user".<BR>
            The "Lock user" and "Unlock user" links are very quick ways to deny or allow access to LOVD, although this can also be accomplished through the edit user form.<BR>
            <BR>

            Users who are logged in, can also be booted out of the system. If a user is logged in, a link is added named "Force user log out". This will destroy the user's session and force the user's log out. Locking the user essentially also causes the user to be booted out of the system the next time the user performs an action, although in that case it's not possible for the user to log back in until the account is unlocked.<BR>
            <BR>

<?php
include ROOT_PATH . 'inc-bot.php';
?>
