Email fields store one email address as text and validate it with email-specific rules. They are used for contact addresses, notification recipients, or external account identifiers.
Use an email field instead of a normal text field when the value should be checked as an email address.
Basic Settings
| Setting | Description |
|---|---|
| Name | The field label shown to users. It is required and should describe whose email address is collected |
| API Name | The stable technical name used by data APIs, scripts, formulas, imports, and integrations. It is required |
| Required | Requires users to enter an email address before the record can be saved |
| Readonly | Shows the email address but prevents users from changing it |
| Disabled | Makes the field unavailable for normal use |
| Hidden | Stores the email address while hiding it from normal form pages |
Email Field Config
| Setting | Description |
|---|---|
| Suggested Domains | Configures domain suffixes suggested to users, such as gmail.com or company.com |
| Add Domain | Adds one domain suffix to the suggested domain list. Enter only the domain suffix, not a full email address |
| Placeholder | Prompt text shown before users enter an email address |
| Input Status | Adds a visual status to the field, such as warning or error |
| Validate Trigger | Controls when email validation runs: when the value changes, when the field loses focus, or when the record is submitted |
| Allow Custom Domain | Allows users to enter domains outside the configured domain list |
| Invalid Email Message | Custom message shown when the value is not a valid email address |
| Invalid Domain Message | Custom message shown when custom domains are disabled and the entered domain is not allowed |
| Field Color | Sets the display color used for the field |
| Help Text | Helper copy shown near the field. Use it to explain which email address users should provide |
Domain Settings
| Setting | Description |
|---|---|
| Suggested domain | A suffix such as qq.com, gmail.com, or company.com. Runtime can use it to help users complete the email address |
| Custom domain enabled | Users may enter any valid email domain. Suggested domains are still useful as shortcuts |
| Custom domain disabled | Users must use one of the configured valid domains. At least one valid domain must be configured |
Common Examples
| Scenario | Suggested Domains | Custom Domain |
|---|---|---|
| Internal employee email | company.com | Disabled |
| Customer email | gmail.com, outlook.com, qq.com | Enabled |
| Partner account email | partner.com, company.com | Enabled |
Configuration Tips
| Tip | Description |
|---|---|
| Use domain suffixes only | Enter company.com, not name@company.com |
| Disable custom domains for internal-only fields | This keeps the field limited to approved company domains |
| Write separate invalid messages | Use one message for invalid email format and another for disallowed domains |