A data layout describes how a single record is displayed — which fields appear, in what order, grouped how, with which read-only vs editable controls. Different audiences need different layouts of the same data: a sales rep, a support agent and a finance person all see the same customer record but care about different parts.
What a Layout Defines
- Field order: Sequence in which fields appear.
- Grouping: Sections with headings (e.g. “Contact”, “Billing”, “Notes”).
- Visibility: Which fields show; which are hidden in this layout.
- Editability: Read-only vs editable per field per layout.
- Related panels: Embedded lists of related records (e.g. customer's orders).
- Tabs: Different layout pages within the same record.
- Layout-specific actions: Buttons available in this layout but not others.
Per-Audience Layouts
One record, many views. Common patterns:
- Internal admin layout: Everything visible, everything editable.
- Internal staff layout: Most fields visible, some restricted to admins.
- Customer-facing layout: Only the customer's own data, minimal editing.
- Read-only audit layout: Everything visible, nothing editable.
- Mobile-optimised layout: Single column, most-important fields first.
Worked Examples
- CRM customer record: Sales view shows pipeline; Support view shows tickets; Finance view shows billing — all of the same record.
- Patient record: Doctor view shows clinical history; Receptionist view shows demographics + appointments; Billing view shows insurance + invoices.
- Product record: Editor view has all fields editable; Public marketplace view shows only the listing fields.
- Mobile field service: Engineer's mobile layout strips out admin fields and pulls in job-specific actions.