> 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-create-a-custom-field.md).

# How to create a custom field

This guide shows you how to add a custom field for your properties or reservations, so your team keeps that data in Guestway.

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

* You need the permission to edit custom field definitions. See [Users and roles](https://docs.guestway.io/account-and-administration/users-and-roles.md).
  {% endhint %}

## Create the field

{% stepper %}
{% step %}

### Open the custom fields

Go to **Settings** → **Organization** → **Custom Fields** and click **Create**.
{% endstep %}

{% step %}

### Name the field

Enter the **Name**, for example *Parking info*. The **Variable** fills in from the name. Change it now if you want: you cannot change it later.

{% hint style="success" %}
Keep names short and use the same style for all fields. Agree on the names with your team before you add many fields.
{% endhint %}
{% endstep %}

{% step %}

### Choose what it is for

In **Target**, choose **Property** for data about a listing, multi-unit or complex, or **Reservation** for data about one booking. You cannot change it later.

Add a **Description** if your team needs to know what goes in the field.
{% endstep %}

{% step %}

### Choose how it shows

Leave **Visible** on. Turn on **Important** if your team must not miss the field.

Leave **Used by AI** on if the AI can use the value when it replies to guests. Turn it off for data that the AI must not use.

{% hint style="success" %}
Keep **Important** for the one or two fields that matter most. When every field is important, none stands out.
{% endhint %}
{% endstep %}
{% endstepper %}

## Choose the value type

{% stepper %}
{% step %}

### Choose the type

In **Value Type**, choose **Text**, **Number**, **Yes / No**, **List**, **Date** or **Time**. You cannot change it later.

For **List**, type each option in **List Options** and press Enter.

{% hint style="success" %}
Choose the narrowest type that fits. When the answer is always yes or no, a **Yes / No** field is easier to filter on than a text field.
{% endhint %}
{% endstep %}

{% step %}

### Add a default value

If most records have the same value, enter a **Default Value**. For reservations, it applies only to new reservations. For properties, it applies to all properties without a value.
{% endstep %}

{% step %}

### Save the field

Click **Create**. You see *Successfully created!*, and the form is ready for the next field.

Next, fill in the values on the **Custom Fields** tab of your properties, or on the reservations in the inbox.
{% endstep %}
{% endstepper %}

## Related

* [Custom fields](https://docs.guestway.io/properties/custom-fields.md): all fields and value types
* [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)
* [Property custom fields](https://docs.guestway.io/properties/custom-fields/property-custom-fields.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-create-a-custom-field.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.
