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

# Hotels and room types

> Add the properties you contract rooms with, manage each hotel's room types, and archive what is no longer taking bookings.

The **Hotels** page lists the properties housing is arranged at for this event. Hotels are the foundation of the module: [room blocks](/en/housing/room-blocks) and [stays](/en/housing/stays) both build on a hotel and one of its room types.

## Add a hotel

<Steps>
  <Step title="Click Add hotel">
    Name the property — "Hilton Kuala Lumpur". That is all the dialog asks; everything else is configured on the hotel's page.
  </Step>

  <Step title="Fill in the property details">
    On the hotel's page: the address, and the hotel's **time zone** — by default it follows the event's, but a hotel in another city can carry its own, so stay nights mean the hotel's local nights.
  </Step>
</Steps>

<Note>
  The **external provider** and **external property ID** fields exist for hotels synced with an outside housing system. Leave them empty when the hotel is managed here — which is the normal case.
</Note>

## Room types

A **room type** — Deluxe King, Twin — is the unit housing is managed in. It is a kind of room, never a specific room: blocks contract counts of a room type per night, and stays reserve a room type, not a door number.

Room types are created and edited **on their hotel's page**:

* **Name** — what the contract calls it.
* **Sleeps** — how many guests one room takes. This capacity is **informational**: it helps you place people sensibly, but nothing enforces it. A stay's guest list can be whatever reality is.

<Tip>
  Create exactly the room types your contract names, with the contract's wording — the rooming list you export later will use these names, and the hotel should recognize them.
</Tip>

## Archiving

Hotels and room types are **archived**, never deleted:

* An **archived hotel** keeps its room blocks and stays but takes no new ones — history stays intact and answerable.
* An **archived room type** likewise takes no new blocks or stays; existing ones keep their reference.
* **Restore** brings either back into use.

Archive a hotel when the contract falls through or the property is no longer used for this event; the stays already placed there remain on record.

## Rules to know

* Room types live on their hotel's page — that is the only place they are created and edited.
* "Sleeps" is informational; nothing counts guests against it.
* Archived hotels and room types keep all existing blocks and stays but accept no new ones.
* Nothing in housing is ever deleted — archiving is how things end.
* Every operation on a hotel and its room types is recorded in the event's [audit log](/en/events/settings).