> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/standard-form-fields.md).

# Standard Form Fields

Choose which standard fields your Action Page form shows and requires: name, email, phone, address, employment, and organization, by page type.

**Standard fields** are the built-in contact fields on your Action Page form, such as name, email and address. You set them in the Page Builder under **Page > Form**, in the **Form fields** panel. This article covers each standard field, what you can change on each page type, and how required fields work.

## Open the Form Panel

To open the Form panel:

1. Go to **Action Pages > Pages**.
2. Hover over the page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Page > Form**.

Expand a field to change its settings. Check **Required field** to make donors fill it in, where the page type allows.

## Standard Fields

* **Name:** First and last name, with an optional Title.
* **Email:** Shown and required on new pages.
* **Phone:** Shown and optional on new pages. You can change the field label.
* **Address:** You can change the address label and which countries are allowed.
* **Employment:** Occupation, Employer name and Employer address. Off until you add it. Set Required on each field inside the block.
* **Organization:** Organization name and type. Off until you add it.

When **Employment** is on, donors are asked whether they're currently employed. Occupation and employer fields are checked only when a donor says yes.

## What You Can Change by Page Type

| Setting                           | Donation                  | Event                          | Lead                  |
| --------------------------------- | ------------------------- | ------------------------------ | --------------------- |
| Name always required              | Yes                       | Yes                            | No                    |
| Address always shown and required | Yes                       | Yes                            | No                    |
| Email always shown                | Yes                       | Yes                            | No                    |
| Remove a standard field           | Phone and Employment only | No for name, email and address | Any field except Name |
| Reorder standard fields           | No                        | Yes                            | Yes                   |

{% hint style="info" %}
On Donation Pages, the order is fixed: name, email and phone, then address, then Employment.
{% endhint %}

## Email or Phone

If neither Email nor Phone is required, donors must enter at least one of them. The field row shows "Email or phone required" when this rule applies.

## Custom Fields Placement

Custom fields appear after the standard fields by default. Once your page has a custom field, use the arrows on the **Standard fields** and **Custom fields** sections to move all custom fields above the standard fields. See [Custom Form Fields](/action-pages/page-builder/custom-form-fields.md).

When you're done, click **Save**.

## Troubleshooting

"Email must be displayed if required" or a similar message appears when you save. A field is set to required but isn't shown. Show the field or clear **Required field**, then save again.

## Related Articles

* [Custom Form Fields](/action-pages/page-builder/custom-form-fields.md)
* [Hidden Fields](/action-pages/page-builder/hidden-fields.md)
* [Page Builder Overview](/action-pages/page-builder.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.anedot.com/action-pages/page-builder/standard-form-fields.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.