> 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/command-centre-client/configuring-command-centre/administration/schedules/changing-times-and-states-within-schedules.md).

# Changing times and states within Schedules

You can change the state of any of the time-state list options as required.

1. Click on the state/time bar of the Day Category you want to make a state change to.

   A State/time data entry pop-up displays, allowing you to alter states for different times during the 24 hour cycle.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7d2ad86ca16d8fb480410ec210306045041f824c%2Fchangingtimes%26states.png?alt=media)

   **Note:** The name of the Day Category will display in the title bar. This example is for the "Weekends" Day Category.
2. The **From** time of 00:00 (Midnight) cannot be changed, however the State can be by selecting another state from the drop-down list.

   The available states will depend on the Schedule type.

<details>

<summary>Click here for a description of the states available for each Schedule Type</summary>

<table><thead><tr><th width="132">Schedule Type</th><th>Possible States ( Note: The default state is highlighted)</th></tr></thead><tbody><tr><td>Cardholder Access</td><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-675a17dda89ca7aef8c650721b8189338ce3c72a%2Fschedule_chaccessstates.png?alt=media" alt=""><br>Access can be "Granted" or "Denied".</td></tr><tr><td>Access Zone *</td><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2ee70dd7d0824ce16879d75b898523dca80641b3%2Fschedule_azstates.png?alt=media" alt=""><br>The various modes available set the access mode for the Access Zone, (e.g. Free - No PIN, Secure - No PIN, Secure - PIN, etc.). The access mode controls the credentials required in order to identify a Cardholder at the reader.<br><br><strong>Note:</strong> The access mode also controls the action required when performing an Access Zone or Alarm Zone override at the reader.<br>For an HBUS Terminal, the Log On Credentials on the <strong>Welcome Screen</strong> tab control the action required when performing an Access Zone or Alarm Zone override at the terminal using the <strong>Arm</strong> or <strong>Mode</strong> keys. However, the access mode controls the action required when performing a double card override at an HBUS Terminal.<br>For example:<br><strong>Free - No PIN</strong><br>With this mode the door is in free access. To perform an override you need to press the appropriate function key on the reader, (i.e. <strong>Arm</strong> or <strong>F1</strong> for Alarm Zones and <strong>Mode</strong> or <strong>F2</strong> for Access Zones), and present a valid credential. When attempting to unset an Alarm Zone you will need to present a valid credential.<br><strong>Free - PIN</strong><br>With this mode the door is in free access. To perform an override you need to press the appropriate function key on the reader, (i.e. <strong>Arm</strong> or <strong>F1</strong> for Alarm Zones and <strong>Mode</strong> or <strong>F2</strong> for Access Zones), present a valid credential and enter your 4 digit PIN. When attempting to unset an Alarm Zone you will need to present a valid credential and enter the PIN.<br><strong>Secure - PIN</strong><br>With this mode the door is secure. For access present a valid credential and enter your PIN. To perform an override you need to press the appropriate function key on the reader, (i.e. <strong>Arm</strong> or <strong>F1</strong> for Alarm Zones and <strong>Mode</strong> or <strong>F2</strong> for Access Zones), present a valid credential and enter your PIN.<br><strong>Code or Card - No PIN</strong><br>With this mode, for access you can either enter the 4 digit code (set on the <strong>Access Mode</strong> tab of the Access Zone Property pages), or present a valid credential.<br>To perform an override you need to press the appropriate function key on the reader, (i.e. <strong>Arm</strong> or <strong>F1</strong> for Alarm Zones and <strong>Mode</strong> or <strong>F2</strong> for Access Zones), and present a valid credential.<br><strong>Dual Auth - No PIN</strong><br>With this mode, access is gained by two authorised Cardholders, each presenting a valid credential. To perform an override you need to press the appropriate function key on the reader, (i.e. <strong>Arm</strong> or <strong>F1</strong> for Alarm Zones and <strong>Mode</strong> or <strong>F2</strong> for Access Zones), and present a valid credential.<br><br><strong>Note:</strong> Dual Authorisation is not supported for Elevator use.</td></tr><tr><td>Alarm Zone *</td><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-437b61057d7fc1f1dfc0671c6baaf55a58cebd54%2Fschedule_alarmzonestates.png?alt=media" alt=""><br>(or as defined in Configuration Client on the <strong>Alarm Zone States</strong> tab of the Server Properties)<br>All items in the Alarm Zone change to the same state (set/unset, armed/disarmed) at the same time.</td></tr><tr><td>Output *</td><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-976b0efa564c2a0c270ac7f62868065f5768aff6%2Fschedule_outputstates.png?alt=media" alt=""><br>Sets the action (on, off, etc.) of the outputs that are assigned to this Schedule. This is where you would configure a Time Clock Relay.</td></tr><tr><td>Notification</td><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-29ba902737e14f7ce15563b898267c8fa75039de%2Fschedule_notificationstates.png?alt=media" alt=""><br>Notifications can be "Disabled" or "Enabled".<br>If in "Disabled" state, then cardholders with this Schedule will not receive notifications during this time.</td></tr><tr><td>HV/LF</td><td><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2d57030eb0a7776a03d519ae25cf286f6c312ef8%2Fschedulehvlfstates.png?alt=media" alt=""><br>Set the action (High Voltage, Low Feel or Cancel Untimed Overrides) for all Alarm Zones that this Schedule has been assigned to.</td></tr></tbody></table>

\* Included in the list of States is the option to **Cancel Untimed Overrides**. A **Cancel Untimed Overrides** instance entered at a particular time of day returns the state of an Access Zone, Alarm Zone or Output type Schedule to the scheduled state.

A **Cancel Untimed Override** instance entered on a Schedule acts to cancel any non-timed override in existence for all items controlled by that Schedule. As it does not have a time interval it appears on the state/time bar as a ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6c75c842bd1edbcec9835343b96feb84690745a2%2Fcanceluntimedoverride.png?alt=media), so it is easily recognised as a cancel override.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8bf3c88b29172ed2ac99b9096afa16999d5540d4%2Fschedule_canceloverride.png?alt=media)

</details>

3. Click the **Add a state change** button.

   A new State drop-down field appears with the Time Box beside it enabled.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a76ab94ea90e7625baea4fbd86ae2217267d3dc3%2Fchangingtimes%26states2.png?alt=media)
4. Select the required State from the drop-down list.
5. Alter the Time Box to the time you want that State to change from.
6. Repeat Steps 1-5 for each state change you want to make to any of the Day Categories on this Schedule.
7. Click the **OK** button.

   The State/time data entry pop-up closes. The following screen shot is an example of how the screen will start to look as you add state changes.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-3fb1fef5491c503f8ff3b8a9edb16e65ca7108ad%2Fdaycategoryentry2.png?alt=media)
8. Click the **Save** button.

   **Note:** Whilst the state/time bar shows pending updates, these are not committed to the database until the **Save** button is clicked.


---

# 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/command-centre-client/configuring-command-centre/administration/schedules/changing-times-and-states-within-schedules.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.
