> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/properties/general/about-property-types.md).

# About property types

This page explains why Guestway sorts your properties into four levels, and why you set most things once on the highest level that fits.

## Four levels, from the organization to one unit

Guestway sorts your properties into four levels. **Global** is your whole organization. A **complex** is a building or a site with several units. A **multi-unit** groups units inside it, for example a floor or a block of the same kind of unit. A **listing** is one unit that guests book.

Not every property has every level: a single holiday home is just a listing.

## Why settings flow down

Much of what guests need to know is the same for many units. The Wi-Fi of a building, the bin day, the parking, the house rules and the deposit rarely change from one unit to the next. If every listing kept its own copy, one change would mean editing dozens of pages, and one forgotten copy would give a guest the wrong answer.

That is why most settings flow down. Custom field values, the billing account, the default security deposit and checklists are inherited from the level above when a property has none of its own. Guidebooks and saved replies linked to a level show on every property below it. You change the answer in one place, and every unit follows.

## Where to set something

A good rule: set a value on the highest level where it is true, and make an exception only where the answer really differs. A building handbook belongs on the complex. Floor-specific details belong on the multi-unit. Only what is unique to one unit belongs on the listing.

The product shows where a value comes from with **Inherited from**, so an exception stays easy to spot. An exception also stops following the level above. That is why it is worth keeping exceptions few: each one is a place you must remember when the standard changes.

## What stays on one level

Some things only make sense for the unit a guest stays in. The address, the Wi-Fi details and the room details belong to the listing, and the marketing name belongs to what guests book: a listing or a multi-unit. A complex has none of these, because guests never book a building as a whole.

## Related

* [General](https://docs.guestway.io/properties/general.md): the levels and the tabs of each level
* [Property custom fields](https://docs.guestway.io/properties/custom-fields/property-custom-fields.md#inheritance)
* [How to set a custom field for a whole complex](https://docs.guestway.io/properties/custom-fields/how-to-set-a-custom-field-for-a-whole-complex.md)
* [About checklists](https://docs.guestway.io/properties/checklists/about-checklists.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.guestway.io/properties/general/about-property-types.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.
