# Full Name Fields

Full Name fields are designated to store first and last names, as well as optional Titles (such as Mr, Ms, Mrs etc.) and optional middle names. This makes them a great candidate for managing client and employee names. When used in text, the individual values are joined together as you would expect to see them written.

## Name Components

A Full Name field can store:

* **Title** (optional): Mr, Ms, Mrs, Dr, etc.
* **First Name** (required)
* **Middle Name** (optional)
* **Last Name** (required)

## Display Format

Names are automatically formatted and displayed as a complete name string, following standard naming conventions (e.g., "Dr. John Michael Smith" or "Jane Doe").

## Use Cases

Full Name fields are ideal for:

* Employee and staff directories
* Client and customer records
* Contact management systems
* User profiles and accounts
* Event attendee lists
* Professional directories

## Advantages Over Separate Text Fields

Using Full Name fields instead of separate first/last name fields provides:

* Consistent name formatting across your application
* Better sorting and searching capabilities
* Proper handling of titles and middle names
* Reduced data entry errors
* Automatic name display in forms and views

## Best Practices

* Use Full Name fields for any person-related data where you need professional name display
* Consider cultural naming conventions for your user base
* Full Name fields work well with [User tables](/users-and-permissions/user-table.md) and user management
* Use in combination with other contact fields like [Phone Numbers](/data/collections/field-types/phone-number.md) and email addresses


---

# Agent Instructions: 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:

```
GET https://guides.noloco.io/data/collections/field-types/full-name.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.