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

# Enterprise Form Builder

The Enterprise Form Builder is a dedicated form-building and data management interface built specifically for non-developers. This application offers a team of non-developers the capability to easily manage forms and data without needing access to the Form.io project. This relieves the risk of unintentional modifications or changes to project settings that could potentially affect the stability of the application running on Form.io. Only forms designated by Project users are available within the interface. Take advantage of the white-labeling feature for the Form Manager application by adding custom logos, CSS, and branding within the project settings.

[**Learn more about the Enterprise Form Builder**](/dev/enterprise-form-builder-module.md)

<figure><img src="https://501951130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6LdEf8SjBIeQDsRL3BdV%2Fuploads%2Fgit-blob-af0c2b5332ed22d93692ba51d04fde402a27b8fb%2Ffmg1.jpg?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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://help.form.io/form-building/enterprise-form-builder.md?ask=<question>&goal=<user_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.
