> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/classic-tutorials/creating-a-customer-portal/set-the-layout.md).

# Set the Layout

In this section you will learn how to set the layout for creating a customer portal

Jet Admin provides a library of pre-built **UI components**, such as `Table`, `Map`, `Gallery`, or `Charts` that you can **drag and drop** to display your data. As well as the `Layout` components that are used to assemble other components on the page.

### Set the Layout

`Columns` are used to set the horizontal component of the layout. You can add multiple columns and resize them.&#x20;

To add columns, follow the steps:

1. From the Layout menu, drag and drop **Columns**
2. **Drag and Drop** the Tasks Table in the **Right Column**
3. **Drag and Drop** a Form in the **Left Column**

{% @arcade/embed flowId="6Nwgc22eZgdQzUN8KFfA" url="<https://app.arcade.software/share/6Nwgc22eZgdQzUN8KFfA>" %}

We also can change the position of the individual fields in the record view. For that, drill down into the record and drag and drop the fields you want to reassemble:

{% @arcade/embed flowId="I3gyu8LesPigQCpUxvxk" url="<https://app.arcade.software/share/I3gyu8LesPigQCpUxvxk>" %}

Now, let's add our `Project` table and link it to the `Tasks` table:

{% content-ref url="/pages/-Mizrl8MaWUqHSs9-LOJ" %}
[Link Related Tables](/classic-app-builder/classic-tutorials/creating-a-customer-portal/link-related-table.md)
{% endcontent-ref %}


---

# 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://docs.jetadmin.io/classic-app-builder/classic-tutorials/creating-a-customer-portal/set-the-layout.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.
