> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/build/organising-the-platform/calendar-settings.md).

# Calendar Settings

Set the working days, default view, slot duration, public holidays and non-working days used by every calendar view of your workspace.

The calendar settings define how the [calendar view](https://www.center.daxium-air.com/user-documentation/use/views/calendar.md) looks for everyone in your [workspace](https://www.center.daxium-air.com/user-documentation/components-concepts-terminology.md#workspace): which days are worked, which days the calendar shows when it opens, how long a time slot lasts, and which days are public holidays or non-working days.

These settings are shared. They apply to every calendar view of the workspace, in every display mode (Agenda, Week, Month and Timeline), for all [users](https://www.center.daxium-air.com/user-documentation/components-concepts-terminology.md#user), on the web and on mobile. The default view and the slot duration are starting points: users can [adjust them from the calendar view](https://www.center.daxium-air.com/user-documentation/use/views/calendar.md#adjust-the-display).

{% hint style="info" %}
Only administrators can change the calendar settings.
{% endhint %}

## Open the calendar settings

In the back office, go to **Settings > General > Calendar**.

A banner at the top of the page reminds you that the configuration applies to all the calendar views of your workspace.

<figure><img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2F0oVLkrqVz7hNCSKjqRY0%2Fimage.png?alt=media&amp;token=d165e401-fd29-475d-b7e0-cdbc3da438de" alt=""><figcaption></figcaption></figure>

## Configuration

<figure><img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2FOkpp8UMa75r3HTrIyNnE%2Fimage.png?alt=media&amp;token=c1fa03ee-a596-49e8-86c1-76fd4877b062" alt=""><figcaption></figcaption></figure>

### Working days

Select the days of the week that your teams usually work. A selected day is highlighted, and a counter next to the label shows how many days are selected (for example **5/7**). By default, Monday to Friday are selected.

### Default view

Choose which days are visible when a user opens the calendar:

* **All days**: the calendar shows the whole week.
* **Working days only**: the calendar shows only the [working days](#working-days) you selected.

### Default slot duration

Set the standard duration of each time slot in the calendar grid: **30 min**, **1h** or **2h**. A shorter slot gives a more detailed grid; a longer one fits a whole day on screen. The default is **30 min**.

### Save your changes

Changes to the configuration are not saved automatically. Click **Save** to apply them to every calendar view of the workspace. The button is only active when you have unsaved changes.

## Public holidays and non-working days

This section lists the days off of your workspace, year by year. Use the arrows on either side of the year to move to the previous or next year. These days are flagged in every calendar view, so your teams can see at a glance when not to schedule work. They also apply to the task view (see [Tasks](https://www.center.daxium-air.com/user-documentation/build/building-forms/tasks.md)).

<figure><img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2FGi3FNMpTjna1Xdxi8SAV%2Fimage.png?alt=media&amp;token=be08aa6d-4d48-4b8b-8b27-98f48ea9e04f" alt=""><figcaption></figcaption></figure>

### Add a day

Click the **+** button at the top right of the section. In the **Add a day** window:

<figure><img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Friaj28L7r99BhgqOEimk%2Fimage.png?alt=media&amp;token=3cec0bfd-71f8-4e0a-9dfe-e01dd765e0c4" alt="" width="326"><figcaption></figcaption></figure>

1. Leave **Active** on so that the day is applied to the calendars. Turn it off to keep the day in the list without applying it.
2. Enter a **Name**, for example "National holiday". This name is required.
3. Choose its **Type**: **Public holiday** or **Non-working day**.
4. Pick the **Date**. To cover several consecutive days, tick **Date range** and pick a start and an end date.
5. For a day that falls on the same date every year, such as New Year's Day, tick **Repeat every year** and choose for how many years (5 by default). Daxium-Air creates one occurrence per year, so you don't have to add the day again each year.
6. Click **Add**.

The new day appears in the list under its year.

### Edit or delete a day

Each day in the list shows its name, its date, its type and whether it is active. Administrators can change it with the pencil icon, or delete it with the bin icon. Deleting a day removes it from the calendar views of the whole workspace.

<figure><img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2FGLgjh7T5TBXoE2cL2Bz4%2Fimage.png?alt=media&amp;token=fd96579e-690b-42ab-a51c-21e18d99d5b4" alt=""><figcaption></figcaption></figure>


---

# 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://www.center.daxium-air.com/user-documentation/build/organising-the-platform/calendar-settings.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.
