> 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="/files/tzs6kgoHbnuy97NSHpUX" 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 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://help.form.io/form-building/enterprise-form-builder.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.