--- title: "Form Settings" slug: "form-settings" updated: 2026-09-14T03:09:01Z published: 2026-09-14T03:09:01Z canonical: "help.infoodle.com/form-settings" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.infoodle.com/llms.txt > Use this file to discover all available pages before exploring further. # Form Settings The Settings tab controls how your form behaves — when it's available, who can access it, what happens after someone submits it, and who gets notified. Work through each section below. ## Description | Field | What it does | | --- | --- | | **Form description** | An internal note about the form. Only admins can see this — it does not appear on the public form. | | **Submit button text** | Customise the label on the submit button. Defaults to Submit. | | **Include reCAPTCHA** | Adds a reCAPTCHA checkbox to the form to deter spam submissions. | | **Visible to Search Engines?** | Untick to tell search engines not to index this form's public URL. | | **Show on Dashboard?** | Makes the form appear in the Forms widget on users' dashboards. To automatically link each submission to the logged-in user, you must also add a Person Safe ID field to the form in the Build tab — the dashboard setting alone is not enough. | | **Login required?** | Restricts access so only users already logged into infoodle can view and submit the form. | --- ## Appearance Paste any custom CSS here to further style the public-facing form. This CSS applies only to what visitors see — it does not affect the form designer or entries screens. See [CSS Code Advanced](/v1/docs/css-code-advanced) for guidance. --- ## When is this form available? |Field| What it does| |**Start date**| The first date the form accepts submissions. Leave blank to open immediately when published.| |**End date**| The last date the form accepts submissions. Submissions on or after this date are rejected. Leave blank for no end date. |**Status**| **Active** — the form accepts submissions. **Not Active** — the form is hidden when embedded; visitors who reach the direct URL will see that the form is unavailable. **Deleted** — the form is hidden from your form list unless you filter by **All** or **Deleted**.| **Important:** The form must be set to Active and published before it will accept public submissions. --- ## Notify internal users or groups after an entry is completed Use this section to alert staff when someone submits the form. - **Person** — search for a specific person to notify. - **Group** — select a group whose members will all be notified. Only select internal staff groups here — do not select a community or public group. When a group is selected, you can choose to send a **brief notification** (summary only) rather than the full form details. The notification email includes the Entry ID in the subject line so staff can locate the entry quickly. If neither a person nor a group is selected, no notification email is sent. --- ## After the form is completed Choose what happens when a user clicks **Submit**. - **Show a message to the user** — displays a thank-you message on screen. The message can contain HTML. Tick Stay on form after message? to keep the form visible after submission. If you leave this unticked, the form automatically resets after 5 seconds — useful for shared kiosk devices. - **Take the user to a web page** — redirects the visitor to a URL of your choice (for example, your main website or a second infoodle form). You can also choose whether the destination page replaces only the embedded form area or takes over the entire browser page. --- ## Form access restrictions These two settings control which infoodle users can manage this form and its entries. They work independently of role-level permissions and apply per form. - **Form Edit Restriction** — limits which group's members can open this form in the designer and make changes to it. If set, users outside that group cannot edit the form even if their role otherwise allows form editing. Remove the group (click the ×) to open editing to all users with the relevant role permission. - **Form Entry Restriction** — limits which user or group can view and process this form's entries. If set, only the nominated user or group members can see entries in the approval screen. Leave this blank to allow all users with form processing permissions to access entries. > **Tip:** If a staff member loses access to a form after someone leaves your organisation, check these two settings first. You may need to remove a departing user from the Entry Restriction field or update the Edit Restriction group. See [What are Roles](/v1/docs/what-are-roles) for the role-level permissions that interact with these settings. --- ## Next steps - [Form Email Response](/v1/docs/form-email-response) — set up the automated email sent to the person who submitted - [Form Approval Settings](/v1/docs/form-approval-settings) — configure who reviews and approves entries - [Form Auto-Approval](/v1/docs/form-auto-approval) — set rules so entries are approved without manual review - [Publishing a Form](/v1/docs/publishing-a-form) — make your form live and get the sharing link ## Related - [Forms](/forms.md) - [Adding a Form](/adding-a-form.md) - [CSS Code (Advanced)](/css-code-advanced.md) - [Processing Form Entries](/processing-form-entries.md) - [Form Email Response](/form-email-response.md) - [Publishing a Form](/publishing-a-form.md) - [Form Auto-Approval](/form-auto-approval.md)