> 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.md).

# Building Forms

Design forms quickly, easily, and intelligently

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.

***

## Creating Forms

You can create forms in <mark style="color:red;">four</mark> 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 the Form

Edit the form name inline at the top of the page.
{% endstep %}

{% step %}

#### Add a Field

* Click on the blue "+" button to insert a field anywhere, even between existing fields.&#x20;
* Choose the desired field type from the choices.
  {% endstep %}

{% step %}

#### Move a Field

* Hover over the field you want to move.&#x20;
* Use the \[name of icon] button to drag and drop the field to move them between sections and columns.
  {% endstep %}

{% step %}

#### Set Field Conditions

Use the dropdown next to the ellipsis (**⋮**) menu:

* **Editable -** Users can enter or change data.
* **Mandatory -** Users must fill in this field before submitting.
* **Read-Only -** Users can view but not edit (useful to create introductions, descriptions, or reference information).
* **Invisible -** The field is hidden to users.
  {% endstep %}

{% step %}

#### Customize & Delete Fields

From the ellipsis (**⋮**) menu:

* Rename and format the field (bold, italic, font size, color).
* Add a tooltip for guidance.
* Delete the field.

> Additional customization options are available depending on the field type.\
> → See [Controls per Field Types](/interfacing-help-files/interfacing-help-files-fr/developpeurs-de-solutions/designer/building-forms/controls-per-field-types.md) for details.
> {% endstep %}

{% step %}

#### Finalize Your Form

When your form is ready, you can:

* **Save** — Store your progress to return later.
* **Preview** — Check how the form looks before publishing.
* **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><strong>Creating Task-Specific Fields</strong><br><br>Tailor your forms for each step in your workflow.</td><td><a href="https://content.gitbook.com/content/AgpNu7XmgN3Z9B8kIShD/blobs/l5cODyCYvCO9Nw1FXQ14/IMS%20Icons%20(1).png">IMS Icons (1).png</a></td><td><a href="/interfacing-help-files/interfacing-help-files-fr/developpeurs-de-solutions/designer/building-forms/creating-task-specific-fields.md">Creating Task-Specific Fields</a></td></tr><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>

notes:

* click on the 3 dots to edit: name of field + its formatting (bold, italic, font size, color), placeholder (when nothing is entered, this will be a light grey placeholder like: type here... or insert number, enter your value, etc), initial value (default), tooltip (small pop up to hint users), delete field, more options (depends on the field, but example maximum characters (that users can input), position of the choices (left, right))

* multi select drag and drop

* have to select child, not inherit

* components of the forms can select to appear for different tasks or parts of a process


---

# 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.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.