> 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.md).

# Locker Management Solution

### Introduction

The 'Locker Management Solution' is used to manage Cardholder's access to Lockers. You can configure Lockers to enable Cardholders to self-assign Lockers, or the operator can manually assign Lockers to Cardholders via the Locker Viewer, Cardholder Viewer, or Bulk Changes. You can configure Lockers so that they are automatically quarantined for a specified period upon the expiry of their Cardholder assignments, or the operator can manually quarantine Lockers at any time. While quarantined, Lockers cannot be assigned to Cardholders, and can only be opened by privileged Access Groups. Using the Locker Viewer, an operator can view all current assignments he is privileged to.

This feature enables you to (in either the Command Centre Client or the Configuration Client):

* manage individual and group access to Lockers
* configure Lockers for self-assignments and/or manual assignments
* configure Lockers for automatic quarantining and/or manual quarantining
* notify the Cardholder when a Locker has been assigned or removed (via existing Command Centre Notifications framework), see [Enabling Event/Alarm Notifications for a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/enabling-event-alarm-notifications-for-a-cardholder.md).
* report on Locker activity (access events plus alarms such as Locker Forced Open and Locker Open Too Long)
* report on Cardholders including current Locker assignments
* view status, and override Lockers
* manage remote site Lockers. See **Multi-server** section below.

**Notes:**

* The recommended lockers limit is 256 lockers per Controller 6000 or 7000, with 16 x High Density IO boards and 2 to 4 readers. This limit is derived from the Controller 6000 or 7000 Input/Output hardware limit.
* If an Alarm Zone is assigned to an HBUS Terminal (via Alarm Zones tab), then that HBUS Terminal cannot be allocated to a Locker Bank.

***

### Licensing

The 'Locker Management Solution' is a licensable feature, i.e. your license file must contain the following options:

`[Features]`\
`Lockers=1`

`[Limits]`\
`Lockers=X` (Where `X` is the number of Lockers that can be created)

***

### Operator Privileges

An Operator requires the appropriate Locker privileges to perform Locker tasks. The privileges only apply within the Divisions assigned to that Operator Group.

<table><thead><tr><th width="234">Operator Privilege</th><th>is required to...</th></tr></thead><tbody><tr><td>"Edit Lockers"</td><td>create, edit and delete Lockers and Locker Banks.</td></tr><tr><td>"Manage Locker Assignments"</td><td>assign (allocate), modify and/or remove Lockers from Cardholders. It does not include View Cardholder privilege however; View Cardholder privilege is not required to see existing Locker assignments in Locker Viewer.</td></tr><tr><td>"Override"</td><td>manually quarantine Lockers ('Quarantine Locker' override), and cancel the active override on a Locker ('Cancel Override'). Performing 'Cancel Override' on a quarantined Locker will take it out of quarantine.</td></tr><tr><td>"Override - Open Locker"</td><td>open Lockers and unallocated Lockers ('Open Locker' override).</td></tr><tr><td>"View Lockers and Assignments"</td><td>view Lockers, Locker Banks and Locker assignments.</td></tr></tbody></table>

**Notes:**

* Edit Site does not include Edit Lockers therefore, you cannot create, edit or delete Lockers or Locker Banks.
* View Site cannot view Lockers or Locker Banks.

***

### Multi-server

The following Command Centre multi-server functionalities can be achieved from a remote server:

* override Lockers (Open Locker, Quarantine Locker, Cancel Override)
* override Locker Banks (Unlock Unallocated Lockers)
* view Lockers
* assign and/or remove Lockers.

***

### Considerations

* Cardholders can continue to self-allocate and use Lockers while the Command Centre server is down. The Command Centre server will be updated once it is back online.
* When the Controller and the Command Centre server reconnect, if there is a conflict between an attempted operator allocation or quarantine (that occurred while the Controller was offline) and a self-allocation, the self-allocation takes precedence and the attempted Operator action is ignored.
* While the Controller is offline, Locker Configuration and operator modification of Locker assignments will be ignored by the Command Centre. For example, a Cardholder assignment is about to expire in 3 minutes. The connection between server and controller is lost, and the operator modifies the Locker Configuration to extend the Cardholder assignment. After 4 minutes, the connection is re-established. However, the change to the Cardholder assignment has not occurred, and the Locker has been removed from the Cardholder.

  Therefore, configuring, assigning, or removing Lockers while the Controller is offline are not recommended.
* While the Controller is offline and a Cardholder self-assigns a Locker, if the allocated Locker is being accessed for the first time, the T-20 reader grants access, but it does not display the Locker name.
* If a Locker Bank and a Locker reader are connected to different Controllers, and a Cardholder presents a credential to the reader, the reader will time out after 20 seconds and the Cardholder will be denied access.

***

### Bulk Configuration Tool

The Bulk Configuration Tool can be used to create and configure a large number of Lockers and Locker Banks. Refer to the *Bulk Configuration Tool* page on the Gallagher Security Hub for further detail:

[Bulk configuration tool | Deployment Resources | Gallagher Knowledge Hub](https://help.security.gallagher.com/knowledge-hub/deployment-resources/support-tools-and-troubleshooting/bulk-configuration-tool)

**Note:** An account is required to access the Security Hub, so register if needed.

***

### Configuration

To configure Locker Management, perform the following procedures in the Configuration Client:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring a Locker Bank](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/locker-management-solution/configuring-a-locker-bank.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Locker Bank Status and Overrides](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/locker-management-solution/locker-bank-status-and-overrides.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring a Locker](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/locker-management-solution/configuring-a-locker.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Locker Status and Overrides](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/locker-management-solution/locker-status-and-overrides.md)


---

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