> 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/guestway-platform/properties/custom-fields.md).

# Custom Fields

The **Custom Fields** tab on a property shows every property-level [Custom Field](https://docs.guestway.io/settings/organization-settings/custom-fields) defined for your organisation, with the current value for this Listing, Multi-Unit, or Complex. This is where you fill in the data — the field definitions themselves are managed under **Settings → Organization Settings → Custom Fields**.

<figure><img src="https://3944456244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBrW4TrHoVgRLXkGBzLVy%2Fuploads%2FwWy1EVJlX4MECrIpNZkD%2Fimage.png?alt=media&amp;token=a95d380c-6064-49e6-b231-ae25e2e32593" alt=""><figcaption></figcaption></figure>

***

### What the tab shows

Open the **Custom Fields** tab on any Listing, Multi-Unit, or Complex to see every property-targeting Custom Field your organisation has configured. The header carries a count — *Custom Fields (12)* — so you know how many definitions apply at this level.

For each field, the tab shows:

* The field **name** as defined in [Custom Fields settings](https://docs.guestway.io/settings/organization-settings/custom-fields).
* An **info icon** beside the name with the field's description (when one is set), shown on hover.
* A **star icon** when the field is flagged as **Important** in settings.
* The **current value** for this property, formatted for the field's value type.
* An **Inherited from** footer when the value comes from the parent multi-unit or complex (see below).

If a field has no value, the row is left blank.

***

### Editing a value

Update a Custom Field value directly on the property — changes apply only to this property and propagate everywhere the field is referenced (the Listing tab in the [Unified AI Inbox](https://docs.guestway.io/guestway-platform/unified-ai-inbox), reports, integrations, etc.).

The input control depends on the field's value type:

| Value type  | Control                                                     |
| ----------- | ----------------------------------------------------------- |
| **Text**    | Rich-text editor — type **@** to insert template variables. |
| **Number**  | Numeric input.                                              |
| **Yes/No**  | Yes/No selector.                                            |
| **Date**    | Date picker.                                                |
| **Time**    | Time selector (10-minute increments).                       |
| **Options** | Dropdown showing the choices configured for the field.      |

For details on configuring fields and choosing value types, see [Custom Fields settings](https://docs.guestway.io/settings/organization-settings/custom-fields).

***

### Value inheritance and overrides

Custom Field values cascade **Complex → Multi-Unit → Listing**. A listing shows its own value if it has one; otherwise its multi-unit's value; otherwise the complex's value. Multi-unit beats complex when both are set.

The state is shown on each field card:

* **Inherited from** *name* — the card's footer names the parent whose value is shown, with an arrow icon. Click the name to open that multi-unit or complex.
* **No footer** — the value is set on this property itself.

To change a value, open the field:

| Control                       | What it does                                                                                                                           |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Use parent value** (toggle) | On: this property follows the parent. Off: enter a value of your own.                                                                  |
| **Override** *parent name*    | Shown while editing when a parent value exists; compares the parent's value with yours so you can confirm the override is intentional. |
| **Use parent value** (button) | Discards your own value and returns to inheriting.                                                                                     |

Hovering the inheritance icon in the inbox's Listing tab shows the same comparison: *The custom field `code` inherited value from complex:* followed by the **Complex:** and **Listing:** rows.

Use the cascade to set building-wide answers once (`Has_luggage_room`, parking instructions, bin day) at the **Complex** level, floor- or block-specific answers on the **Multi-Unit**, and override on the **Listing** only where the answer is genuinely different.

***

### Integration-managed fields

Some Custom Fields are populated and kept in sync by an external integration. When that's the case, the input is disabled and a tooltip explains: *"This field is managed by an integration and cannot be edited here."* To change the value, edit it in the source system — Guestway will re-sync.

***

### Tips

* **Define once, fill in everywhere.** Create the definition in [Custom Fields settings](https://docs.guestway.io/settings/organization-settings/custom-fields), then fill values from each property's Custom Fields tab.
* **Set defaults at the highest level that's true.** Anything identical across a building belongs on the **Complex**; anything identical across a block belongs on the **Multi-Unit**. Listings inherit for free.
* **Override only when you have to.** A listing-level override should be a deliberate choice — the **Inherited from** footer makes overrides easy to spot during reviews.
* **Lean on Important.** Fields flagged Important display a star, which is a fast visual cue when scanning a long list.
* **Keep field names short and consistent.** Short labels scan faster, especially when the same fields surface on the Listing tab inside the [Unified AI Inbox](https://docs.guestway.io/guestway-platform/unified-ai-inbox).
* **Filter custom fields by their values** — including **date**, **time**, and **dropdown (Options)** fields, and **Complex custom field** values — to find the reservations or conversations you need.
* Use the **search box** at the top of the list to find a custom field by name.

***

### Related pages

* [Custom Fields settings](https://docs.guestway.io/settings/organization-settings/custom-fields) — define new Custom Fields, choose value types, and manage existing definitions.
* [Properties](https://docs.guestway.io/guestway-platform/properties) — the hub for listing-level configuration.
* [General (Listings Details)](https://docs.guestway.io/guestway-platform/properties/general-listings-details) — the listing settings shown alongside Custom Fields.
* [Unified AI Inbox](https://docs.guestway.io/guestway-platform/unified-ai-inbox) — where property-level Custom Fields surface on the Listing tab during conversations.
* [Reservation Panel](https://docs.guestway.io/guestway-platform/reservation-panel) — where reservation-level Custom Fields appear and can be edited.


---

# 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/guestway-platform/properties/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.
