> 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/products/cc-software/configure/calendars/calendars-default-calendar.md).

# Default calendar

Understand how the Default Calendar applies Day Categories to dates across a Command Centre site.

### Calendars in Command Centre

A Calendar maps Day Categories onto real dates so that schedules know what kind of day each date is. It controls scheduled items across Command Centre, including Access Schedules, Scheduled Outputs, access decisions, and Notification Schedules.

The Default Calendar is the site-wide calendar. Every controller uses it unless told otherwise.

{% hint style="info" %}
Configure the Calendar when you first build the system. This is easier than configuring it later.
{% endhint %}

### Default Calendar behavior

When a site is created there is only one Day Category by default, the **Default Day Category**, and it is applied to every day in the Calendar.

When a Channel Partner builds a new system, the recommendation is to create a Day Category for every day of the week plus at least one holiday. Applying a Day Category to the Calendar then applies the Schedules in that Day Category to the devices in Command Centre.

### Day Category allocation

First, set the day-by-day states on a Standard Access Zone schedule. Here the Holiday category is set to **Secure - PIN**, while every weekday category is **Secure - No PIN**:

![Access Zone schedule Times tab listing Day Categories (Default, Monday-Sunday, Holiday) with their State / Action; Holiday is Secure - PIN, weekdays are Secure - No PIN](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2154a3b7e5055a090d4e4b450e24bef579a76d06%2FSECHUB-CCS-CAL-DEFAULT-01-access-zone-schedule-day-categories.png?alt=media)

Then allocate those Day Categories onto the Default Calendar. The 25th and 26th of December and the 1st and 2nd of January are assigned the Holiday category (shown purple):

![Default Calendar Properties, Day Category Allocation tab, showing a November 2019 to February 2020 view with 25/26 December and 1/2 January marked as Holiday in purple](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-317429ae4c14d7597dc9dee44d728ffdaff31185%2FSECHUB-CCS-CAL-DEFAULT-02-default-calendar-day-allocation.png?alt=media)

The result: the Access Zone is in **Secure - No PIN** mode every day, except the 25th and 26th of December and the 1st and 2nd of January, where it is in **Secure - PIN**.

{% hint style="info" %}
Further examples are available in the Command Centre online help and the standard training manual.
{% endhint %}


---

# 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/products/cc-software/configure/calendars/calendars-default-calendar.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.