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

# Creating a Day Category

Perform the following procedure to create a new Day Category:

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

   The new Day Category is added to the Viewer Navigation Panel, and the Day Category Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-aeae1e2aec05126b1acd30d93213b21c26b16a5a%2Fdaycategoryconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the day category, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. Click the **Close** button.

   The Day Category Configuration pop-up closes.
5. There are two tabs, (i.e. **Colour** and **History/Notes** ). The **Colour** tab displays by default.
6. To change the colour, click on the required colour square from the displayed colour swatch under **Standard Colours**.

   The selected colour displays in the large **Colour** square, and the RGB (Red, Green, Blue) values of the colour display beside it.
7. If you want to record any note(s) about the Day Category, 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 Day Category has been created.

### Hints

{% hint style="info" %}
**Editing and Deleting Day Categories**

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 Day Categories.
{% endhint %}

{% hint style="info" %}
**Duplicating Day Categories**

Operators privileged to create Day Categories can also duplicate Day Categories, which makes the task of setting up multiple Day Categories 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-day-category.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.
