> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/forms/form-canvas.md).
# Form canvas
A form in the Workflow Designer is a graphical layout of fields that are bound to the data model. From here, you can control how the fields of the data model appear in Collibra. The fields are arranged in rows on the canvas, as shown below:
Each row of the graphical layout is made up of exactly twelve columns. All columns are equal in size, so the width of a column is one-twelfth the width of the whole form. You can lengthen or shorten a field to fit into any number of columns and place more than one field on a row.
{% hint style="warning" %}
When Collibra displays a task in the sidebar, all the fields are shown in one column to adapt to the limited available width. Only tasks in full screen mode take advantage of the multi-column layout.
{% endhint %}
---
# 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://developer.collibra.com/workflows/designing-workflows/forms/form-canvas.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.