All topics
English

Module fields · 2 min read

Edit, hide and deactivate fields safely

Distinguish required, visible and active settings while preserving data already in use.

In this guide
  1. What you can change after creation
  2. Three different controls
  3. Change and verify the settings
  4. Introduce requirements without disrupting work
  5. Related guides

For Insurance agency Owners and administrators.

What you can change after creation

Open the card’s Edit field pencil. Review label, description, options, section and usage controls. The editor locks API name and type. Renaming a label does not populate values or translate existing records.

Before changing a used list, check example records, saved filters and processes that rely on its options. Renaming Received to Documents received should not be treated as migration of every existing value.

Three different controls

ControlEffect
Required fieldRequires a value in workflows that validate the field. Consider when the information becomes available.
Show field on module screensControls presentation. Hiding the field removes its required setting.
Active fieldKeeps or withdraws the definition from operational use while preserving existing values.

Hidden is not profile-based protection. Configure Security and data to restrict who can view or edit sensitive values. A field hidden from a form is not a secure vault.

Field hidden in the editor: required setting cleared and activation controlled separately.
Field hidden in the editor: required setting cleared and activation controlled separately. Open the image to enlarge it.

Change and verify the settings

  1. Open the field in the correct module.
  2. Adjust the control. To hide it, clear Show field on module screens and confirm Required field is cleared and unavailable.
  3. To suspend use, clear Active field.
  4. Click Save field and reopen the catalog.
  5. Test an existing record and a new record.
  6. To restore use, reactivate and make it visible as needed; review the required setting again.

There is no field-delete button in this editor. Hiding or deactivating does not erase existing values and is different from clearing a value on an individual record.

Introduce requirements without disrupting work

Start optional, align staff input and review existing data. Make the field required when appropriate for the point in the workflow. In Accounts, Tasks, Deals and Policies, editing another record attribute without changing custom fields does not require retroactively completing every new field.

Imports and internal processes may follow their own rules to preserve operations. Required does not guarantee every historical or imported record has a value. Monitor empty values with filters and plan completion.

Related guides

Updated October 25, 2026.