Data Design — shaping your own records

Data Design lets an org admin design the shape of the records in any module you have turned on — the fields you actually use, arranged the way you work, related to each other and calculated. Open it at /data-design and pick the module you want to design; the tabs are Fields, Layout, and Build with Wally.

Adding a field (Fields tab):
Click "+ New field", give it a Label (it is stored under an automatic key), pick a Type, and add optional help text. The types are Text, Long text, Number, Currency, Percent, Date, Date and time, Checkbox, Email, Phone, URL, Picklist, Multi-select picklist, Geolocation, and three derived kinds below. Non-derived fields can be marked Required, Read-only, or Show in lists.

Relating modules — Lookup fields:
A Lookup (relationship) field stores a reference to a record in another module — never a copy of its values, so the referenced record stays the single source of truth. You choose which module it points at, and what happens when that record is deleted: block the delete (safest), clear the reference, or delete the referrers (destructive).

Calculating — Formula and Roll-up fields:
A Formula field is calculated from your other fields (for example ROUND(cf_amount * cf_rate, 2)); the expression is checked as you type and supports conditionals. A Roll-up summary counts, sums, averages, or takes the min or max of the records in another module that point back at this one. Both are worked out fresh when shown by default; turn on "make it sortable and searchable" on a roll-up only if you need to sort or filter by it.

Rules and field-level security:
Add validation rules with your own error message — when the rule's expression is true, the save is blocked and your message shows next to the field. You can also narrow who may see and who may edit each field by role; narrowing either is enforced on the server, not just hidden.

Layout — order and sections (Layout tab):
Drag fields to reorder them and add "+ Section header" to group them under your own headings. Built-in fields are reorderable and groupable here exactly like custom ones — you can rename, hide, require, and reorder a built-in field, but never remove it. Removing a section header un-groups its fields into the previous section; nothing is lost.

Publishing a field to your website:
Every field is private by default. To let a value appear in a public Builder block, turn on "Allow this field on our public site" for that field — a separate, explicit decision. While it is off, the server refuses to send the value at all, so it never leaves. A field that looks sensitive asks you to acknowledge before it can be published, and a formula or roll-up built on a private field cannot be published until the fields it reads are.