EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

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:

TypeUse it for
textNames, tiers, external references, and short notes
numberScores, quantities, limits, and other numeric values
dateRenewal dates, review dates, and contract milestones
booleanYes-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

  1. Open Settings → Customer fields.
  2. Enter a field name, such as Account manager.
  3. Select Add, or press Enter.
  4. Choose the field type.
  5. Add any other fields that the workspace needs.
  6. Select Save changes.
  7. Wait for Custom fields saved.
  8. 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:

  1. Review the values already stored on customers.
  2. Confirm that they can be represented by the new type.
  3. Update the field during a coordinated maintenance window when many operators use it.
  4. 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

FieldTypeExample
Account managertextMorgan Lee
Contract tiertextEnterprise
Renewal datedate2027-01-31
Health scorenumber82
Legal review requiredbooleanYes

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.

Related Pages

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

Command Center

Triage the finance signals that need attention, then open the source record or forecast.

Customer Lifecycle

Learn how Eigenn creates, enriches, uses, retains, and permanently deletes a customer record.

On this page

Where Customer Fields LiveSupported Field TypesAdd a FieldRename a FieldChange a Field TypeRemove a FieldChoose Useful FieldsExample Field SetAccess and GovernanceTroubleshootAdd says the field already existsThe new field does not appear on a customerExisting values look wrong after a type changeA removed field still has dataA teammate cannot save field definitionsRelated Pages

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesApproval PoliciesAssistant AutomationAssistant Command CenterAssistant Workspace and Saved WorkBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer FieldsCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionFiles and Document VaultFinancial Analytics and ReportsFinancial OverviewInbox and ApprovalsInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewPlanning Data and DimensionsPlanning Models and FormulasPlanning Time and ActualsPlanning UncertaintyPlanning Versions and CollaborationPlanning Views and ExportsReceivablesReceivables AnalyticsReceivables ControlsScenario PlanningSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransaction CodingTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow OutcomesWorkflow PausesWorkflows
OverviewBuild a Driver-Based Planning ModelBuild and Review a ForecastBuild Your First WorkflowCollaborate on a Planning ModelCompare and Share Planning ScenariosConfigure Approval PoliciesConfigure Assistant OperationsConfigure Customer FieldsConfigure Notifications and BrandingConfigure Planning Time and ActualsConfigure Receivables ControlsConnect Planning Data and ActualsConnect Transaction RecordsCreate and Manage CustomersCreate and Send InvoicesCreate Your First Planning ModelDeveloper API SetupFirst Cash ReviewInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsReview a Customer Finance RecordReview, Restore, and Export a Planning ModelRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Planning Uncertainty AnalysisRun Your First Command Center ReviewSave and Share Assistant WorkSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsRemote Tracker API StatusTracker Categories APITracker Entries and Timers APITracker Projects APITransactions APIWebhooks API StatusWorkflows API
Overview
Overview