Browse the Knowledge Center

Managing fields

Configure standard and custom fields on People, Companies, Opportunities, pipelines and custom entities, and tag records without a tags field.

Updated October 25, 2026 · 6 min read

Video:Add a custom field1:08 All videos →

Fields define the information stored in CRM records, describing attributes of People, Companies, Opportunities, pipelines and custom entities. They enable teams to capture structured data, filter records, automate workflows, and generate AI insights. Every field shows up as a column in your tables.

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 a Table or Kanban view, open the view's Settings, then Fields, to:

Select which fields display
Hide a field with the eye icon
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 table: on the entity's list (for example People), open Settings and click Add Custom field
From Settings: Settings → Data → Entity → open the entity → Fields → Create Field. For a pipeline, use Settings → Data → Pipeline instead (see Working with pipelines)

When creating a custom field, you pick its Field type, give it a name, set its options or settings, and add an optional description. For a Select field, add each option, give it a colour, and use the option's menu to make one the default. Click Create field, and the field is a new column on your list, ready to fill in.

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: one value that represents a step in a process

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
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) and for stages
Multi-select: stores multiple values from a fixed list (Interests, Product Lines)
Status: one value that represents a step in a process

Kanban views group their columns by a Select field, and so does grouping in a table. If you want a board for a process, store its stages in a Select field. Pipeline stages are a Select field too.

Tagging records

Vetta has no built-in tags field. The simplest way to tag records is a custom Text field:

Add a Text field, for example Tags.
Type the tags on each record, for example "webinar, partner".
In any view, filter on that field with Contains and a tag, such as "webinar", to see every record that carries it.

A Text field takes any new tag on the spot. A Multi-select field also works when your tags are a fixed list, but each new tag has to be added as an option in the field's settings before you can use it on a record.

💡

Separate tags with commas and pick one spelling for each. Contains matches any part of the text, so a filter for "partner" also finds "partners", while a typo such as "parnter" is missed.

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 Vetta Brain, enrichment, and sequence variables all read your fields, so well-named, well-described fields directly improve AI output.

Common questions

Can I delete a standard field like Job Title or City?

No. Standard fields can't be deleted, but you can hide them from any view where they're not relevant. See Default fields.

Does hiding a field delete its data?

No. Hiding a field in a view never deletes its data, and other views can still show it. See Field visibility.

How do I add a custom field?

Either from the table (open the view's Settings and click Add Custom field) or from Settings → Data → Entity, where you open the entity, go to Fields and click Create Field. See Adding custom fields.

How do I add a field to a pipeline?

Use Settings → Data → Pipeline instead of the Entity page, open the pipeline and create the field there. See Adding custom fields and Working with pipelines.

Select, Multi-select or Status: which one do I need?

Select stores one value per record, best for categories and stages. Multi-select stores several values from a fixed list. Status stores one value that represents a step in a process. See Select vs. Multi-select vs. Status.

Why can't I create a Kanban board on my entity?

Kanban columns are grouped by a Select field, so the entity needs one first. Add a Select field that holds the stages, then create the board. See Select vs. Multi-select vs. Status and Managing views.

How do I tag records?

Vetta has no built-in tags field. Add a custom Text field, type the tags on each record separated by commas, and filter on it with Contains in any view. See Tagging records.

Why does my filter for "partner" also show "partners"?

Contains matches any part of the text, so "partner" matches "partners" too. A typo such as "parnter" is missed, so pick one spelling for each tag. See Tagging records.

Key outcome

You can now hide, add and describe fields on any entity or pipeline, choose the right field type for each piece of data, and tag records with a Text field and a Contains filter. Clean, well-described fields make your views, workflows and AI features more accurate.

Still stuck?

We reply the same business day, 9:00 to 17:00 CET, Monday to Friday.

Contact support