> 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/configuring-a-locker-bank/configuring-a-locker-bank-scenarios.md).

# Configuring a Locker Bank (Scenarios)

<table><thead><tr><th width="265">Scenario</th><th width="387">Configuration</th><th>Configuration /Explanation</th></tr></thead><tbody><tr><td>Assign Lockers permanently (without an until date/time)</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fb22e3ce9b17983f0bb6622cc99016caae24d846%2Flocker-scenario1.png?alt=media" alt=""></td><td><p>The 'Until' date and time checkboxes are deselected.</p><p>The 'One time use - Multiple entries allowed during first' checkbox is deselected.</p></td></tr><tr><td>Assign Lockers to end at a future explicit date and time</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3b30dc329be5d411873cdebdad6deb767ab72082%2Flocker-scenario2.png?alt=media" alt=""></td><td>Locker assignments will end at the configured date and time (i.e. on 3/05/2018 at 13:30).</td></tr><tr><td>Assign Lockers to end at a future explicit date</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5121732cd9e01ce1d01d9c64ae9231f4a4e661aa%2Flocker-scenarios-endatexplicitdate.png?alt=media" alt=""></td><td>Locker assignments will end at 23:59 on that explicit date (i.e. on 3/05/2018 at 23:59).</td></tr><tr><td>Assign Lockers to end at the next occurrence of an explicit time</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4f969aaf9040f6ccdbbc82daeca22439cdc3358c%2Flocker-scenarios-nextoccurencetime.png?alt=media" alt=""></td><td><p>Locker is assigned until the next occurrence of the explicit time. Depending on the time of allocation, an assignment could be only for a few minutes or almost an entire day.</p><p><strong>E.g.</strong> If a Cardholder badges:</p><ul><li>at 12:56 to assign a Locker, the Locker will be assigned for only a few minutes.</li><li>at 13:01 to assign a Locker, the Locker will be assigned for almost an entire day.</li></ul></td></tr><tr><td>Assign Lockers to end in a specific number of minutes, hours, days, weeks or months</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5854917fbeaca5b3b72f4f1d86d9bedbde23cc5d%2Flocker-scenarios-relativenumberofxx.png?alt=media" alt=""></td><td>In this example, the Locker is assigned for 3 days.</td></tr><tr><td>Assign Lockers to end in a specific number of hours or days etc. and then at the next occurrence of an explicit time</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c3463f1f740e9d9f6bf9bdf9bcbb8dd0dfc35747%2Flocker-scenarios-relativenumberofxx%2Cthenuntil.png?alt=media" alt=""></td><td><p>Locker is assigned for the configured period (i.e. 8 hours) plus the time until the next occurrence of the configured time (i.e. 17:00).</p><p>Depending on the time of the allocation, the assignment period can vary.</p><p><strong>E.g</strong>. The first Cardholder is assigned a Locker at 08:58. This Cardholder’s assignment will be for 8 hours and 2 minutes.</p><p>The second Cardholder is assigned a Locker at 09:02. This Cardholder’s assignment will be for 31 hours and 58 minutes. This is because the first assignment period (i.e. 8 hours) wasn't finished before the first occurrence of 17:00, therefore the assignment was extended till next occurrence of the 17:00.</p></td></tr><tr><td>Assign Lockers for one-time use – Multiple entries allowed during first xxx minutes</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5f54fabf0e20f776f49ddb44a82fb6034ba23dc4%2Flocker-scenarios-onetimeuse.png?alt=media" alt=""></td><td><p>Locker is assigned permanently however, once the one time use minutes have lapsed (i.e. after 20 minutes), and the Cardholder badges, the Locker opens (to allow the Cardholder to remove items) then it is removed from the Cardholder.</p><p><strong>Note:</strong> During the one time use period, the Cardholder can badge as many times as required without losing the Locker.</p></td></tr><tr><td>Assign Lockers for a certain period (i.e. 2 hours) but only for one-time use - Multiple entries allowed during first xxx minutes</td><td><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ad6a00d98c02fd7b364817566548f77eed5ca4e0%2Flocker-scenarios-max2hours%2Conetimeuse.png?alt=media" alt=""></td><td>Locker is assigned for a maximum of 2 hours with 10 minutes of multiple entry time (the Cardholder can badge to use the Locker as often as required in the first 10 minutes). However, once this period is over, and the Cardholder badges, the Locker opens (to allow the Cardholder to remove items) then the Locker is removed from the Cardholder. Otherwise, the assignment will end after 2 hours.</td></tr></tbody></table>


---

# 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/configuring-a-locker-bank/configuring-a-locker-bank-scenarios.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.
