> For the complete documentation index, see [llms.txt](https://hotelizer.gitbook.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hotelizer.gitbook.io/manual/en/menu/calendar.md).

# Calendar

## Basic functions 

![Reservation Plan ](/files/-MctuRlOSpqYECRylfv4)

1. **Basic navigation** of the Calendar. Here you can move the booking plan to any period you want to see.
2. **Search** for reservations by entering the reservation code or customer name. The plan will be automatically moved to the reservation you will find which will be highlighted in red so you can easily find it in the plan.
3. **Reservation plan settings.** Ηere you can change the outlook of the plan. These settings are saved for your user only and do not affect others. So each user can see the plan differently.
4. With this option, can you adjust the **height** of the cells in your plan.
5. “**Actions**”, has three options: 
   1. Add a reservation 
   2. Restrict availability to rooms of your choice and on any dates
   3. Change the room rates 
6. Rooms 
7. Automatic **Parked line**. Here are the reservations you have, but which have **not** been placed in a specific room. However, they continue to **count normally** in the calculation of availability.
8. By clicking & drag at this point you can change the length of the room column.
9. By **dragging & dropping the 3 dots** in a room & moving on the vertical axis you can **change** the order of the rooms **in the plan**.

## NAVIGATION 

![Basic navigation of the booking plan](/files/-Mctz-jGPHHN8QJc-0lv)

1. Moving the plan one year back
2. Moving the plan one day before 
3. Selected period
4. Adjust the space you want to see in your plan. E.g. you are given the opportunity to adjust your plan per week, 14 days, 20 days, 31 days and 45 days.
5. Moving the plan one day after
6. Moving the plan one year ahead
7. You can select and move the plan to the month of your choice
8. Choose the specific dates 

## COLORS

A reservation in the shot may appear in a specific color for a variety of reasons. You can control the appearance of colors from the shot settings.

#### Reservation status 

* When a reservation is **blue** it means that they are **in-house guests**.
* When a reservation is **green** it means that it is a **confirmed** reservation and we are waiting for it at the accommodation..
* When a reservation is **red** it means that it has **left the property** and we have checked it out.
* When a reservation is **yellow** it means it is **optional**, if we are not sure when exactly it will come to the property. In this case, when we do not know when the customer will come, we can move the reservation to the "parked" option, until the confirmation is made by him.

#### Source

The color of the reservation may come from the source of the reservation. Each source also has a specific color which you can change from the settings (Settings / Channels / Sources)

#### Company color

If this reservation has been associated with an agent or company and it has some color in its profile then this color will also appear in the shot.

#### Tags

If you have added a tag to the reservation then the color you have assigned will be displayed.


---

# 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:

```
GET https://hotelizer.gitbook.io/manual/en/menu/calendar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.