> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/en/property-management/structure.md).

# Properties, floors, rooms and apartments

Open Property Profile and Floor and Room Definitions.

![Property and unit definitions](https://582852079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH3QewPp8q2H0UbFFNMYS%2Fuploads%2Fgit-blob-1c3f48db0cfc367caee91477bee69e897a87d31f%2Fproperty.png?alt=media)

## Plan the structure

The hierarchy is hotel → property/branch → floors and units. A unit may be an apartment, room, dormitory or bed. Rooms can belong to an apartment, and beds can belong to a room. The physical floor and parent unit are separate relationships; rooms within a multi-floor apartment may be on different floors.

## Create floors and units

1. Select the property and open Floor and Room Definitions.
2. Set the floor code, display name and order. Do not reuse a floor code within the same property.
3. In the unit form, select the apartment, room or dormitory type and enter its code.
4. Assign the appropriate floor and, if necessary, a parent unit.
5. Complete the rental-mode choice in the room form.
6. Add physical beds, amenities and inventory information.
7. Save and check the unit in the definitions list and the relevant operational view.

## Rent a room or individual beds?

| Choice          | Result                                                                        |
| --------------- | ----------------------------------------------------------------------------- |
| Entire room     | The room is the reservation unit; its physical beds describe the room layout. |
| Individual beds | Linked bed spaces are offered separately.                                     |

The room's rental mode also applies to beds added later. Changes that would affect existing reservations may be blocked.

## Edit or delete a definition

Edit the record to inspect its floor and parent-unit assignment. If a structural change would affect confirmed or active reservations, first move them appropriately or consider cancellation for reservations that have not checked in. Follow the application's validation rather than bypassing it.

For bulk actions, review every selected unit code. Check filters and selected rows before applying changes to multiple units.

Continue with [beds and bunk beds](/en/property-management/beds.md) and [amenities and inventory](/en/property-management/amenities.md).


---

# 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://docs.interaktifotel.com/en/property-management/structure.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.