> 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/settings/organization-settings/custom-fields.md).

# Custom Fields

Define and manage custom field definitions for properties or reservations.

Custom Fields let you add extra information to your Guestway records — reservations and properties — beyond the fields that come built into the platform. Use them to capture data unique to your operation, so everything your team needs is stored inside Guestway instead of spreadsheets or notes elsewhere.

***

### What Custom Fields are for

Every business tracks something the default fields don't cover. Custom Fields give you a place to store that information where it's useful — right next to the reservation or property it relates to.

#### Property Custom Fields

Attach data that belongs to the property — set it once on a **Complex** or **Multi-Unit** and every listing beneath inherits it, or set it on an individual listing. Examples:

* Check-In / Check-Out Instructions
* Amenities that aren't standard (ski locker, sauna).

#### Reservation Custom Fields

Attach data that belongs to a specific booking, such as:

* Invoices

***

### Opening Custom Fields settings

Go to **Settings → Organization Settings → Custom Fields**.

***

### Creating a Custom Field

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/mk648j0hqr>" %}

1. On the Custom Fields page, click **Create**.
2. Enter a clear **name** — this is what will appear wherever the field is shown.
3. Choose the **value type** that matches the data you want to capture (see table below).
4. Select the **Target**: **Property** (available on every Listing, Multi-Unit and Complex) or **Reservation**.
5. Optionally mark the field as **important** to make it stand out on the record.
6. Optionally set a **default value** so new records are pre-filled.
7. Save the field.

#### Value types

| Value type  | Use it for                                                                 |
| ----------- | -------------------------------------------------------------------------- |
| **Text**    | Free-form values — names, codes, notes. Supports **@** template variables. |
| **Number**  | Numeric values like counts, prices or IDs                                  |
| **Yes/No**  | Simple yes/no flags                                                        |
| **Date**    | A calendar date                                                            |
| **Time**    | A time of day (10-minute steps)                                            |
| **Options** | A dropdown with the choices you define                                     |

> **Default value** applies only to newly created reservations. For properties it is applied to all existing listings, multi-units and complexes that don't have a value set yet.

***

### Setting a field across a whole complex

Property fields cascade **Complex → Multi-Unit → Listing**. Fill the value once on the complex and every multi-unit and listing in it shows that value until one of them sets its own; a value entered on a listing or multi-unit always takes priority over the complex.

1. Go to **Properties**, open the **Complex** tab and select the complex.
2. Open **Custom Fields** and set the value.
3. On any listing or multi-unit inside the complex, the field now reads **Inherited from** *complex name*. Override it there only where the answer genuinely differs.

The definition's detail page shows the target as **Listing / Multi-unit / Complex**. See [Custom Fields (properties)](https://docs.guestway.io/guestway-platform/properties/custom-fields) for how inheritance is shown and overridden.

#### Filtering by complex-level fields

In the **Reservations** list and the **Inbox**, the filter panel offers **Complex custom field** alongside **Listing custom field** and **Multi-unit custom field**. Pick the chip, then the field, then the value — for example every conversation in buildings where *Has\_luggage\_room* is **Yes**.

***

### Managing existing Custom Fields

The table lists **Name**, **Variable** (the code you use in templates), **Value Type**, **Target** and **Visible**.

* **Edit** a field to rename it or change its settings.
* **Archive or delete** fields that are no longer in use. Fields synced from your PMS can't be deleted — set **Visible** off to hide them instead.

Removing a field also removes the data captured in it — archive instead if you might need the values later.

***

### Tips

* **Keep field names short and consistent.** Short labels scan faster in lists and forms.
* **Pick the narrowest value type that fits.** A Yes/No field is easier to filter and report on than a free-text field when the answer is always one of two values.
* **Set building-wide answers on the Complex.** Bin day, parking instructions, luggage room — fill them once and let every listing inherit.
* **Use Important sparingly.** Flagging everything as important defeats the purpose — reserve it for the one or two fields your team must not miss.
* **Retire unused fields.** Custom Fields that aren't filled in add noise — archive them when they stop being useful.
* **Agree on conventions across your team** before rolling out new fields, so everyone captures the same data in the same way.

***

### Related pages

* [Custom Fields (properties)](https://docs.guestway.io/guestway-platform/properties/custom-fields) — fill in values on a Listing, Multi-Unit or Complex and see where they're inherited from.
* [Properties](https://docs.guestway.io/guestway-platform/properties) — overview of properties where you can edit custom fields.
* [Reservation Panel](https://docs.guestway.io/guestway-platform/reservation-panel) — where reservation Custom Fields appear and can be edited.
* [Users](https://docs.guestway.io/settings/organization-settings/users) — manage who in your organization can create and edit Custom Fields.
* [Organization Settings](https://docs.guestway.io/settings/organization-settings) — other workspace-wide configuration options.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.guestway.io/settings/organization-settings/custom-fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.