> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/developpeurs-de-solutions/designer/building-forms/building-forms-option-2.md).

# Building Forms (option 2)

Design forms quickly, easily, and intelligently with Designer.

### Overview

Designer lets you create flexible, no-code forms to collect information, automate workflows, and connect tasks to the right users. You can generate forms automatically with AI, start from scratch, reuse existing forms, or adapt ready-made templates.

### Take a Tour

Begin with an interactive walkthrough to learn how to build forms.

## Creating Forms

You can create forms in four ways, depending on your needs:

{% stepper %}
{% step %}

### Generate with AI

* Click **AI & Upload**
* Enter a form name and provide text instructions describing the form’s purpose and any requirements
* (Optional) Upload a file to support or replace text instructions
* Click **Generate**
  {% endstep %}

{% step %}

### Build from Scratch

* Click **New**
* A blank form opens where you can begin adding fields
  {% endstep %}

{% step %}

### Reuse an Existing Form

* <mark style="color:red;">Steps</mark>
  {% endstep %}

{% step %}

### Use a Template

* Click **Template**
* Browse available templates by category or use case. Select the desired template to start editing
  {% endstep %}
  {% endstepper %}

***

## How to Build Forms

No matter how your form was created you can easily build, customize, and manage it:

{% stepper %}
{% step %}

### Name Your Form & Arrange Fields

* **Name the Form**
  * Edit the name inline at the top of the page.
* **Add Fields**
  * <mark style="color:red;">Click the blue "+" button</mark> <mark style="color:red;">to insert a field anywhere, even between existing fields.</mark>
  * <mark style="color:red;">Select the desired field type.</mark>&#x20;

> <mark style="color:red;">More on field types here.</mark>

* **Move Fields**
  * Hover over the field you want to move.
  * Use the drag-and-drop icon (☰) to reposition the field within sections or columns.
    {% endstep %}

{% step %}

### Set Field State

Use the dropdown next to the ellipsis (**⋮**) menu to control how users interact with each field:

* **Editable** — Users can enter or change data.
* **Mandatory** — Users must complete this field before submitting.
* **Read-Only** — Users can view but not edit (useful for instructions or references).
* **Invisible** — The field is hidden from users.
  {% endstep %}

{% step %}

### Customize & Delete Fields

From the field’s ellipsis (**⋮**) menu:

* Rename or format the field (bold, italics, size, color).
* Add a tooltip to guide users.
* Delete the field.
* Access additional options depending on the field type.&#x20;

> <mark style="color:red;">More on controls per field types here.</mark>
> {% endstep %}

{% step %}

### Creating Task-Specific Fields

* Click **Select Task(s)** at the top of the form.
* Choose one or more tasks from the dropdown list.

{% hint style="info" %}
For complex processes, type the task name in the **search box** to find tasks quickly.
{% endhint %}

* Add, edit, or adjust fields specifically for the selected tasks.

{% hint style="warning" %}

#### Adjusting field states

Using the dropdown, you can specify one state for the selected tasks and a separate state for the rest of the process.&#x20;

* For example, a field could be hidden for certain tasks but editable for all other steps.
  {% endhint %}

* To remove a selected task, click the "×" next to its name at the top of the form. To clear all tasks, click **Remove All.**
  {% endstep %}

{% step %}

### Finalize & Deploy

* **Save** — Store your progress to return later.
* **Preview** — See how the form will look for users.
* **Delete** — Remove the form if no longer needed.
* **Deploy** — Publish the form and make it available to users.
  {% endstep %}
  {% endstepper %}

***

## See Also

Want to take your forms further?

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><p><strong>Controls per Field Types</strong><br></p><p>Customize fields to make forms clear, efficient, and user-friendly.</p></td><td><a href="https://content.gitbook.com/content/AgpNu7XmgN3Z9B8kIShD/blobs/G6zPS1BQMzi4Ngu69mQ5/IMS%20Icons%20(2).png">IMS Icons (2).png</a></td><td><a href="/interfacing-help-files/interfacing-help-files-fr/developpeurs-de-solutions/designer/building-forms/controls-per-field-types.md">Controls per Field Types</a></td></tr></tbody></table>


---

# 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://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/developpeurs-de-solutions/designer/building-forms/building-forms-option-2.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.