> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/data-capture/forms/settings.md).
# Settings
From the Form Settings screen you can configure:
**Form type** which can be changed at any time.
**Auto-submit** causes the form to submit immediately when the page loads, skipping the form view and going straight to the confirmation page. This is useful for single-click competition entries or opt-outs, where a hidden field sets a value in the database without the contact needing to do anything.
**Status** controls whether the form is active. Inactive forms will not accept submissions.
**Close date** automatically deactivates the form after a specified date.
**Source** sets the value recorded in the Source field for any new contacts added via this form.
**Form Access** controls who can access the form. Options include open access for anyone with the link, restriction to API use only, restriction to allowed IP addresses for the account, or a custom IP address whitelist.
**Layout** sets the visual layout applied to the form. See Layouts for more detail.
The Edit Form Settings screen, showing form details, settings, and access options.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ubiquity.co.nz/documentation/data-capture/forms/settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
