> 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/custom-fields/how-to-set-a-custom-field-for-a-whole-complex.md).

# How to set a custom field for a whole complex

This guide shows you how to fill in a property custom field once on a complex, so every multi-unit and listing in it uses that value.

{% hint style="info" %}
**Before you start**

* The custom field must have the target **Property**. See [How to create a custom field](https://docs.guestway.io/properties/custom-fields/how-to-create-a-custom-field.md).
  {% endhint %}

## Set the value on the complex

{% stepper %}
{% step %}

### Open the complex

Go to **Properties**, open the **Complex** level and select the complex. Open the **Custom Fields** tab.
{% endstep %}

{% step %}

### Enter the value

Click the field, enter the value and click **Save**.

{% hint style="success" %}
Put everything that is the same for the whole building on the complex, for example the bin day, the parking or the luggage room.
{% endhint %}
{% endstep %}

{% step %}

### Check a listing

Open a listing of the complex and its **Custom Fields** tab. The field shows the value with **Inherited from** and the name of the complex.
{% endstep %}

{% step %}

### Make an exception where needed

If one listing or multi-unit has a different answer, click the field there, turn off **Use parent value** and enter its own value. A multi-unit value wins over the complex value.
{% endstep %}
{% endstepper %}

## Filter by complex-level fields

{% stepper %}
{% step %}

### Add the filter

In the inbox or in **Reservations**, open the filters and choose **Complex custom field**.
{% endstep %}

{% step %}

### Choose the field and the value

Choose the field, then the value. For example, *Has luggage room* is **Yes** shows the conversations in all buildings with a luggage room.
{% endstep %}
{% endstepper %}

## Related

* [Property custom fields](https://docs.guestway.io/properties/custom-fields/property-custom-fields.md#inheritance): how inheritance works
* [Custom fields](https://docs.guestway.io/properties/custom-fields.md)
* [How to filter conversations and save a view](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/how-to-filter-conversations-and-save-a-view.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/custom-fields/how-to-set-a-custom-field-for-a-whole-complex.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.
