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

# Shifts

### Introduction

The licensed Shifts feature introduces a new 'Shift' item to Gallagher Command Centre, which must be configured in Gallagher Configuration Client. Shift items can be configured with the shift's start date, days on shift, days off shift (break days), daily hours of the shift, and optionally an end date. The Access Groups that work this shift can then be assigned to the Shift item. This allows for two main functions:

#### Shifts in Time Reports

The Time Report and Time Report - Overview allow Shifts to be used. In these reports, specific Shifts can be applied to the Report Date and Time filter, so that the report only includes events for Cardholders who were assigned to one (or more) of those Shifts within the Report Period. Additionally, when Shifts are used in the Report Date and Time filter, rather than setting 'Daily Time Ranges' to mark the earliest and latest assumed entry and exit times, Shift items are used. Where a Cardholder is missing an entry or exit event within the specified Report Period, the Start time or End time of their Shift can be used to assume the missing entry or exit time.

The Report Layout can also be configured to include the 'Shift' column, to display the Shift(s) the Cardholder was working during the time between each entry and exit event.

**Note:** A report row’s ‘Shift’ column only displays a Shift if the Cardholder was actively in an Access Group associated with a Shift at the times that the entry or exit events occurred. This also applies to the past movement time for historical manual access events; it is not relevant in the report whether the Cardholder is associated with a Shift at the time an operator manually creates an event.

#### Regulated Zones - Shift management

Regulated Zones is a separately licensable feature of Command Centre. It introduces a 'Shift management' rule that raises an alarm when a Cardholder enters a zone early for their shift, fails to enter on time, or fails to exit on time. Previously configured using Personal Data Fields to specify shift details, this feature has been enhanced to allow Shift items to be used instead, with a similar but more intuitive configuration, and an expanded result.

***

### Licensing

Shift items are a licensable feature. You must purchase the following licence to configure Shifts in Gallagher Command Centre:

`[Features]`\
`Shifts=1`

***

### Configuration

Select the item below that you require further detail on:

![](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 Shift](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/shifts/configuring-a-shift.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) [Purging Shift history](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/shifts/purging-shift-history.md)

#### Reports

Shifts are only applicable to the reports 'Time Report' and 'Time Report - Overview' in Gallagher Command Centre Client (not Configuration Client). Refer to the *"Creating Reports"* chapter and the *"Quick Tips for configuring the 'Report Date and Time' filter"* topic in the Gallagher Command Centre Help.

#### Regulated Zones

Regulated Zones is a separate licensable feature. Refer to the document *"Release Note Regulated Zones (v9.11).pdf"* (or later version) for information about using Shifts with Regulated Zones.


---

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