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

# Field types

> The typed custom fields available on Accounts, Contacts, and Projects, and when to use each.

Custom fields are typed. The field type tells Parley how to validate, store, display, and use the value — which is what makes the field usable by agents rather than just readable by people.

| Type              | Use it for                                         | Instead of                                    |
| ----------------- | -------------------------------------------------- | --------------------------------------------- |
| **Text**          | Labels, identifiers, short descriptions            | A note, when the content is long or narrative |
| **Number**        | Counts, amounts, scores, measurements              | Text, when arithmetic or sorting matters      |
| **Boolean**       | Clear yes/no facts                                 | A status string that means yes or no          |
| **Date**          | Deadlines, expiration dates, target dates          | Text dates that can't be sorted or filtered   |
| **Datetime**      | Appointments, filing events                        | A date, when time of day matters              |
| **Email**         | A structured email address on the record           | Copying an exchange into a field              |
| **URL**           | A website, portal link, durable external reference | Text                                          |
| **Address**       | A durable postal address on the record             | A note, for explanations or proof of address  |
| **Single-select** | One controlled value from a defined set            | Free text that drifts in spelling             |
| **Collection**    | Tags, categories, languages — repeatable values    | Single-select, when more than one applies     |

## Notes on the trickier ones

### Text

Free-form text for short facts that don't require a stricter format. Use a note instead when the content is long, narrative, or intended to preserve context.

### Number

Use a number when arithmetic, comparison, or sorting matters. Don't store numeric values in text if the value will be used operationally — it will sort alphabetically and break every report it appears in.

### Date and datetime

Dates represent calendar dates; datetimes represent a date and a time. Use a datetime when the time of day matters, such as an appointment or a filing event.

### Email

Use this for a structured email address when the address is an attribute of the record. For the correspondence itself, use email activity or the relevant source record rather than copying the exchange into a field.

### Address

Use an address field when the address is a durable attribute of the record. Use a file or note for explanations about the address, or proof of it.

### Single-select

One value from a predefined set — `New`, `In Progress`, `Filed`, `Closed`.

Because the options are defined centrally, single-select fields eliminate spelling variations and make filtering and reporting reliable. This is the type that most often rescues a messy workspace.

### Collection

A set of values rather than one. Use a collection when the record may have more than one value; use single-select when exactly one controlled value should apply.

## Creating fields

Owners and Admins create fields. Tell the Agent what you want:

> "Add a Matter Number field to Projects and a Max-Out Date field to Contacts."

Parley attaches them to your Projects, Accounts, and Contacts. You can also add and edit them directly in Settings. The fields Parley ships with are there for inspiration — they're fully flexible to how your firm runs.

See [Permissions](/admin/permissions).