Fields define the information stored in CRM records, describing attributes of People, Companies, Opportunities, and custom entities. They enable teams to capture structured data, filter records, automate workflows, and generate AI insights.

Default Fields

Core entities come with predefined fields like Name, Job Title, Emails, Phones, Company, and City. These standard fields ensure consistency across the workspace and cannot be deleted, though they can be hidden from views if irrelevant to your workflow.

Field Visibility

In Table or Kanban views, open the view's fields settings to:

Select which fields display
Hide unnecessary fields
Reorder fields according to your priorities

Hiding a field in a view never deletes its data; other views can still show it. See Managing views.

Adding Custom Fields

There are two ways to add a custom field:

From the workspace: Open the entity table → add a field from the table's field options
From Settings: Settings → Entities → select the entity → create a new field, choosing its type and configuration

When creating a custom field, you configure its type, name, options or settings, and an optional description. Adding descriptions is recommended for AI accuracy.

Available Field Types

Basic types

Text: free text input
Number: numeric values
True/False: checkbox fields
Date and Time: deadlines and timestamps
Rich Text: formatted notes

Choice types

Select: single option from a list
Multi-select: multiple options simultaneously
Status: like Select, but representing progression through a process (e.g., Discovery → Proposal → Closed Won / Closed Lost); Status fields drive Kanban columns

Contact types

Emails, Phones, Links: structured contact information with primary + additional values
Full Name: first and last name
Address: structured postal address

Advanced types

Currency: formatted monetary amounts
Relation: links to records of another entity
Actor: who created or owns something
Unique ID: auto-generated identifiers
JSON / Array: structured data for technical use cases

Select vs. Multi-select vs. Status

Select: stores one value per record: best for categories (Industry, Lead Source)
Multi-select: stores multiple values: best for tags (Interests, Product Lines)
Status: one value that represents a step in a process: best for stages, and required for Kanban views, whose columns group records by a Status or Select field

Status fields also enable Dalil to analyze conversion and pipeline health across stages, and give workflows clean stage-change events to trigger on.

Field Descriptions

Descriptions clarify how fields should be used across the team and provide context for AI analysis, enabling more accurate signals, insights, and automation. AI features like scoring, enrichment, and sequence variables all read your fields, so well-named, well-described fields directly improve AI output.

Managing fields