> 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/customize-your-portal.md).

# Customize your Portal

In this section you will learn how to customize your customer portal

In Jet Admin, you can **customize the appearance** of your Portal for better usability. Let's start with the `Units` table.

**Let's disable** unnecessary columns and **rearrange** the order.

1. Click on the **Units Table**
2. Disable the unnecessary columns

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

{% hint style="info" %}
In Airtable, field types are detected automatically, but for other data sources you might need to configure them by clicking on the **column icon**
{% endhint %}

Let's now set the number of **displayed rows** to **5**, and make the first row selected by default. To do that, follow the steps:

1. Go to the **Display Tab**
2. Set 5 in the **Rows Per Table** section
3. Enable the **Select First Row By Default** option

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

You can change the **field types** to render different fields differently and customize their appearance. To do so,

1. Click on the **Priority** field
2. Choose **Low Option**
3. Click on the **Color** field
4. Choose the Color

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

In Jet Admin, you can configure and customize **any component individually on any page**. Let's make our record fields non-editable so that the users will be able to change them.

1. Click on the **Unit ID** field
2. From the menu on the right, change it to **Editable**
3. Click on the Assign To ID field
4. From the menu on the right, change it to **View-Only**

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

Applying similar edits to the `Tasks` table and we're done with the UI customization.

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2Fb1fuKNCFWLUgTV4wJuVO%2Fimage.png?alt=media&amp;token=f6d47c5d-764d-4d22-8a97-940f2fe91b3a" alt=""><figcaption></figcaption></figure>

Now, let's invite external users and make them interact **only with their data:**

{% content-ref url="/pages/-MizsTUT7xryLnA\_fV2W" %}
[Users & Permissions](/classic-app-builder/classic-tutorials/creating-a-customer-portal/invite-users.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/customize-your-portal.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.