Object Layout Customization
Audience: Technical Admins, Developers, Solution Architects
Purpose: Explains how to customize Record layouts, list views, and actions for an Object, and clarifies what layout configuration does and does not affect.
Overview
Customize Layout focuses on the presentation and interactions you have with your Object rather than the data structure. It does not change fields, relationships, validation rules, or stored data.
During Object configuration, Customize Layout appears as Step 4. If Workflows are enabled, it becomes Step 5.
General Settings
Related Objects
Customize Fields
Customize Layout
Permissions
The Customize Layout step lets you control how Records for an Object are displayed and interacted with in Kizen. This includes how individual Records are laid out, which fields appear in Record lists by default, and which actions users can take on a Record.
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 Records are displayed in Kizen
Default Columns: Which fields appear in Record list views by default
Custom Actions: Actions users can take directly from a Record
Each area controls a different part of the Record experience.
Record Layout Tab
Record layouts control how a single Record appears when a user opens it. Layouts determine which components appear on the Record page, how they are arranged, and who can see a given layout.
A Record layout includes:
A layout name
An active or inactive state
Optional display settings (such as whether to show the Automations tab)
A configurable layout canvas made up of rows, columns, and components
Layout-specific sharing settings
Changes to a Record layout affect how Records are displayed, not what data is stored.
When to Use Record Layouts
Use Record layouts when:
Records require a clear visual hierarchy
Different users need different Record experiences
Actions and timelines should be emphasized or hidden
Objects contain many fields and components
How Record Layouts Work
Each Object can have one or more Record layouts. From the Record Layout tab, select an existing layout (such as Standard View) to modify or create a new one.
Each Record layout defines the visual structure of a Record 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 Automations tab.
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 Record page.
Layout components define what information and functionality appears on a Record 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 Record page.
Available layout components include:
Field categories: Displays selected fields from the Object
Team and Activities: Displays assigned team members and activity-related information
Action Block: Displays available actions for the Record (email, notes, automations, and activities)
Lead Sources: Displays lead source information (when applicable)
Timeline: Displays activity and timeline history for the Record
Related Object Fields: Displays selected fields from a related Record 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 Record layout to support guidance, workflows, or contextual information.
Record Preview
The Record 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
Visibility and Sharing
Record layouts have their own sharing settings that control who can view Records using a given layout.
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 Records using that layout. They do not grant edit or admin permissions.
When to Use Record Layouts
Use Record layouts when:
Records require a clear visual hierarchy
Different users need different Record experiences
Actions and timelines should be emphasized or hidden
Objects contain many fields and components
Default Columns Tab
Default columns control which fields appear in the Object’s Record list view. These columns define what users see when browsing Records without opening them.
Note: Default columns apply to all users unless it's customized by the user.
How Default Columns Work
From the Default Columns tab, you configure the table columns shown for the Object by default.
The page is divided into three main areas:
Column Preview: shows a live preview of the Record list table
Available Columns (Drag to Add): fields that can be added as columns to the Record 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.
Active Table Columns: fields currently shown in the table (this will match the preview)
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 Record 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.
Custom Actions Tab
Custom actions define Object-specific actions that users can take directly from a Record. Actions typically trigger automations and support Record-based workflows.
How Custom Actions Work
Custom actions control the execution state of an automation for a specific Record, allowing users to trigger automations without needing general Start Automation permissions.
Each custom action includes:
Action Name: the label shown to users
Action type: defines how the associated automation is controlled when the action is used (for example, start, pause, or cancel).
Automation: the automation 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 Record and can also be run in bulk from list views.
Visibility and Sharing
Custom actions have their own sharing and permission settings, separate from Object-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.
When to use custom actions
Use custom actions to:
Trigger automations from a Record
Support approval or review workflows
Enable Record-based operational tasks
What's Next
After customizing layouts, continue to Object Permissions to control who can view, create, edit, and delete Records for this Object. If you need to add or update fields, see Custom Fields or review Records to see how data appears to users.
Last updated
Was this helpful?