Field library

Save a group of fields once — an address block, a signature section, a standard disclosure — and insert it into any form. Inserting copies the fields into the form; nothing references the group afterwards, which is exactly what keeps published forms immutable.

Saving a group

In the builder, the Field library panel sits beside the palette. Save this page as a group captures the current page's fields under a name and publishes them to your organisation's library. Groups version like everything else: editing one clones a draft, publishing replaces the live version, and publishing runs the same field-level checks a form's own publish runs — a group whose fields would be refused on a form is refused as a group, with the same messages.

Inserting one

Insert copies the group's live fields onto the current page as ordinary fields. The copy is careful about identity: slugs that would collide with the form (or with a previous insertion of the same group) are renamed, and the group's internal references — a total's formula naming its siblings, a summary panel's rows, a cascading picker's parent — are rewritten to match. References to fields outside the group are left alone, so a group's formula may deliberately name a field it expects the form to have.

Each inserted field carries a small provenance stamp recording which group and version it came from. It is a label, not a link: the engine ignores it, and nothing about the form resolves through the group afterwards.

Styled fields

A field can carry its own look — label and text colors, background, border, accent, corner radius, and a scoped CSS escape hatch — set in the inspector's Style section. Describe a look in plain English and the AI proposes one onto the canvas for you to keep, tune or clear; nothing applies to submitters until you save and publish. Styles render on the public form page and in the builder's preview; the app's own screens keep the app's theme.

A styled field saved to the library is a reusable style: insert it as a new field, or use Copy a saved style in the inspector to put its look onto a field you already have. Styles pass the same publish fence as everything else — colors must be real hex, the CSS is size-capped and may not contain < or @import — and a stored style that predates those checks degrades safely rather than breaking the page.

Copy, deliberately — not reference

A form that changed because somebody edited a library group would break the platform's oldest promise: a published version is immutable, and a submission keeps the definition it was filled against. So insertion copies, editing a group affects only future insertions, and archiving a group breaks nothing that already used it. If you need the same fix in five forms that share a block, update the group and re-insert — the stamp tells you which forms carry which version.

Who can use it

The library needs the same permission as building forms. Groups belong to your organisation and are isolated the way everything else is; they do not travel with cross-organisation form shares.