> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/locker-management-solution/locker-bank-status-and-overrides.md).

# Locker Bank Status and Overrides

An Operator can perform the following overrides at the Locker Bank level:

* Open Unallocated Lockers - Unlocks all unassigned Lockers (including quarantined Lockers)
* Cancel Override - Cancels the Unlock Unallocated Lockers override

### Procedure

To override a Locker Bank, perform the following procedure:

1. From the Configuration Client menu, click **Configure** > **Lockers**.

   The Locker List Window displays.
2. Double-click on the appropriate Locker Bank.

   By default the **General** tab displays.
3. Click the **Status and Overrides** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-799769f16fbd50a25fd82990678fa625a0c2a965%2Flockerbankstatusandoverride.png?alt=media)
4. Select 'Open Unallocated Lockers' from the **Override** drop-down list. This includes opening quarantined Lockers.
5. Set the duration for the override to be implemented.

   You can either:

   * select the **Until this time** radio button, and enter the time of day you want the override to occur, or
   * select the **For nn Hours, nn Minutes** radio button, and enter the hours, minutes and/or AM/PM.
6. Click the **Override Now** button.
7. Click **OK**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/locker-management-solution/locker-bank-status-and-overrides.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
