Customer and resource layouts

A layout is the shape of a form. It decides which fields appear when somebody adds a customer or a resource, how those fields are grouped, and which ones can still be changed later.

Open Settings, pick the brand in the Scope selector, then click Customer layout & fields or Resource layout & fields.

You need the Brand Administrator or Tenant Admin role.

Note

Layouts cover customers and resources. Job forms work differently: each job type carries its own operator and resource forms, built in the form builder.

The builder

Three panels. Components on the left is what you can add, Layout Canvas in the middle is the form, and Properties on the right shows the settings for whatever you’ve clicked.

Build from the outside in: drag a Panel onto the canvas, drop a Section into one of its columns, then drag fields into the section. Drag anything up or down to reorder it.

An empty brand opens with a sensible starting arrangement already on the canvas, so you’re editing something rather than staring at a blank page.

The palette lists the record’s own fields, grouped by category, and any custom fields you’ve set up for customers or resources. A field already on the canvas is marked as added, so you don’t place it twice. Custom fields decide what exists across your whole organisation. The layout decides which of them this brand shows, and where.

Panel, Tab Container, Section, Heading, Divider and Rich Text are the same building blocks as the job form builder, and they behave the same way. Click a panel to set its title, how many columns it has, whether it collapses, and whether it starts open.

Field settings

Click a field and the Properties panel gives you its Label, a Required switch, and a Read-only switch.

Under Visibility Settings you decide when the field can be touched.

• Editable when creating: somebody adding a new record can fill this in.
• Editable when editing: somebody opening an existing record can change it.
• Visible in view mode: the field shows when the record is only being read.

Turning off editing on an existing record is how you pin down something that shouldn’t drift after setup, such as an account reference.

Conditional Visibility hides a field until the conditions you set are met, and Conditional Required leaves it optional until they are. Pick another field on the form, pick a test, give it a value. Add more than one condition and all of them have to be true. Sections and tabs take visibility conditions too, so you can hide a whole block.

Hiding a field never deletes what’s in it. The data stays; the form just stops showing it.

Naming it and choosing who sees it

Layout Settings in the top right opens a panel with the rest.

Layout Name is what you call this arrangement. System Default marks it as the one anybody uses when nothing more specific applies. Role Assignments lets you tick the roles this layout is for, so you can point it at your operators or your managers.

Checking it before you save

Preview shows the form as your team will meet it, with tabs for Create, Edit and View. Flick between them: it’s the fastest way to catch a field that’s readable but not editable when it should be.

Save Layout commits your changes. The builder also keeps a draft as you work and offers it back next time you open the layout, and it warns you before you leave with unsaved changes.

Keeping forms usable

Show the fields your team actually fills in and hide the rest. Group them under headings that match the conversation your office has with a customer, so the form reads top to bottom in the order somebody would ask the questions. A short form gets filled in properly; a long one gets half-filled.

What’s next

• Custom fields: create the fields you place here
• The form builder: the same idea for job forms
• Adding a customer: the form your team will see