> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/configuration/dropdowns/calendar.md).

# Calendar

The calendars used within GLPI are configurable by entity. They are characterized by periods of opening as well as periods of closing.

These calendars are used in the `SLA` (see Configure SLAs) and the [configuration of entities](/documentation/modules/administration/entities.md).

## Calendar

### Time ranges

Corresponds to the opening time slots of the entity. You can add as many as necessary per day as long as these slots do not overlap.

### Close times

Lists the closing periods assigned to this calendar and allows you to add a new one; see [lca configuration of closing periods](#conf-close-periods).

## All Information

For an item, all information is displayed on one page from the *All* tab. This shows all of the tabs of an object's form in one view, one below the other.

## Close times <a href="#conf-close-periods" id="conf-close-periods"></a>

The list of closure periods is a flat list of valid values. It can be delegated by entity.

A closure period consists of a name, a period and whether this closure is recurring or not.

Concerning the field Recurring, if it is in Yes it means that the period indicated is valid all the time. In this case GLPI would not care about the year indicated.

Very useful to indicate the holidays recurring each year (Christmas, Victory of 1945, May 1 ...) or the period of closure of the company (closed every year from 1 to 31 August) and especially it avoids re-entering the same dates each year.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.glpi-project.org/documentation/modules/configuration/dropdowns/calendar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.