> For the complete documentation index, see [llms.txt](https://docs.informationhub.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.informationhub.io/project/forms/form-settings.md).

# Form Settings

After creating a form, you can adjust its settings to control how it looks, who can access it, and how it behaves on submission. Open a form and click the **Settings** button in the toolbar to reach the settings page.

## General settings

### Form name

Change the display name of your form. This is the name that appears in the forms list and at the top of the form when someone opens it.

### Visibility

Set who can see the form within your project (Private, Public, or Protected).

### Email notifications

By default, the platform sends a submission notification email to the person who submitted the form after every successful submission. You have two controls to change this:

**Send Custom Email toggle** - when this toggle is **ON**, the default submission notification is suppressed entirely. No email will be sent to anyone, including the submitter. Turn this on if you want to silence all submission emails for this form (for example, during high-volume data collection sessions where email noise is unwanted).

**Email List** - enter a comma-separated list of email addresses. When the **Send Custom Email** toggle is **OFF** (the default), every address in this list will also receive the submission notification alongside the submitter. Leave this blank to send notifications only to the submitter.

The Email List field is visible regardless of the toggle state, but addresses in the list only receive emails when the toggle is \*\*OFF\*\*. If the toggle is ON, no emails are sent even if addresses are listed. {% endhint }

### Webhook

Enter a URL in the **Webhook** field to have Information Hub send an HTTP POST request to that address each time the form is submitted. Use this to connect your form to external systems or automation tools.

### Sharing

Toggle **Allow Sharing** to enable the public share link for this form. When sharing is on, a **Preview** button appears - click it to open the form as a respondent would see it.

To stop accepting new responses, turn **Allow Sharing** off. The link will stop working, but the form and all previously collected data are not affected.

Click **Save** to apply your general settings changes.

## Form configuration

### Layout type

Choose how the form is presented to users. Options include Default, Icons and Text, Icons, and Accordions. Different layouts change the visual arrangement of sections and questions.

### Show section header

Toggle this on or off to show or hide section headings when someone is filling in the form.

### Submit buttons

Choose how the submit area behaves:

* **Submit** - a single submit button. After submitting, the respondent sees a confirmation page.
* **Submit Many** - a "Submit and Reset" button appears alongside the standard Submit button. After submitting, the form clears immediately so the respondent can fill it in again straight away. Use this for high-volume data entry sessions.

### Submit button size

Set the size of the submit button to **Default** or **Large**. A larger button can be easier to tap on mobile devices.

### Logo

Enter a URL for a custom logo image to display at the top of the public form. Use the **Logo** field for a light-background logo and the **Dark mode Logo** field for a version that looks correct on dark backgrounds.

### Colours

Customise the appearance of your form:

* **Primary colour** - used for buttons, highlights, and active elements.
* **Secondary colour** - used for secondary UI elements.

These settings only affect the form when it is opened via its shareable link.

### Require logged in user

When this toggle is on, only registered Information Hub users who are logged in can access and submit the form. Their identity is recorded with each submission. When it is off, anyone with the link can submit without creating an account.

Click **Save** to apply your form configuration changes.

## Reordering sections and questions

The **Reordering** card lets you change the order of sections and questions without rebuilding the form:

* Drag the handle next to a **section** to move it to a new position. Click **Save** to apply the new section order.
* Drag the handle next to a **question** to reorder it within its section. Click **Save** to apply the new question order for that section.
* If your form has more than one section, a **Move to...** dropdown appears next to each question. Select a different section from the dropdown to move the question there.

## Delete form

The **Delete Form** card at the bottom of the settings page contains a **Delete** button. This permanently removes the form. See [Delete a Form](/project/forms/delete-form.md) for details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.informationhub.io/project/forms/form-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
