> 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**.
***
### 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.
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 from **Multi-Unit → Listing**. A listing inherits the value set on its parent multi-unit unless you override it at the listing level.
Two icons make the inheritance state visible next to a value:
* **Inherited** — when a listing has no value of its own and is showing the multi-unit's value, a small arrow icon appears. Hover it to see where the value came from.
* **Overridden** — when both the listing and the multi-unit carry a value and they differ, the same arrow icon appears with a popover comparing both values side by side, so you can confirm the override is intentional.
Use this to set sensible defaults at the multi-unit level (for example, `Has_luggage_room`) and only override on the listings 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 multi-unit level.** Anything that's the same across a building belongs on the multi-unit, so listings inherit it for free.
* **Override only when you have to.** A listing-level override should be a deliberate choice — the inheritance icon makes those 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).
***
### 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=&goal=
```
`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.