> 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/calendars-and-day-categories/creating-a-special-calendar.md).

# Creating a Special Calendar

Perform the following procedure to create a special Calendar:

1. Click the **New Calendar or Day Category** button on the Viewer Navigation Panel, and then select **Special Calendar**.

   The new special calendar is added to the Viewer Navigation Panel, and the Special Calendar Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-09ad9485c46c37c79d47af8613df685c2f6cc1ac%2Fspecialcalendarconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the calendar, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this calendar to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-b59df7c2a078bd54f6c17dd30b3ce00d3e5b1279%2Fselectdivisionforreport_popup.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your calendar at a later stage.
5. Click the **Close** button.

   The Special Calendar Configuration pop-up closes.
6. There are two tabs, (i.e. **Calendar** and **History/Notes** ). The **Calendar** tab displays by default.

   Configure the Special Calendar as required. See [Assigning Days to Day Categories](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/calendars-and-day-categories/assigning-days-to-day-categories.md) for further details.
7. If you want to record any note(s) about the Special Calendar, click the **History/Notes** tab.

   Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
8. Click the **Save** button.

   A new Special Calendar has been created.

### Hints

{% hint style="info" %}
**Editing and Deleting Special Calendars**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Special Calendars.
{% endhint %}

{% hint style="info" %}
**Duplicating Special Calendars**

Operators privileged to create special Calendars can also duplicate special Calendars, which makes the task of setting up multiple special Calendars that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% 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/command-centre-client/configuring-command-centre/administration/calendars-and-day-categories/creating-a-special-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.
