> 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/assignment-tab.md).

# Assignment tab

1. Click the **Assignment** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-96c88ce92b87e64fb1ee89df9d765a2cac6adc61%2Flockerbankselfassignment2.png?alt=media)
2. Enter the appropriate access group(s) allowed to self-assign Lockers.

   Drag and drop the access group(s) into the grid.

   If you want a cardholder to be able to self-assign a locker with attributes, go to Step 7.
3. Configure 'End of assignment' as required.

   See [Locker Bank Configuration (Scenarios)](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/locker-management-solution/configuring-a-locker-bank/configuring-a-locker-bank-scenarios.md) for details.

   <table><thead><tr><th width="202">To...</th><th>then...</th></tr></thead><tbody><tr><td>Assign Lockers with explicit until date and/or time</td><td><ol><li><p>Click the <strong>Assign Lockers with explicit until date and/or time</strong> radio button.</p><p>The Until date and time fields activate.</p></li><li>Select the <strong>Until</strong> date check box.</li><li>Click the date drop-down button, then select an explicit end of assignment date.</li><li><p>Do you need to configure an explicit end of assignment time?</p><p>If <strong>no</strong>, then go step 4.<br>If <strong>yes</strong>, select the <strong>Until</strong> time check box, then enter the specified time.</p><p><strong>Notes:</strong></p><ul><li>If you do not configure the 'Until' date or, time or the 'One time use - Multiple entries allowed during first N minutes', then Locker assignments will be permanent.</li><li>When the configured 'Until' date expires, Cardholders will be unable to self-assign Lockers.</li><li>If you only configure the 'Until' time (i.e. the Until date checkbox is deselected), the Cardholder will have access to that Locker until the next occurrence of the configured time.</li></ul></li></ol></td></tr><tr><td>Assign Lockers for (fixed period)</td><td><ol><li>Click the <strong>Assign Lockers for</strong> radio button.</li><li>Enter a numeric value for <strong>the Assign Lockers for</strong>, then from the drop-down list select an option (minutes, hours, days, weeks or months).</li><li><p>Do you want to configure a specific end of assignment time?</p><p>If <strong>no</strong>, then go step 4.<br>If <strong>yes</strong>, select the <strong>then until</strong> time checkbox, then enter the specified time.</p><p><strong>Note:</strong> The 'then until' time will always overlap to the next occurrence time if the initial 'Assign Lockers for' period has not ended before the 'then until' time.</p><p><strong>E.g.</strong> If the Locker Bank is configured as:</p><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6a84a8aad917583503e77084d05e9d8657b71c78%2Flockerbankselfassignment3.png?alt=media" alt=""></p><ul><li>If the Cardholder badges at 09:02, the 7 hour assignment will not end before 16:00. Therefore, the Cardholder will have access to the Locker until the next occurrence of 16:00 hours.</li><li>If the Cardholder badges at 08:02, the 7 hours assignment will finish at 15:02, but the Cardholder will continue to have access to the Locker until 16:00 hours.</li></ul></li></ol></td></tr><tr><td>Raise a warning event before allocation expires</td><td><ol><li>Select the Raise a warning event checkbox.</li><li><p>Set the raise warning event period to the value that is required to represent the number of minutes, hours, days, weeks or months before the allocation expires to raise a warning event.</p><p>When the configured period is reached, the following event is raised: "[Locker name] of [Locker Bank] is due to expire for [Cardholder] at [YYYY-MM-DD] [HH:MM]."</p><p>Using this event (Event Group: Cardholder Locker Expiry Warning), you can set up a Notification Filter to alert Cardholders in advance of their imminent allocation expires. For more, see the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/creating-a-notification-filter.md">Creating a Notification Filter</a> topic.</p><p><strong>Notes:</strong></p><ul><li>If One time use checkbox is selected, then the Raise warning event option is disabled.</li><li>The warning event is only raised for Lockers that have an Allocated Until date.</li></ul></li></ol></td></tr></tbody></table>
4. You can configure the 'One time use - Multiple entries allowed during first N minutes' in conjunction with both the above options. The cardholder can use the Locker as many times as required during this period. However, once this period is over and the Cardholder badges, the Locker will open (to allow the Cardholder to remove his/her items from the Locker), then the Locker will be unallocated from the Cardholder despite the remaining assignments period.

   Do you want to configure 'One time use - Multiple entries allowed during first N minutes'?

   If **no**, then go step 6.\
   If **yes**, select the **One time use - Multiple entries allowed during first N minutes** checkbox.
5. Enter the number of minutes during which the Cardholder is allowed multiple entries (this is limited to 999 minutes).

   **Note:** If the 'One time use - Multiple entries allowed during first' is selected and has a value of '0' minutes, Lockers will be unallocated from Cardholders after:

   * the first badge, if the Locker was manually assigned, OR
   * the second badge (first badge to self-assign, second badge to remove), if the Locker was self-assigned.
6. Do you want to allow the operators to assign multiple lockers to a Cardholder?

   If **no**, go to step 7.\
   If **yes**, select the **Allow operators to assign multiple lockers per cardholder** checkbox.
7. If you want a cardholder to be able to assign Custom Fields Attributes:

   **Note:** You need to create Custom Fields first.

   1. Click on the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-af3563f0c875bf586e53a81c275a259039da055d%2Finsertarrow.png?alt=media) of the **Category** field and select a Catergory.
   2. Check the **Allow cardholder to select** checkbox.

      A cardholder who is a member of the Access Group will be able to self-select only a locker that has the Attribute in the Attribute column.

      **Note:** If you do not check the checkbox, the next available locker will be auto-assigned to the cardholder.
   3. Right-click the Access Group.

      The context menu will give you a list of the attributes that can be added (from the list created on the **Custom Fields** tab of one or more Lockers).
   4. Add the attribute and continue until you have selected all the attributes you want. Additional attributes are added by selecting Include '\[Value Name]', (e.g. Include 'Medium').

      If you do not add an attribute the default is 'All Values'. This means the same as selecting each available type individually.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-396ca35dba290770489766c752e424b1538cfee9%2Flockbank_assignmenttab_addvalues.png?alt=media)


---

# 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/assignment-tab.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.
