> 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/assigning-days-to-day-categories.md).

# Assigning Days to Day Categories

Perform the following procedure to assign days to Day Categories.

**Note:** Individual dates, (e.g. Monday 25 October) can be assigned to Day Categories on any Calendar, whereas particular days, (e.g. All Saturdays) can be assigned to Day Categories on the Default Calendar.

#### Assigning particular days to Day Categories

1. Click on the Default Calendar from the list in Viewer Navigation Panel.
2. Click the **Calendar** tab, if not already displayed.
3. Click on the Day name on the calendar.

   A browse tool displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-de8f5bea0a357ba8c65952645ccbe27343a20289%2Fdaycategoryallocation.png?alt=media)
4. Select the required Day Category and click the **OK** button.

   The pop-up closes.

   The Day name will be the colour assigned to the selected Day Category (see example below), and the **Assigned Day Categories** list on the right will show the selected Day Category beside the Day.
5. Click the **Save** button.

#### Assigning individual dates for Day Categories

1. Click on the appropriate Calendar, (i.e. either the Default Calendar or a Special Calendar), from the list in Viewer Navigation Panel.
2. Click the **Calendar** tab, if not already displayed.
3. Click on the specific date on the calendar.

   A browse tool displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-047e7c27ffa8679709939b67b65d9c0c8893dd2c%2Fdaycategoryallocation2.png?alt=media)
4. Select the required Day Category and click the **OK** button.

   The pop-up closes.

   The date will be inside a box of the colour assigned to the selected Day Category (see example below), and the **Assigned Day Categories** list on the right will show the selected Day Category beside the date.

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

   **Notes:**

   * Day Categories that have been defined in the Default Calendar will display differently in a Special Calendar, i.e. instead of a date being inside a coloured box it will be in a plain box, (e.g. 28th January in the above example), and in the **Assigned Day Categories** list it will display in *italics*.
   * There is a limit of 400 special days in the Default Calendar and 400 in each Special (regional) Calendar. This allows a total of 800 special days to be defined for any one Special Calendar. When the limit is reached, the system will remove special days in the past without warning, until all newly selected days can be added. If all special days in the past have been removed and the limit is still exceeded, the extra newly selected days will not be added and a warning message will display.


---

# 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/assigning-days-to-day-categories.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.
