# Field groups and reusable field sets

> Add a Field Group to collect related answers at once, choose where they're saved in your CRM, add Property Information pages, and keep mapping consistent.

## Before you start

- You need a form open in the builder — see
  [Build a form: fields, pages, and rules](https://kb.incenti.co/forms/build-a-form.md) for the palette and
  the rest of the **Builder** tab.
- A Field Group adds several related fields to the current page at once, and
  can optionally save what the respondent enters to a contact, organization,
  address, or property record in your CRM. This page covers each group's
  contents, where its answers are saved, its settings, and the Property
  Information group's separate setup.

## Steps

### Add a field group

In the left panel's palette, under **Field Groups**, click one of:

- **Contact Information** — First Name, Last Name, Email, Phone
- **Organization Information** — Organization Name, Website, Industries
- **Address** — Street Address, Apt/Suite, City, State, ZIP / Postal Code
- **Property Information** — Property Name, Street Address, City, State,
  County, Zip Code, Total Acres, Description

Contact Information, Organization Information, and Address are added to the
page immediately, then open a small dialog asking where the answers should be
saved. Property Information works differently — see
[Add Property Information pages](#add-property-information-pages) below.

### Choose where answers are saved

The dialog that opens after adding a group asks a question specific to that
group's type:

- **Contact Information** — "**Save this contact to your CRM?**" Choose
  **Main point of contact (primary)**, **Additional contact (secondary)**,
  **Other contact**, or **Don't save to CRM — just collect the answers.**
  Only one group on a form can be the main point of contact.
- **Organization Information** — "**Save this organization to your CRM?**"
  Answer **Is this the primary contact's organization?** with **Yes**, **No**,
  or choose not to save to CRM. Only one Organization Information group is
  supported per form.
- **Address** — "**Where should this address be saved?**" Pick a combination
  of target (Primary contact or Organization) and kind (main, mailing, or
  other address), or **Don't save to CRM.** Each combination can only be used
  by one Address group on the form — already-used combinations are shown
  disabled with "(already used)."

Every dialog pre-selects a recommended option, so you can also just click
**Save** to accept it. Click **Cancel** instead and the group you just added
is removed. You can change this choice later from the group's own settings.

_Screenshot: The "Save this contact to your CRM?" dialog after adding a Contact Information field group, with Main point of contact (primary) selected and the Save and Cancel buttons._

### Change a group's settings

On the canvas, a group is shown as one block with its label and a badge such
as "Saves to: Primary contact" summarizing its CRM auto-save choice. Click
the group's header to open **Group Details** in the left panel. You can:

_Screenshot: The Group Details panel for a Contact Information group: Label, the CRM auto-save options with Main point of contact (primary) selected, the read-only Fields list, Additional fields, and the Duplicate Group and Delete Group buttons, with the group highlighted on the canvas._

- Edit the group's **Label**.
- Change its **CRM auto-save** choice — the same options offered in the
  add-time dialog.
- Review its **Fields** (a read-only list).
- For a Contact Information or Organization Information group, add
  **Additional fields**: enter a label, pick a type (Input, Textarea,
  Dropdown, Checkbox, Date, or Phone), optionally toggle **Required**, and
  click **Add field**. Each additional field can be removed individually.
- Click **Duplicate Group** to add a copy of the group to the page, or
  **Delete Group** to remove the whole group — its fields, its CRM auto-save
  setting, and any conditional rules that reference its fields all go with
  it. There's no way to remove just the grouping while keeping the fields as
  standalone questions.

A field that's part of a group shows its CRM mapping as read-only in its own
**Field Details** panel, with a note that it's "Managed by the group's CRM
auto-save setting" — change it from the group's settings instead.

### Add Property Information pages

Clicking **Property Information** in the palette opens **Add property
pages**, where you set a **Minimum properties** and **Maximum properties**
count and choose **Add each property to the properties list** or **Don't
save — just collect the answers.** Clicking **Add pages** inserts that many
property pages into the form — nothing is added to the canvas until you
confirm this dialog.

Property Information has constraints the other groups don't:

- It's only available on a multi-page form, and is disabled with an
  explanation ("Property pages need a multi-page form," "This form already
  has property pages," or "This form already has a Property Information
  group") when those conditions aren't met.
- Only one set of property pages is supported per form.
- A form with property pages can't use **Single Page Mode** (on the
  **Settings** tab).
- Property pages are removed as a set from their own settings panel, not one
  group at a time from **Delete Group**.
- When **Add each property to the properties list** is on, each property a
  respondent submits is matched by its address against the properties you
  already have. A match updates that property; no match creates a new one.

### Change or remove the property pages

In the **Pages** list, the property pages sit under a collapsible
**Properties** group showing the minimum and maximum, with up and down arrows
and a sliders icon that opens the **Property Pages** panel. Pages beyond the
minimum are badged "Hidden until revealed" — they appear to a respondent only
once the rules that manage the set reveal them.

The panel holds:

- **Number of properties** — a **Minimum** and a **Maximum**, then **Apply**.
  Both must be whole numbers between 1 and 20, or you'll see "Minimum and
  maximum must be whole numbers between 1 and 20."; the minimum can't exceed
  the maximum. Lowering the maximum asks you to confirm before it removes the
  pages it no longer needs.
- **Save to properties list** — the same choice you made when adding the pages:
  add each submitted property to your properties list, or just collect the
  answers.
- **Additional fields** — a mini-form for adding your own questions to every
  property page: enter a **Field label**, pick a type (Input, Textarea,
  Dropdown, Checkbox, Date, or Phone), optionally toggle **Required**, and
  click **Add field**. Each one can be removed individually.
- **Removed fields** — catalog fields you took off the pages, each with a
  **Re-add** button.
- **Remove property pages** — removes the whole set. The confirmation dialog
  warns that it "Removes all property pages, their fields, and their rules from
  this form."

### Add a field from the palette to all property pages

While a property page is selected, clicking a field type card in the palette
doesn't add a field to that page alone, because property pages stay
identical. Instead, for a supported type, a confirmation opens: **Add to all
property pages?** It reads "Property pages stay identical, so this _Type_ is
added to each of the _N_ property pages. You can rename or remove it in the
property pages' settings." Click **Add to all pages** to confirm, or
**Cancel** to leave the pages as they are.

Confirming adds the field to every property page as an additional field. It
isn't required, and its label is the type's name (for example, "Date"). The
**Property Pages** settings panel then opens with the new field listed under
**Additional fields**, where its **X** removes it from every property page. To
rename it, select the field on a property page and change its label in the
**Field Details** panel.

Supported types are the same six the **Additional fields** mini-form offers:
**Input**, **Textarea**, **Dropdown**, **Checkbox**, **Date**, and **Phone**.
Other cards, such as **Table**, **Signature**, **Upload**, **Email**, and
**URL**, are disabled on a property page. Hover one to see "_Type_ fields
aren't available on property pages." If the builder refuses to add the field,
a "Couldn't add field" message appears with the reason.

### Legacy Address groups

An Address group created before CRM auto-save existed shows "No CRM auto-save
configured." in **Group Details**, with a **Configure as Address group**
button. Click it to pick a target and kind the modern way; the group then
behaves like any other Address group.

## What happens next

- Whatever CRM auto-save choice you make, a submission creates or updates the
  matching contact, organization, address, or property record automatically
  — no manual data entry.
- A group's answers only fill values the record doesn't already have. Where the
  record holds something different, the existing value is kept and the
  difference is recorded as a sync conflict on the response — see
  [CRM sync and conflicts](https://kb.incenti.co/responses/crm-sync-and-conflicts.md).
- Keeping the same group types mapped the same way across your forms (for
  example, always saving the first Contact Information group as the primary
  contact) is what makes autofill and CRM sync reliable. A public form link
  never pre-fills anything: autofill happens in the portal, after a signed-in
  respondent chooses **Continue in portal** and uses **Autofill with AI** —
  see [Autofill a response](https://kb.incenti.co/responses/autofill-a-response.md).

## Common questions

**Q: Can I add a second Address group?**
A: Yes. Add another Address group and pick a different target/kind
combination in its dialog — for example, the organization's mailing address
after the primary contact's main address is already used. Combinations
already used by another group on the form are disabled.

**Q: Can I change where a group's answers are saved after I've added it?**
A: Yes. Click the group's header on the canvas and change its **CRM
auto-save** choice in the left panel. The same options from the add-time
dialog are offered, and combinations already used by another group on the
form stay disabled.

**Q: Do field groups show up differently to respondents?**
A: A group appears as one block headed by the group's **Label** (for example,
"Contact Information"), with its fields laid out compactly underneath. The
CRM auto-save choice is never visible to respondents; it only affects what
happens after submission.

**Q: Can I add my own field to the property pages from the palette?**
A: Yes, for Input, Textarea, Dropdown, Checkbox, Date, and Phone. Select any
property page, click the field type's card, and confirm **Add to all pages**.
The field is added to every property page, because they stay identical. Other
field types are disabled on property pages.

**Q: I deleted a group by mistake — can I get the fields back individually?**
A: No. **Delete Group** removes all of the group's fields together, along
with its CRM auto-save setting and any conditional rules on those fields.
Add the group again from the palette and reconfigure it.

## Related

- [Build a form: fields, pages, and rules](https://kb.incenti.co/forms/build-a-form.md)
- [Map fields to your CRM](https://kb.incenti.co/forms/map-fields-to-your-crm.md)
- [Field types reference](https://kb.incenti.co/forms/field-types-reference.md)
- [CRM sync and conflicts](https://kb.incenti.co/responses/crm-sync-and-conflicts.md)
- [Review a response](https://kb.incenti.co/responses/review-a-response.md)
