Module Builder

Key Concepts

The Module Builder is where you design how your data is structured and how forms look when creating or editing records.

Layout Tab

The Layout tab is a three-panel workspace where you build your record form by dragging field types into sections.

Panel Layout

Header Controls

Adding Fields

To add a field to your form, drag a field type from the left panel and drop it into a section in the center panel.

Available Field Types

Unused Fields

Drag a field from the layout into the "Unused Fields" bin (bottom of the left panel) to remove it from the form without deleting its data. Fields here can be dragged back into the layout at any time.

Configuring Field Properties

Click any field in the Form Layout to open its configuration in the right panel. The panel has two tabs: Properties and Permissions.

Properties Tab

Permissions Tab

Controls which roles can see or edit this specific field. This is the same as Field-Level Security configured from the Roles page, but accessed per-field instead of per-role.

Sections

Sections are named containers that group related fields together on the form. Every field must belong to a section.

Section Controls

The first section (typically "Basic Details") is marked as a system section and cannot be deleted, but you can rename it and reorder fields within it.

Card View Tab

The Card View tab controls which fields appear in the compact record representation — shown in list views, related lists, and when hovering over lookup fields.

Three Panels

Controls

Form Rules Tab

The Form Rules tab lists all form rules configured for this module. From here you can create new rules, edit existing ones, or toggle them on/off.

Table Columns

Creating a Form Rule

Click "Create Form Rule" to open a dialog where you name the rule and choose when it should trigger.

Dialog Fields

Trigger Options

Click "Next" to proceed to the rule builder. The button is disabled until you enter a name.

Form Rule Builder

After clicking Next, you land on the full rule builder. This is where you define the logic: which records the rule applies to (FOR) and what happens (DO).

Builder Layout

FOR Options

Click "Save" when done. The rule is created in an active state and immediately applies to forms.

Conditions

When you select "Records matching condition", a criteria builder appears where you define which records the block applies to.

Condition Row

Condition Pattern

When you have multiple conditions, a Condition Pattern appears showing how they combine. By default, all conditions use AND logic (all must be true). Click the pattern to edit it and use OR logic or custom combinations like (1 AND 2) OR 3.

Actions

Actions define what happens when the block's condition is met. Add actions from the "Add Action" dropdown in the DO section.

Action Types

After Adding an Action

Once you add an action, a Target Field dropdown appears. Select the field this action should affect. You can add multiple actions to the same block — they all execute when the condition is met.

Multiple Blocks

Click "Add Condition" at the bottom to add another block. Each block is independent — it has its own FOR condition and DO actions. Blocks are evaluated in order and can be reordered by dragging.

Real-World Use Case

Equipment rental company building a custom Reservations module

A construction equipment rental company needs to track reservations — which customer booked which machine, for what dates, at what rate. No generic CRM module fits, so they build one from scratch using the Module Builder.

1. 1Create a Reservations module with sections: "Booking Details", "Equipment", "Pricing", and "Status"
2. 2Add a Lookup field linking to the Customers module and another linking to the Equipment module
3. 3Add Date fields for Pickup Date and Return Date
4. 4Add a Currency field for Daily Rate and a Formula field that calculates Total Cost (Daily Rate × number of days)
5. 5Add a Dropdown field for Status with options: Reserved, Picked Up, Returned, Cancelled
6. 6Add an Item Table for accessories included with the rental (safety gear, attachments, etc.)
7. 7Use the Permissions tab to make the "Daily Rate" field read-only for the Operations team (only managers can set pricing)

Common Workflows

Add a new field to a module

1. 1Go to Settings → Modules and click the module name
2. 2In the Layout tab, find the field type in the left panel (e.g., "Dropdown")
3. 3Drag it into the desired section in the center panel
4. 4In the right panel, enter a Field Label
5. 5Configure properties: toggle Required, set Help Text, add options (for dropdowns)
6. 6The field is saved automatically when you drop it

Reorganize your form layout

1. 1Open the module in the Layout tab
2. 2Drag fields up or down within a section to reorder them
3. 3Drag fields between sections to move them to a different group
4. 4Use the section header's arrow buttons to reorder entire sections
5. 5Drag a Section from Field Types to create a new grouping

Configure the card view

1. 1Open the module and click the Card View tab
2. 2Click fields in the Available Fields list to add them (up to 5)
3. 3Drag selected fields to reorder how they appear on the card
4. 4Check the Preview panel to see how it looks
5. 5Click "Save Card View configuration"

Create a conditional form rule (show a field based on another field's value)

1. 1Open the module and click the Form Rules tab
2. 2Click "Create Form Rule"
3. 3Enter a descriptive name (e.g., "Show Reason when Lost")
4. 4Set Trigger On to "Create or Edit"
5. 5Click "Next"
6. 6In the builder, select "Records matching condition"
7. 7Click "Add Condition"
8. 8Set the condition: Field = "Status", Operator = "Equals", Value = "Lost"
9. 9In the DO section, select "Show Field" from the Add Action dropdown
10. 10Set Target Field to "Loss Reason"
11. 11Click "Save"

Make a field required only in certain situations

1. 1Create a form rule (follow the steps above through step 8)
2. 2In the DO section, select "Mark Required" from the Add Action dropdown
3. 3Set Target Field to the field you want to make conditionally required
4. 4Click "Save"