Appearance
Form editor
The Form Editor is where you build the form that people will complete. It is designed around a simple cycle: add a field, select it, adjust its details, then preview the experience before publishing.
Open a form in the editor
Open My Forms, then select the form you want to work on. For testing, use a non-production form and non-sensitive sample values.
Shared with me is where forms shared with you inside the company are visible. Open a shared form only with the owner’s authorization.
The editor at a glance
| Area | What it is for |
|---|---|
| Form name and save status | Identify the form and confirm that changes have been saved. |
| Undo and Redo | Step backward or forward through recent edits. |
| Fields | Add questions, content, and form controls. |
| Edit | Change the selected field’s name, appearance, validation, and field-specific settings. |
| Design | Change the form’s visual appearance, including theme, page, and field styling. |
| Conditions | Add conditional logic and calculations. |
| Payments | Configure payment behavior when the form collects payments. |
| Integrations | Connect the form to external services and supported actions. |
| Responses | Review form submissions. |
| Files | Work with files associated with the form, when available to your permission level. |
| Translations | Manage translated versions of the form, when enabled. |
| Settings | Configure form-level details, notifications, submission behavior, and security. |
| Workflow | Open the workflow connected to the form. |
| Publish | Choose how to share or embed the finished form. |
| Preview | See the form from a respondent’s point of view. |
Some tabs depend on your permissions, plan, enabled integrations, or product configuration. If an expected option is not visible, check access and plan limits before changing the form design.
A reliable way to build a form
- Write down the outcome you need: registration, request, feedback, payment, or another task.
- Add only the essential questions first.
- Give each question a clear label and a useful internal field name.
- Mark genuinely essential answers as required; do not make every field required by default.
- Add rules only after the basic question flow is clear.
- Preview and complete the form yourself using ordinary, non-sensitive test data.
- Configure settings and publishing only when the form content is ready.
This order keeps the form understandable and makes it much easier to troubleshoot a problem later.
Core editor task guides
- Add and configure a field
- Configure common field settings
- Style the form
- Field settings reference
- reCAPTCHA security control
Saving and recovery
AbcSubmit displays a save-status indicator beside the form name. Wait until it shows that the form is saved before closing the tab or moving to another area.
Use Undo immediately when an edit was accidental. Redo restores an edit that you just undid. These controls are most useful for recent changes in the current editing session; they are not a substitute for a carefully reviewed production form.
Before you make a major change
Changing a live form can affect people who are completing it, the data stored in responses, rules, notifications, reports, workflows, and integrations. Before changing a live form:
- Preview the impact in a non-production form or approved draft whenever possible.
- Avoid changing an existing field’s internal name unless you understand every rule, notification, export, or workflow that refers to it.
- Test conditional logic and required-field behavior from the respondent’s point of view.
- Review the published form after saving if it is already shared or embedded.