Customer Fields
Define team-wide customer fields for business-specific data that should be comparable across customer records.
Customer fields let a workspace track business-specific data that does not fit the standard customer record. Define the fields once under Settings. Eigenn then shows the same field set on each customer.
Use customer fields for values such as account manager, contract tier, renewal date, customer segment, or a risk-review flag.
Where Customer Fields Live
- Open Settings → Customer fields to define the workspace field set.
- Open a customer record to enter values for that customer.
Field definitions belong to the workspace. Field values belong to the individual customer.
Supported Field Types
You can create:
| Type | Use it for |
|---|---|
| text | Names, tiers, external references, and short notes |
| number | Scores, quantities, limits, and other numeric values |
| date | Renewal dates, review dates, and contract milestones |
| boolean | Yes-or-no conditions such as strategic account or legal review required |
A new field starts as text. Change the type after you add it.
Choose the type that matches the value that operators will enter. A consistent type makes the field easier to compare and validate.
Add a Field
- Open Settings → Customer fields.
- Enter a field name, such as Account manager.
- Select Add, or press Enter.
- Choose the field type.
- Add any other fields that the workspace needs.
- Select Save changes.
- Wait for Custom fields saved.
- Open a customer and confirm that the new field appears.
Field names must produce a unique workspace key. Two names that normalize to the same key cannot both be added.
Rename a Field
Edit the field label, then select Save changes.
Eigenn keeps the field's stable key when the label changes. Existing customer values remain attached to that field.
Use a rename when the business meaning stays the same. Create a new field when the meaning or data type changes substantially.
Change a Field Type
Choose a different type, then save.
Before you change a type:
- Review the values already stored on customers.
- Confirm that they can be represented by the new type.
- Update the field during a coordinated maintenance window when many operators use it.
- Check representative customer records after the save.
A label or type change affects the shared definition for every customer.
Remove a Field
Select the remove control beside the field, then select Save changes.
Removing a field hides it from the active field set. Eigenn keeps values that were already saved against its stable key. This protects historical data if the field returns later, but operators should not depend on hidden values as an active workflow.
Export or record important values before you remove a field from a business process.
Choose Useful Fields
Good customer fields are:
- used across many customer records
- owned by a known person or process
- specific enough to interpret consistently
- stable enough to compare over time
- not already represented by a standard Eigenn field
Avoid fields that duplicate invoice status, payment status, risk calculations, or notes that already have a dedicated product surface.
Example Field Set
| Field | Type | Example |
|---|---|---|
| Account manager | text | Morgan Lee |
| Contract tier | text | Enterprise |
| Renewal date | date | 2027-01-31 |
| Health score | number | 82 |
| Legal review required | boolean | Yes |
Document the meaning of each field in the team's operating process, especially numeric scores and boolean flags.
Access and Governance
Customer field definitions affect the whole workspace. Coordinate changes with the people who manage customer records, receivables, and reporting.
Use a role with permission to change workspace settings. A visible control does not guarantee that the server will accept the change.
Review the field set periodically. Remove abandoned fields, correct unclear labels, and avoid many overlapping versions of the same concept.
Troubleshoot
Add says the field already exists
Choose a more distinct name. Field keys are normalized from the name, so punctuation or spacing alone may not make the key unique.
The new field does not appear on a customer
Confirm that you selected Save changes, then reload the customer record. Also confirm that you are in the same workspace where the field was created.
Existing values look wrong after a type change
Return to Settings, confirm the intended type, and inspect representative customers. Restore the prior type when the existing values cannot be interpreted safely.
A removed field still has data
Removal hides the field definition but keeps previously saved values. This is expected. Re-add the same field only when the workspace intends to use those values again.
A teammate cannot save field definitions
The shared definition needs workspace-settings permission. Ask a workspace owner to make the change.