Form Settings
Configure the public text and internal name for a form.
Form settings control the basic text shown to respondents and the internal name admins use to recognise the form.
Open a form in the builder and go to Settings.
Admin Settings
Internal Title
The internal title is the name shown to admins in the FormWork interface.
Use it for:
- Separating similar forms
- Naming test or draft forms
- Including campaign, region, or team details
Examples:
- Customer Quote Request - UK
- Supplier Onboarding - 2026
- Support Escalation Form - Internal
The internal title is not shown to respondents.
Public Form Settings
Form Title
The form title is shown to respondents at the top of the form unless the embed hides it.
Good titles are short and specific:
- Request a Quote
- Supplier Onboarding
- Submit a Support Request
Form Description
The description gives respondents context before they start.
Use it for:
- Explaining what the form is for
- Listing information they should have ready
- Setting expectations about what happens next
Keep the description concise. Long instructions are usually better placed near the relevant fields.
Submit Button Text
Submit button text controls the label on the final submit button.
Examples:
- Submit
- Send Request
- Complete Application
- Place Order
- Request Approval
Choose text that matches the action the respondent is taking.
Success Message
The success message is shown after the form is submitted.
Use it to confirm:
- The submission was received
- What will happen next
- Whether the respondent should expect an email
- Typical response times
Example:
Thank you. Your request has been submitted and our team will review it within two business days.
Related Settings
Some form behaviour is managed outside the Settings page:
- Use Appearance for colours, fonts, spacing, and theme mode.
- Use Share for direct links and embed code.
- Use Fields for default values, validation, and conditional visibility.
- Use Workflows for notifications, generated files, integrations, and internal automation.
- Use Metafields for admin-only fields and review processes.
Best Practices
- Use the internal title for admin clarity and the public title for respondent clarity.
- Avoid vague submit labels like Go or Next on the final submission.
- Keep success messages specific enough that respondents know the form worked.
- Review settings before publishing a new form version.