Skip to content

Instance · Forms

Details

Last updated 1 November 2026

Use this tab to fill out basic form details. Input requirements and descriptions are displayed in the table below:

Input LabelTypeRequiredDescription
Form Name Input Field Yes The name of the form.
Form Path Display Field No The path used by Insites to store the form. The system automatically cleans and transforms your form name to one that follows internal rules and conventions.
Database Dropdown Field Yes The database used by the form to store submitted data.
Redirect To Input Field No The relative URL a user is directed to upon a successful form submission.
Spam Protection Radio Buttons No

The type of spam protection used by your form. Options include the following:

  • None
  • reCAPTCHA V2
  • reCAPTCHA V3

Note

You must choose a value from the Database field before you can open the following tabs:

  • Fields
  • Form Code
  • Email Notifications

The Settings tab is available straight away.

reCAPTCHA v3

Google reCAPTCHA version 3 is an invisible security measure designed to significantly enhance user experience by providing protection to forms without causing any disruption to users. Users do not need to interact with the form for the system to check whether they are humans or bots, so there is less friction. This section discusses the input requirements and descriptions if you choose reCAPTCHA v3 as your spam protection option.

Input LabelTypeRequiredDescription
Action Input Field Yes The name of the action you are applying reCAPTCHA to. Please refer to the reCAPTCHA v3 documentation for more details
Minimum Score Number Field No

A score between 0.0 and 1.0 assigned by reCAPTCHA to each user interaction, where '1.0' indicates a high likelihood that a human performed the interaction and '0.0' indicates a very high likelihood that a bot performed the interaction

You can set a threshold score based on your risk tolerance and the specific action being protected (e.g., login, registration, form submission). Any score at or above this threshold is deemed acceptable, while scores below it trigger your defined security measures, such as requiring two-factor authentication or blocking the action entirely.