Sections

The reusable data unit of a Journey Manager App — bound to a View, it defines fields, field linking, creation rules, and the layout pages that present its records.

A Section is the reusable data unit of a Journey Manager App. It binds to a View — which sets the object type, the filters, and the available fields — and exposes one or more layout pages that present those records. One section can be reused across many apps.

Properties

Property	Type	Required	Description
title	string	Yes	Display name.
slug	string	Yes	Identifier (a–z, 0–9, -); unique.
icon	string	No	Icon shown for the section.
description	string	No	What the section is for.
object_type	string	Yes	The kind of object the section manages — for example contacts, content instances, documents, or orders.
type	string	Yes	The section subtype.
view_id	reference	Yes	The bound View. Must exist; changing it re-seeds the fields from the new View.
fields	array	No	Per-field display and link configuration.
layout_pages	array	No	The layout pages this section exposes.
allow_exports_generation	boolean	No	Enables exports for the section.
creation_rules	object	No	Rules for record creation.

View binding & fields

A section’s data comes entirely from its bound View: the View decides the object type, which records appear (its filters), and which fields are available. When you set or change the view_id, the section’s fields are re-seeded from that View’s fields, so the section always reflects the View it points to. You then customize each field’s display — its label, whether it’s sortable, and whether it links elsewhere.

Field linking

A field can declare a link so its value becomes a clickable drill-down into another section’s layout page — for example, a contact name that opens the contact’s Single Record page, or an order number that opens the order detail. When you save, the link is enriched with the target’s title and slug. A section may link to its own Single Record page (a self-reference), which is the common pattern for “click a row to open its detail.”

Creation rules

For sections whose users create records, creation rules scope and route that creation:

• Picker scoping — restrict the pickers on a creation form to the records returned by a chosen View (for example, limit which contacts or locations a user can select).
• Related record routing — map a related record to the Single Record page that should open when a user navigates to it, so drill-downs land on the right detail page.

Layout pages

A section holds one or more layout pages — each a different way to present the same records. The full catalog of list and visualization types, with the configuration each one needs, is on the Layout pages page; the detail and creation experiences are on the Single Record pages page.

Exports

When allow_exports_generation is on, users can export the section’s records. Exports run in the background and produce CSV and JSON files, with a notification when the download is ready. Apply filters before exporting to keep the output focused.

Behaviour & rules

A section can’t be deleted while it’s linked to an app. Detach it from every app first, then delete it.

Related

Layout pages

Every way to present a section’s records.

Single Record pages

The record detail view and the New Record form.

Views

The data source every section binds to.

App Designer

How an app’s navigation points at sections.