Share your feature requests anytime
Search icon Our Plugins

Configuring form fields

After selecting which fields are available in your form, Forms RB allows you to configure how those fields behave for users and how their data is handled in submissions.

This article explains how field configuration works and what you can control at the field level.


Where field configuration happens

Field configuration is managed inside the Fields tab of the form editor.

Each field can be:

  • Enabled or disabled
  • Configured individually
  • Included or excluded from form submissions

All changes are saved per form and applied instantly after saving.


Field visibility and availability

Each field has a simple toggle switch:

  • Enabled — the field is displayed in the form dialog and included in submissions
  • Disabled — the field is hidden from users and ignored during submission

At least one field must be enabled for a form to be published.


Field labels and meaning

Each field has a predefined label that is shown to users (for example: Name, Email, Message).

These labels:

  • Appear directly above or inside the input field
  • Are used when displaying submission details in the admin panel
  • Help identify submitted data clearly when reviewing records

Field labels are consistent across the form and submission records.


Required vs optional fields

By enabling or disabling specific fields, you control which information is required from users.

Common configurations include:

  • Requiring Name and Email for contact forms
  • Making Phone or Priority optional
  • Enforcing Agreement fields for legal compliance

This allows you to keep forms minimal while collecting only necessary data.


Field impact on submissions

Only enabled fields:

  • Appear in the form dialog
  • Are validated during submission
  • Are saved in form records
  • Are visible when viewing submission details

Disabled fields do not exist from the submission perspective and do not leave empty values in records.


Reset button behavior

The Reset button can be enabled or disabled like any other field.

When enabled:

  • Users can clear all form inputs before submitting
  • The form returns to its initial state

This option is useful for longer forms or forms with multiple optional fields.


Best practices for field configuration

To keep forms user-friendly:

  • Enable only the fields you truly need
  • Avoid overwhelming users with unnecessary inputs
  • Always test the form after changing field configuration
  • Review submission records to confirm expected data is collected

What’s next

Once fields are configured, the next step is controlling how and where forms are displayed.

Continue with:

Simplify your WordPress workflow!

Build faster, cleaner, and more reliable WordPress websites using lightweight plugins designed for real-world workflows.

Get started now