Configure Customer Fields

This guide creates business-specific customer fields that remain consistent across the workspace.

Before You Start

• List the customer facts that operators repeatedly need.
• Remove anything already covered by standard customer, invoice, payment, or risk fields.
• Choose an owner for each proposed field.
• Decide the correct type for each value.
• Use a role that can change workspace settings.

1. Design a Small Field Set

Start with no more than the fields needed for one operating process.

Example:

Define how the team should enter each value before you add it.

2. Open Customer Fields

1. Select Settings.
2. Select Customer fields.
3. Review the current definitions.
4. Confirm that a similar field does not already exist.

A differently punctuated name can normalize to the same field key.

3. Add the Definitions

For each field:

1. Enter the field name.
2. Select Add, or press Enter.
3. Choose text, number, date, or boolean.
4. Check the label.

Create a new field when the business meaning is distinct. Do not reuse an old key for a different concept.

4. Save the Workspace Field Set

Select Save changes and wait for Custom fields saved.

The definitions affect every customer record in the active workspace. They do not create values automatically.

5. Add Representative Values

Open several different customer records and enter values.

Use at least:

• one typical customer
• one customer with a blank or unknown value
• one edge case, such as a very large number or a future date

Confirm that the type supports the real values that operators need.

6. Test the Operating Process

Ask the intended operator to:

1. Find the field on a customer.
2. Enter or update a value.
3. Explain the meaning of the value.
4. Use it in the review or handoff that motivated the field.

Rename an unclear label before many records use it.

7. Document Ownership

Record:

• who maintains the value
• when it must be updated
• what blank means
• the allowed text or numeric range when necessary
• whether the field can affect a decision

Eigenn stores the field and value. Your operating process defines its meaning.

8. Change a Field Safely

Before a rename or type change:

1. Review existing values.
2. Confirm that the meaning stays the same.
3. Tell the operators who maintain it.
4. Make the change under Settings → Customer fields.
5. Select Save changes.
6. Check representative customers.

A rename keeps the stable key. A type change can make existing values difficult to interpret, so verify them carefully.

9. Remove an Unused Field

Before removal:

1. Confirm that no active process needs it.
2. Export or record important values when necessary.
3. Remove the definition.
4. Select Save changes.
5. Confirm that the field no longer appears on customer records.

Eigenn keeps previously saved values against the hidden key. Removal is not the same as erasing all historical values.

Review Checklist

A useful customer field has:

• one clear business meaning
• the correct type
• a known owner
• a defined update cadence
• representative values tested
• no duplicate standard field
• a plan for blank and historical values

Troubleshoot

A field name is rejected as a duplicate

Choose a meaningfully different name. Spacing and punctuation do not always create a distinct key.

Operators enter inconsistent text values

Document the allowed terms. When the value is truly yes or no, use a boolean field instead.

A field disappears after removal

This is expected. The saved values remain hidden. Re-add the same field only when the workspace intends to restore that workflow.

The field does not appear after saving

Reload the customer record and confirm the active workspace. Check that the settings save succeeded.

Related Pages

• Customer Fields
• Create and Manage Customers
• Customer Finance Records
• Settings Overview