> 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/shifts/configuring-a-shift.md).

# Configuring a Shift

### Introduction

This procedure covers how to set up a new Shift. A Shift item can be configured for each shift that is worked on site, with details such as their on days and off days, and start and end times. Assigning the applicable Access Groups to the Shift allows for the Shift to be used to report on the Cardholders in those groups.

**Note:** The 'Edit Site' operator privilege is required to perform this procedure.

***

### Configuration

To create a Shift, perform the following procedure in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Shifts**.

   The **Shift** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right-click** and select **New\...** > **Shift**.

   The **General** tab displays.
3. Complete the fields as required.

   For further details, see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the following tabs and configure the Shift as required:

<details>

<summary>Shifts tab</summary>

1. Click the **Shifts** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-75740ad5a1c4a75c6ece23748b6f37bed35bb399%2Fshift_shiftstab.png?alt=media)
2. In the **First Date** field, click the drop-down and select the date of the first 'Day On' day (working day). This could be in the past or future.

   If this shift has already begun in reality (i.e. staff are already working this shift), select the first 'Day On' of the *current* shift cycle. For example, if today is January 4th, and the most recent 'Day Off' (break day) was January 1st, and January 2nd was therefore the first 'Day On' of the current shift cycle, set 'First Date' to January 2nd.

   If this shift has not begun yet, select the first 'Day On' (working day) that will be worked by workers of this shift. The Shift will not be valid until the start of this day.
3. In the **Days On** field, enter the number of working days in the shift. This is the number of consecutive days that staff work between their break days.
4. In the **Start Time** field, enter the time of day that the shift starts on each of the 'Days On'.
5. In the **End Time** field, enter the time of day that the shift ends on each of the 'Days On'.
6. In the **Days Off** field, enter the number of break days in the shift. This is the number of consecutive days that staff stop working for, after the last 'Day On' of the shift cycle and before the first 'Day On' of the next shift cycle.
7. In the **Last Date** field, optionally click the drop-down and select the last day that this Shift is valid for. This date must not be earlier than the 'First Date'. This date does not need to line up with the shift cycle. After this date, this Shift will not apply to any Cardholders. Therefore, after this date:
   * if selected in a Time Report's or Time Report - Overview's 'Report Date and Time' filter, the Shift will have no effect on the Report, and,
   * if using the licensed Regulated Zones feature, Shift management Regulated Zone Rules using this Shift will no longer activate/disable the Competency or raise any alarms in accordance with this Shift. For example, a Shift management rule will not raise an early arrival alarm for a Cardholder whose shift is invalid, since there is no longer a valid definition of 'early'.

</details>

<details>

<summary>Access Groups tab</summary>

1. Click the **Access Groups** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c8c529cef9058813e8431e173336624e0696725a%2Fshift_accessgroupstab.png?alt=media)
2. Drag and drop all Access Groups that work this Shift to the grid on the Access Groups tab.

   Each Cardholder in these Access Groups will have this Shift applied to them, so their access events will appear in a Time Report or Time Report - Overview with this Shift applied to the 'Report Date and Time' filter, and they can be managed by a Regulated Zones Shift management rule with this Shift assigned.

   Once an Access Group is added to a Shift, the Shift will display in a read-only list on the Access Group's 'Shifts' tab.

</details>

5. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Shift item.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
6. Click the **Notes** tab if you want to add a note(s) about this Shift item.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
7. Click **OK** to close and save your changes.

   Click **Cancel** to close without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/shifts/configuring-a-shift.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.
