> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mileapp.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Address

The **Address** input type enables field workers to enter a free-text address as part of a task.

## What is the Address Input?

Address captures a multi-line text string representing a physical location. Unlike the [Coordinate](/pages/flow/flow-builder/component-input-type/coordinate) component, Address has no GPS or geofencing features — it is a passive text field that stores whatever the worker types.

**Use Cases:**

* **Delivery address display**: Show the customer's address on the task card and mobile form
* **Import source for geocoding**: Provide the address during task import and let the system convert it to coordinates automatically
* **Manual address entry**: Allow workers to record a location in plain text when GPS is not required

## Address Properties

<div align="center">
  <img src="https://mintcdn.com/mileapp-c1584fbc/cprHypGBbOUqZvYy/images/component-input-address.png?fit=max&auto=format&n=cprHypGBbOUqZvYy&q=85&s=bece74fd096958a80177570f4859b152" alt="Address component configuration" width="600" data-path="images/component-input-address.png" />
</div>

**Address type of input settings:**

1. **Title** — Component label shown to field workers (e.g., "Customer Address", "Address User")
2. **Type of Input** — Set to Address
3. **Default Value** — Pre-filled address text. A task created with this flow will use this value unless overridden. Supports multiple lines.
4. **Required** — If on, the field must be filled before page completion
5. **Visible** — Controls display on Create Task (web and mobile) and View Task (mobile).

Address has no Geolock or Geocode settings. Those are configured on the [Coordinate](/pages/flow/flow-builder/component-input-type/coordinate) component that references this field.

## How to Configure Address

### Step 1: Add the Component

In the Flow Builder, click **Add Component** on the target page. Set **Component Type** to **Input** and **Type Of Input** to **Address**.

### Step 2: Set Basic Properties

Enter the component **Title** (e.g., "Customer Address"). Toggle **Required** and **Visible** as needed. Optionally enter a **Default Value** — this is a multi-line textarea.

### Step 3: Configure Show As (optional)

In the **Configuration** section:

* Set **Show As** to `content` — the address text appears as the main description line on the task card in the task list.
* Set **Show As** to `title` — the address text appears as the task's title (use only when there is no dedicated name field).
* Set **Show As** to `label` — the address appears as a smaller label on the task card.

### Step 4: Link to a Coordinate component (optional)

Address itself requires no additional setup for geocoding. To enable automatic coordinate population from this address:

1. Add a **Coordinate** component to the same flow.
2. Open the Coordinate component's settings.
3. Toggle **Geocode** on and select this Address component in **Generate Coordinate From**.

Once linked, the Coordinate component drives the relationship — auto-populated during task import when address text is provided.

## How Address Works in Tasks

When a field worker opens a task on the mobile app:

1. The Address field shows a **multi-line text area** with placeholder text
2. The worker can type freely, or the field may already be populated:
   * **From task creation**: If the task was created with an address value (e.g., from Data Source or manual entry), the field is pre-filled
3. The worker can edit the text before completing the page

## Related

* [Coordinate Component](/pages/flow/flow-builder/component-input-type/coordinate) — GPS input that can be auto-populated from this Address field via Geocode
* [Configuration: Task List](/pages/flow/flow-builder/configuration-task-list) — Setting `Show As: content` for address display on task cards
* [Input Component Overview](/pages/flow/flow-builder/component-input-type/component-input)