> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kitospace.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating & Managing Units

> Learn how to create, organize, and manage units — the rooms, spaces, and apartments that everything else in Kitospace attaches to.

## What is a Unit?

A **Unit** is any individual physical or logical space you manage — a hotel room, apartment, office, parking spot, or storage locker. Units are the building blocks that reservations, rates, cleaning missions, and availability all attach to.

## Unit types and categories

Every unit has a **type** that defines its category of space, such as *Standard Room* or *Studio Apartment*. Types let you set default rates once for every unit of that type, share operational behaviour, and group units in reports.

Units can also be grouped into **categories** for extra flexibility. A category carries its own rate overrides and its own booking model — a specific unit or a shared pool — and units can be added to it individually or in bulk by type.

## How do I create a unit?

<Steps>
  <Step title="Open Units">
    Go to the **Units** section in the sidebar.
  </Step>

  <Step title="Start a new unit">
    Click **Create unit** at the top right of the page. On a phone or tablet, use the round **+** button in the bottom-right corner instead.
  </Step>

  <Step title="Fill in the basics">
    Give the unit a **name**, choose a **unit type**, and set its **capacity**.
  </Step>

  <Step title="Save">
    Click **Create**. The unit is immediately available on the **Calendar** and for bookings.
  </Step>
</Steps>

## How do I edit a unit?

Click any unit card in the **Units** explorer to open its detail view. There you can change the name and identifier, capacity, unit type, category membership, rates, and — with the reservations add-on — bookable settings. Changes appear on every staff dashboard in real time.

## Which rate applies?

Rates follow a priority order, and the most specific level wins:

1. **Unit rate** — set directly on the unit
2. **Category rate** — inherited from the unit's category
3. **Type rate** — inherited from the unit's type

If no rate is set anywhere, the effective rate is zero.

<Tip>
  Set your standard price at the **type** level so new units are priced correctly the moment they are created. Use a category rate for a group priced differently, and reserve unit-level rates for genuine one-offs — the fewer overrides you keep, the easier a price change is later.
</Tip>

## What needs an add-on?

| Feature                               | Requires            |
| ------------------------------------- | ------------------- |
| Bookable toggle                       | Reservations add-on |
| Booking model (specific unit or pool) | Reservations add-on |
| Check-in / check-out times            | Reservations add-on |
| Rate configuration                    | Reservations add-on |
| Mission assignments                   | Base platform       |
| Hierarchy (parent / child)            | Base platform       |

## Operational rules

Operational rules govern how a property behaves. They are managed from the **Manage** button on the Operational Rules card of a unit's settings page, and cover four areas:

* **Inventory** — *Overbooking Mode* (**Strict** prevents double bookings, **Flexible** allows them) and a *Conflict Threshold*, the occupancy level at which conflicts are flagged.
* **Payment** — hide payment sections on reservations when payment is handled outside Kitospace.
* **Operations** — switch missions and emergency notifications on or off, and choose an *Assignment Strategy*: **First Match** stops at the nearest parent unit with an assignee, **Accumulation** collects assignees all the way up.
* **Cleaning** — enable housekeeping, pick **Simple** or **Advanced** tracking, and auto-link cleaning tasks to missions.

<Note>
  Operational rules are set once at the top-level unit of a property and inherit down to every unit beneath it. Child units do not keep their own copy — change a rule at the top and it applies to the whole property. On a child unit the page is read-only and shows an "Inherited from …" badge linking back to where the rules are managed.
</Note>

## Check-in and check-out

Check-in and check-out times are set **per unit**, in the unit's **Check-in & Check-out** settings section — not with the operational rules. A unit uses its own times if it has them, otherwise the nearest parent unit's, otherwise the type defaults, and finally the system defaults of 15:00 and 11:00. The turnover buffer is the gap between them, and a per-unit bypass toggle allows back-to-back stays. See [Check-in & Check-out](/docs/units/check-in-checkout) for the full picture.

<Warning>
  Check-in and check-out are an atomic pair: set both or clear both. Saving only one of the two is rejected. To go back to the inherited times, clear both fields.
</Warning>

## Organizing with hierarchy

Units nest parent-to-child — a building contains floors, a floor contains rooms. This is organizational only and does not change booking behaviour.

## Related

* [Capacity](/docs/units/capacity)
* [Check-in & Check-out](/docs/units/check-in-checkout)
* [Rate Plans](/docs/units/rate-plans)
* [Inventory Pools](/docs/units/inventory-pools)