Skip to main content
Fields define what information you capture for each record. Twenty offers a variety of field types to match any data structure.

​
Understanding Fields

Fields are the individual data points in your objects:
  • Text - Names, descriptions, notes
  • Number - Quantities, prices, scores
  • Date - Deadlines, birthdays, timestamps
  • Select - Status, priority, category
  • Relation - Links to other records
  • And many more…

​
Adding a Field

1

Navigate to object settings

Go to Settings → Data Model → Objects and select your object.
2

Go to Fields tab

Click the Fields tab to see all fields for this object.
3

Click New Field

Select + New Field in the top right.
4

Choose field type

Select the type that matches your data (Text, Number, Date, etc.).
5

Configure field settings

Set the field name, description, and type-specific options.
6

Save the field

Click Save to add the field to your object.
New fields appear in table views automatically. You can reorder them in the view settings.

​
Field Types

​
Basic Field Types

Store short or long text content.Use cases:
  • Names and titles
  • Descriptions
  • Email addresses
  • URLs
  • Notes and comments
Options:
  • No specific configuration required
  • Supports multi-line text
  • Full-text searchable
Example:
Field: Project Description
Value: "Redesign the company website with modern UI"

​
Advanced Field Types

Choose one option from a predefined list.Configuration:
  1. Add options with labels and colors
  2. Set a default option (optional)
  3. Reorder options as needed
Example - Project Status:
Options:
  - Not Started (gray)
  - In Progress (blue)
  - On Hold (yellow)
  - Completed (green)
Default: Not Started
Use colors strategically to show status at a glance. Green for positive states, red for issues, yellow for warnings.
Choose multiple options from a list.Use cases:
  • Tags and categories
  • Skills and capabilities
  • Product features
  • Team roles
Example - Project Tags:
Options:
  - High Priority
  - Client-Facing
  - Internal
  - Revenue-Generating
  - Research
Records can have any combination of these tags.
Link to records in another object.Types:
  • One-to-many - A company has many people
  • Many-to-many - Projects have many team members, people work on many projects
Configuration:
  1. Select the related object
  2. Choose relation type
  3. Name the relation field
  4. Optionally create the inverse relation

Learn More

See the Relations guide for detailed examples
Store star ratings (1-5 scale).Use cases:
  • Lead quality scores
  • Customer satisfaction
  • Priority rankings
  • Performance ratings
Example:
Field: Lead Quality
Value: 4
Display: ★★★★☆
Attach documents and files to records.Use cases:
  • Contracts and agreements
  • Presentations
  • Images and screenshots
  • Documents and PDFs
Features:
  • Multiple files per field
  • File preview
  • Version history
  • Direct download
Store a list of text values.Use cases:
  • Email aliases
  • Phone numbers
  • URLs
  • Keywords
Example:
Field: Contact Emails
Values:
  - [email protected]
  - [email protected]
  - [email protected]
Store structured data in JSON format.Use cases:
  • API responses
  • Configuration data
  • Complex nested data
  • Integration payloads
Example:
{
  "features": ["sso", "api", "webhooks"],
  "limits": {
    "users": 100,
    "storage": "50GB"
  }
}
JSON fields are not searchable or filterable in views.
Auto-generated unique identifier.Use cases:
  • Record IDs
  • External system IDs
  • Reference numbers
Features:
  • Automatically generated
  • Guaranteed unique
  • UUID format
  • Read-only

​
Field Settings

When configuring a field, set these properties:

​
Basic Settings

Name

The field label shown in the interface. Use clear, descriptive names.

Description

Explain what the field is for. Helps team members use it correctly.

Icon

Visual identifier for the field in views and forms.

Type

The kind of data stored (Text, Number, Date, etc.). Cannot be changed after creation.

​
Field Behavior

  • Required - Field must have a value (coming soon)
  • Unique - Each record must have a different value (coming soon)
  • Default value - Automatically populated for new records

​
Display Options

  • Show in table - Include in default table views
  • Position - Order in forms and views
  • Width - Column width in table views

​
Field Validation

Some field types have built-in validation:
Field TypeValidation
NumberMust be numeric
DateMust be valid date
Date/TimeMust be valid timestamp
SelectMust be one of the options
RelationMust reference existing record

​
Example: Building a Complete Object

Let’s add fields to a Contract object:

​
Essential Fields

1. Contract Name (Text)
   - Label identifier field
   - Example: "Annual Service Agreement - Acme Corp"

2. Contract Type (Select)
   - Options: Service Agreement, NDA, Master Agreement, SOW
   - Default: Service Agreement

3. Status (Select)
   - Options: Draft, Under Review, Active, Expired, Terminated
   - Default: Draft
   - Colors: Gray, Yellow, Green, Red, Red

4. Company (Relation)
   - Links to Companies object
   - One-to-many relationship

5. Contract Value (Number)
   - Format: Currency
   - Example: 50000

6. Start Date (Date)
   - When contract begins

7. End Date (Date)
   - When contract expires

8. Auto-Renew (True/False)
   - Default: false

9. Owner (Relation)
   - Links to People object
   - Account manager responsible

10. Contract File (Files)
    - Attach PDF of signed contract

11. Terms (Text)
    - Multi-line description of key terms

12. Renewal Notice Days (Number)
    - Days before expiry to send notice
    - Default: 30

​
Managing Fields

​
Editing Fields

  1. Go to Settings → Data Model → Objects → [Object] → Fields
  2. Click the field you want to edit
  3. Modify settings (some restrictions apply)
  4. Save changes
You cannot change a field’s type after creation. Create a new field and migrate data instead.

​
Reordering Fields

In the Fields tab:
  1. Click and drag the handle icon (☰)
  2. Move the field to desired position
  3. Order affects display in forms and default views

​
Deactivating Fields

To hide a field without deleting data:
  1. Click the field in settings
  2. Select Deactivate
  3. Field data is preserved but hidden from views

​
Deleting Fields

Deleting a field permanently removes all data. This cannot be undone.
Standard system fields cannot be deleted.

​
Field Best Practices

Select types that match your data:
  • ✅ Use Number for prices, not Text
  • ✅ Use Date for deadlines, not Text
  • ✅ Use Select for statuses, not Text
  • ✅ Use Relation to link objects, not Text
Proper types enable filtering, sorting, and validation.
Use descriptive names that make sense to all users:
  • ✅ “Project Budget”
  • ❌ “Budget”
  • ✅ “Contract End Date”
  • ❌ “Date2”
Explain what goes in the field:
✅ "Annual contract value in USD, excluding one-time fees"
❌ "Contract value"
Default values save time:
  • Status fields: Start with “Draft” or “New”
  • Boolean fields: Set to most common value
  • Dates: Use “Today” for creation date fields
If a field has a fixed set of values, use Select:
  • Priority: Low, Medium, High
  • Status: Open, In Progress, Closed
  • Type: categorized options
This enables better filtering and prevents typos.
Start with essential fields only:
  1. Add core fields needed for basic workflows
  2. Use the object for a while
  3. Add more fields based on actual needs
Too many fields makes data entry overwhelming.

​
Field Limits

  • Maximum fields per object: 100
  • Field name length: 100 characters
  • Text field max length: Unlimited
  • Select options per field: 50

​
Next Steps

Defining Relations

Connect objects with relationships

Table Views

Work with your fields in table format

Filters and Sorting

Use fields to filter and organize data

Build docs developers (and LLMs) love

Get started for freeTalk to us