Locking a Repository

If you want to temporarily restrict access to your repository for administrative purposes, you can lock it. This will prevent users from logging in unless they have the Manage Connections privilege. For example, you might lock your repository in order to reduce the possibility of changes to the repository when you back it up, move a volume, or for other maintenance tasks. While the lock is in effect, users without the Manage Connections privilege who try to log in will be prevented from doing so and notified that they cannot log in because an administrative lockout is in effect.

Important: Locking a repository does not disconnect the users who are already connected to it; they will remain connected after the lock has gone into place. To see what users are already connected to the repository, you can use the repository's Sessions node.  If you wish to exclude all users who do not have the Manage Connections privilege, you can disconnect users. (See Disconnecting a User for more information.)  Users without Manage Connections will not be able to log in after they have been disconnected until the administrative lockdown is lifted.

To lock a repository

  1. Start the Administration Console and log in as a System Manager.
  2. In the console tree, expand the desired Laserfiche Server.
  3. Select the desired Laserfiche repository.
  4. From the Action menu, point to All Tasks and select Lock (Repository), or right-click the repository name, point to All Tasks, and select Lock (Repository). ClosedClick to view screenshot.
  5. You will be prompted to confirm the repository lockdown. Click Yes to lock the repository.

To lock a repository 

  1. Start the Web Administration Console and log in as a System Manager.
  2. Select the desired Laserfiche Server.
  3. Select the desired repository.
  4. Click on the down arrow next to the repository name. Click Lock Repository.

  5. You will be prompted to confirm the repository lockdown. Click OK to lock the repository.