# Object Layout Customization

{% hint style="success" %}
**Audience**: Technical Admins, Developers, Solution Architects

**Purpose**: Explains how to customize <code class="expression">space.vars.entity</code> layouts, list views, and actions for an <code class="expression">space.vars.object</code>, and clarifies what layout configuration does and does not affect.
{% endhint %}

## Overview

Customize Layout focuses on the presentation and interactions you have with your <code class="expression">space.vars.object</code> rather than the data structure. It does not change fields, relationships, validation rules, or stored data.

During <code class="expression">space.vars.object</code> configuration, Customize Layout appears as Step 4. If Workflows are enabled, it becomes Step 5.

1. General Settings
2. Related <code class="expression">space.vars.object</code>s
3. Customize Fields
4. <mark style="color:$success;">**Customize Layout**</mark>
5. Permissions

The Customize Layout step lets you control how <code class="expression">space.vars.entities</code> for an <code class="expression">space.vars.object</code> are displayed and interacted with in <code class="expression">space.vars.Kizen\_company\_name</code>. This includes how individual <code class="expression">space.vars.entities</code> are laid out, which fields appear in <code class="expression">space.vars.entity</code> lists by default, and which actions users can take on a <code class="expression">space.vars.entity</code>.&#x20;

Use Customize Layout after fields and relationships are defined, but before setting permissions.

***

## What You Can Customize

Within **Customize Layout**, you can configure three areas:

* **Record Layout:** How individual <code class="expression">space.vars.entities</code> are displayed in <code class="expression">space.vars.Kizen\_company\_name</code>
* **Default Columns:** Which fields appear in <code class="expression">space.vars.entity</code> list views by default
* **Custom Actions:** Actions users can take directly from a <code class="expression">space.vars.entity</code>

Each area controls a different part of the <code class="expression">space.vars.entity</code> experience.

<div data-with-frame="true"><figure><img src="/files/gx6jQbtwO0kYadD8qwmp" alt="" width="563"><figcaption></figcaption></figure></div>

### Record Layout Tab

<code class="expression">space.vars.entity</code> layouts control how a single <code class="expression">space.vars.entity</code> appears when a user opens it. Layouts determine which components appear on the <code class="expression">space.vars.entity</code> page, how they are arranged, and who can see a given layout.

A <code class="expression">space.vars.entity</code> layout includes:

* A layout name
* An active or inactive state&#x20;
* Optional display settings (such as whether to show the <code class="expression">space.vars.automations</code> tab)
* A configurable layout canvas made up of rows, columns, and components
* Layout-specific sharing settings

Changes to a <code class="expression">space.vars.entity</code> layout affect how <code class="expression">space.vars.entity</code>s are displayed, not what data is stored.

<div data-with-frame="true"><figure><img src="/files/214UZ8KEuJc9DK1zthde" alt="" width="563"><figcaption></figcaption></figure></div>

#### When to Use Record Layouts

Use <code class="expression">space.vars.entity</code> layouts when:

* <code class="expression">space.vars.entities</code> require a clear visual hierarchy
* Different users need different <code class="expression">space.vars.entity</code> experiences
* Actions and timelines should be emphasized or hidden
* <code class="expression">space.vars.objects</code> contain many fields and components

#### How Record Layouts Work

Each <code class="expression">space.vars.object</code> can have one or more <code class="expression">space.vars.entity</code> layouts. From the <code class="expression">space.vars.entity</code> Layout tab, select an existing layout (such as *Standard View*) to modify or create a new one.

Each <code class="expression">space.vars.entity</code> layout defines the visual structure of a <code class="expression">space.vars.entity</code> page, including which components appear, how they’re arranged, and who can see the layout. Layouts can be active or inactive and may include optional display settings, such as whether to show the <code class="expression">space.vars.automation</code>s tab.

<div data-with-frame="true"><figure><img src="/files/GFckDE91jCzVdiJdPNKN" alt="" width="563"><figcaption></figcaption></figure></div>

#### Record Layout Structure and Components

Layouts are built using a row-and-column grid.

* Rows define horizontal sections of the page
* Each row can contain one or more columns
* Columns hold one or more layout components

You can add new rows and add components within each column to control the structure of the <code class="expression">space.vars.entity</code> page.

Layout components define what information and functionality appears on a <code class="expression">space.vars.entity</code> page. Components are added to a layout within rows and columns. When adding a component, you choose a component type and assign an internal block name for reference.

Components can be reordered within a column to control vertical placement on the <code class="expression">space.vars.entity</code> page.

Available layout components include:

* **Field categories:** Displays selected fields from the <code class="expression">space.vars.object</code>
* **Team and Activities:** Displays assigned team members and activity-related information
* **Action Block:** Displays available actions for the <code class="expression">space.vars.entity</code> (email, notes, <code class="expression">space.vars.automations</code>, and activities)
* **Lead Sources:** Displays lead source information (when applicable)
* **Timeline:** Displays activity and timeline history for the <code class="expression">space.vars.entity</code>
* **Related Object Fields:** Displays selected fields from a related <code class="expression">space.vars.entity</code> on the current record to provide additional context.
* **Custom Content (Builder):** Lets users create and embed flexible, custom UI elements—such as rich text, images, buttons, and layout sections—directly within a <code class="expression">space.vars.entity</code> layout to support guidance, workflows, or contextual information.

<div data-with-frame="true"><figure><img src="/files/iDaBDspFXvCPs4T8zHBp" alt="" width="563"><figcaption></figcaption></figure></div>

#### Record Preview

The <code class="expression">space.vars.entity</code> Preview panel shows a live preview of the selected layout.

* Previews update as you modify the layout
* The preview helps validate structure and component placement before saving

<div data-with-frame="true"><figure><img src="/files/5KbvIrHU5c2hK9Vwofcw" alt="" width="563"><figcaption></figcaption></figure></div>

#### Visibility and Sharing

<code class="expression">space.vars.entity</code> layouts have their own sharing settings that control who can view <code class="expression">space.vars.entity</code>s using a given layout.

<div data-with-frame="true"><figure><img src="/files/cCZYazMfWcVi6aeWxtgg" alt="" width="563"><figcaption></figcaption></figure></div>

You can configure layout visibility for:

* **All Team Members**
  * None
  * View
* **Specific Roles (View)**
* **Specific Team Members (View)**

Layout sharing settings affect which users can see <code class="expression">space.vars.entities</code> using that layout. They do not grant edit or admin permissions.

#### When to Use Record Layouts

Use <code class="expression">space.vars.entity</code> layouts when:

* <code class="expression">space.vars.entities</code> require a clear visual hierarchy
* Different users need different <code class="expression">space.vars.entity</code> experiences
* Actions and timelines should be emphasized or hidden
* <code class="expression">space.vars.objects</code> contain many fields and components

### Default Columns Tab

Default columns control which fields appear in the <code class="expression">space.vars.object</code>’s <code class="expression">space.vars.entity</code> list view. These columns define what users see when browsing <code class="expression">space.vars.entities</code> without opening them.&#x20;

{% hint style="info" %}
**Note**: Default columns apply to all users unless it's customized by the user.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/6N3YhbFqutKuPAasCBdD" alt="" width="563"><figcaption></figcaption></figure></div>

#### How Default Columns Work

From the **Default Columns** tab, you configure the table columns shown for the <code class="expression">space.vars.object</code> by default.

The page is divided into three main areas:

* **Column Preview:** shows a live preview of the <code class="expression">space.vars.entity</code> list table

<div data-with-frame="true"><figure><img src="/files/0YqMFlmriFEHKOjvMDkN" alt="" width="563"><figcaption></figcaption></figure></div>

* **Available Columns (Drag to Add):** fields that can be added as columns to the <code class="expression">space.vars.entity</code> list table. Fields in **Available Columns** are grouped by category (for example, *Ingredient Info* or *Stock & Cost*) and can be searched using the Find Options field.

<div data-with-frame="true"><figure><img src="/files/FMyxU4svIB29I85rILgT" alt="" width="563"><figcaption></figcaption></figure></div>

* **Active Table Columns:** fields currently shown in the table (this will match the preview)

<div data-with-frame="true"><figure><img src="/files/wGH6b0tQu6QYYwti56Y5" alt="" width="563"><figcaption></figcaption></figure></div>

To configure default columns:

* Drag a field from **Available Columns** into **Active Table Columns** to add it
* Drag fields within **Active Table Columns** to reorder them
* Remove a column using the delete icon

Changes are reflected immediately in the **Column Preview**.

#### What Default Columns Affect

Default columns determine:

* Which fields are visible in <code class="expression">space.vars.entity</code> lists
* The order of columns in the table
* Which columns can be sorted by users

These settings define the default list view experience for all users. If a user customizes their list view, their personal settings take precedence.

<details>

<summary>Example</summary>

### Bakery example

In an Ingredients <code class="expression">space.vars.object</code>, default columns might include:

* Ingredient Name
* Owner
* Date Bought
* Last Modified
* Amount (lbs.)

Additional fields, such as *On-Hand Quantity* or *Unit Cost*, can be added depending on what users need to see at a glance.

</details>

### Custom Actions Tab

Custom actions define <code class="expression">space.vars.object</code>-specific actions that users can take directly from a <code class="expression">space.vars.entity</code>. Actions typically trigger <code class="expression">space.vars.automations</code> and support <code class="expression">space.vars.entity</code>-based workflows.

<div data-with-frame="true"><figure><img src="/files/wqBPPu4e7mouWTQ2In4F" alt="" width="563"><figcaption></figcaption></figure></div>

#### How Custom Actions Work

Custom actions control the execution state of an <code class="expression">space.vars.automation</code> for a specific <code class="expression">space.vars.entity</code>, allowing users to trigger <code class="expression">space.vars.automations</code> without needing general Start <code class="expression">space.vars.automation</code> permissions.

Each custom action includes:

* **Action Name:** the label shown to users
* **Action type:** defines how the associated <code class="expression">space.vars.automation</code> is controlled when the action is used (for example, start, pause, or cancel).

<div data-with-frame="true"><figure><img src="/files/mcRkmwuXeVEpXXQGB62K" alt="" width="375"><figcaption></figcaption></figure></div>

* **Agentic Workflow:** the <code class="expression">space.vars.automation</code> that runs when the action is used
* **Action Description:** a short explanation of what the action does

Custom actions operate in the context of the selected <code class="expression">space.vars.entity</code> and can also be run in bulk from list views.

<div data-with-frame="true"><figure><img src="/files/4F8ay9CHqo0jZNKobS9P" alt="" width="563"><figcaption></figcaption></figure></div>

#### Visibility and Sharing

Custom actions have their own sharing and permission settings, separate from <code class="expression">space.vars.object</code>-level permissions.

You can control access by:

* **All Team Members**
  * None
  * View/Use
  * Edit
  * Admin
* **Specific Roles**
  * View/Use
  * Edit
  * Admin
* **Specific Team Members**
  * View/Use
  * Edit
  * Admin

This allows actions to be broadly available, role-based, or restricted to individual users.

<div data-with-frame="true"><figure><img src="/files/5LhIN2d4N66L8WDvd6dh" alt="" width="563"><figcaption></figcaption></figure></div>

#### When to use custom actions

Use custom actions to:

* Trigger <code class="expression">space.vars.automations</code> from a <code class="expression">space.vars.entity</code>
* Support approval or review workflows
* Enable <code class="expression">space.vars.entity</code>-based operational tasks

***

## What's Next

After customizing layouts, continue to [Object Permissions](/docs/concepts/objects/object-configuration/object-permissions.md) to control who can view, create, edit, and delete <code class="expression">space.vars.entities</code> for this <code class="expression">space.vars.object</code>. If you need to add or update fields, see [Custom Fields](broken://pages/6rrJeEIzfjMAZY62pfmc) or review [Records](/docs/concepts/objects/records.md) to see how data appears to users.

<details>

<summary>Related Topics</summary>

* [Objects Core Concepts](/docs/concepts/objects/object-core-concepts.md)
* [Object Data Model](/docs/concepts/objects/object-data-model.md)
* [Object Relationships](/docs/concepts/objects/object-configuration/object-relationships.md)
* [Object Layout Customization](/docs/concepts/objects/object-configuration/object-layout-customization.md)
* [Object Permissions](/docs/concepts/objects/object-configuration/object-permissions.md)

</details>


---

# Agent Instructions: 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:

```
GET https://developer.kizen.com/docs/concepts/objects/object-configuration/object-layout-customization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.