> 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/products/cc-software/operate/locker-management-solution.md).

# Locker management solution

A fully-integrated **Locker Management Solution** to manage locker access, automate allocation, and optimise locker utilisation natively from Command Centre. It works with any locker product wired into a **C6000** via **HBUS**. Available from **v7.90**.

## Allocation modes

* **Self-allocation:** a random locker allocated on presenting a credential at a **T20**.
* **Administrator allocation:** via Command Centre.
* **System automated allocation:** via a scheduled **Bulk Change**.
* **System automated allocation:** via Gallagher's **Cardholder REST API**.

## Expiry modes

Allocate for X hours; expire all at a specified time; one-time use (with a grace period); until the next occurrence of HH:MM (up to 24h access); until DD/MM/YYYY (for example end of week, month, semester, or year); or permanent.

## Audit and configuration

Command Centre provides **audit trails** on locker activity (one audit trail serves both locker and building access), letting a business understand usage levels and adjust accordingly.

It works with any locker product wired into a **C6000** (or I/O expansion modules) via **HBUS**. Lockers-per-bank is bound by standard controller and I/O considerations.

## Custom T20 Locker Display (companion feature)

Displays locker feedback (name and expiry) on a **T20 reader** when a credential is presented to a **third-party reader**. It must be used alongside the Locker Management Solution. Available v8.10 to v8.40; **merged into core in v8.40**, available to users with a Locker Management Solution licence.

## Use cases

Agile and hot-desking workspaces (self-assignment gives low-admin flexible storage); and student environments needing short (2 to 3 hour) locker allocation, primarily for device charging, where self-allocation savings scale with high locker turnover.

**Versions supported:** available from **v7.90**.

***

🔗 **Related**

* [Dual Authorisation Enhancement](/knowledge-hub/products/cc-software/operate/dual-authorisation-enhancement.md). Another Access Management Solutions feature.
* [Dynamic Exit Zoning](/knowledge-hub/products/cc-software/operate/dynamic-exit-zoning.md). Another Access Management Solutions feature.


---

# 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/products/cc-software/operate/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.