Add, edit and remove a field

A field is one piece of information on a contact — a budget, a car model, an appointment date. This page covers creating one, changing one, and the difference between taking a field off a single database and deleting it from the workspace. About 5 minutes per field.

Before you start

You can open Database Configuration — the gear beside a database in the sidebar
You have the Table Settings permission. Without it the Add field or section button is not on screen at all, and field rows do not open
Decide which database the field belongs to first. Every database reads the same field library, but each one chooses which fields it shows

Steps

Pick the database the field belongs to

Open Database Configuration, then click that database’s chip in the row along the top — Leads for the built-in one. The left pane switches to that database’s own list: the Pinned in Leads group, the Row rail row, then a group for each section.

Only the fields this database shows are listed. There is no hidden-fields bucket here — a field the database does not hold is simply absent from the list.

Click Add field or section

It is the dashed, full-width button at the top of the list. A popup opens with a search box whose placeholder reads Search fields to add….

If this button is missing rather than greyed out, you do not have the Table Settings permission

Reuse an existing field, or start a new one

The popup lists every field in the workspace that this database does not already show. Each row carries the field’s name, a pill naming its type, and a dropdown whose placeholder reads Add to….

To reuse a field, open its Add to… dropdown and choose where it should land. Pinned is offered first, then every section by name. The field drops into that group and its row flashes.
To create a new field, click Create field in the popup footer.

Clicking a row’s name instead of its dropdown opens that field’s editor rather than adding it.

Add to… lists Pinned first, then your sections by name. Pinned drops off the list once it is full

If your search matches nothing the popup says No matching fields. If the database already holds every field in the workspace it says Every field is already in this view.

Name it and pick its type

The field editor opens in the right pane — on a phone it rises as a bottom sheet. It starts on a draft called New Field, type Text, section Other.

Type the real name over the header input (its placeholder is Field name…), set Type, fill in whatever settings that type brings with it, then set Section — the group it will sit in on the record card. See Choose a field type for what each type offers.

Top to bottom: the back chevron, the name, the eye that controls the table column, Type, Automations, Section

Stack several new fields before saving and the drafts are named New Field 2, New Field 3 and so on, so you can tell them apart.

Press Create field

The button sits at the bottom of the editor. It reads Creating… with a spinner while it runs, then the field appears in the list and on the Preview of the record card on the right.

While a field is still being created there is no Remove control — the only way out of a half-made field is Cancel, which throws the draft away.

Save

Click Save changes in the footer. A toast reads Database config saved, and the table behind the screen picks up the new column.

Create field writes to the server immediately. The field itself does not wait for Save changes — it is created the moment you press the button, so it has a real identity. Everything else about it (its section, its position, its column visibility) still saves with Save changes, and a later Discard deletes the fields you created in that sitting.

Edit a field that already exists

Click the field’s row to open its editor. You can also get there from the table: click a column header’s chevron and choose Edit field….

Inside the editor, top to bottom:

Control	What it does
The back chevron (Back to fields)	Closes the editor and returns to the list
The name input	Renames the field everywhere — every database, every record card
The eye, top right	Whether this field is a column in this database’s table. See Choose and pin your table columns
Type	What kind of value the field holds, and what it looks like to fill in
Automations	AI Auto-Fill, and on a date field Sync to Google Calendar
Section	Which group the field sits in on the record card
Remove, bottom left	Takes the field off this database, or deletes it outright

Picking a section also adds the field to the database you are in. If you set Section on a field that database was not showing, it appears in the list as well as in that section. That is deliberate — it used to look as though nothing had happened.

In the Library there is no Section control at all — a section belongs to a database, and the Library is workspace-wide. Put a field into a section from a database’s own chip, not from the Library.

Fields you cannot fully edit

Some built-in fields are locked in one way or another, and the editor says which.

What you see	Why	What you can still change
The name is plain text beside a lock, with Built-in field — name can’t be changed	It is one of the three display-only built-ins: AI Summary, History Log and Owner	Its section and, where offered, its column visibility
A type pill and Built-in field — type cannot be changed, with no picker	The field is a core attribute of a contact	Its name, its section, its column visibility
A lock and Built-in field — originally “Date Added”	Someone renamed a built-in, and the screen keeps showing you the original name	Nothing to fix — this is a reminder, not an error
Name’s Section control replaced by a Pinned pill and Built-in field — always pinned	Name is the record’s identity column	Its label
Allow multiple selection greyed out on Status or Source	Those two are core attributes and hold exactly one value	Their other dropdown settings
No AI Auto-Fill switch under Automations	The field is written by the system rather than by a person	Nothing there to set

Most built-ins can be renamed: Status, Priority, Name, Phone, Email, Source, Date Added and the action-date stamp.

Remove from one database, or delete everywhere

These are two different things and the menu keeps them apart. Click Remove at the bottom left of the editor.

Read the sublabels. The top row is reversible; the bottom one is not

Remove from Leads — sublabel Keeps the field + its data. The field leaves this database’s list. It stays in the Library, every other database that holds it keeps it, and no data is touched. The label carries the name of whichever database you are in.
Delete permanently — sublabel Erases all its data everywhere.

Three variations to expect:

In the Library only Delete permanently is offered, because there is no single database to remove the field from.
A built-in field that cannot be deleted shows only Remove from Leads — and in the Library, no control at all.
Name can never be removed from a database.

Delete permanently erases the data, not just the field. The confirmation is titled Delete “Budget” permanently? and reads: This removes the field from every view and permanently erases all data stored in it across every record. This can’t be undone. Every value every contact has ever held in that field goes with it. If you only want the field off one database, use Remove from Leads.

The two places a field lives

The Library chip at the far left of the switcher row is the whole workspace’s field registry, as one flat list. The screen describes it as: Every field in the workspace — one shared definition. Click a field to edit or delete it. Add or remove a field from a specific view inside that view.

Each row shows the field’s name, a type pill, and chips naming the databases that currently show it. Extra databases collapse into a +N chip you can hover to read the rest. A field that no database shows reads Not in any view in italics. A dashed New field button sits at the bottom of the list.

Not in any view means the field exists and holds data, but no database displays it

A database’s chip shows the other view of the same fields: only the ones that database holds, in the order its table uses them.

If something goes wrong

What happens	Why	What to do
There is no Add field or section button	You do not have the Table Settings permission, and the button is hidden rather than disabled	Ask a Workspace Owner for it in Settings → Roles
A field you added on one database is missing from another	Membership is per database; only the definition is shared	Open the other database’s chip and add it there with Add field or section
Renaming a field changed it on every database	There is one definition of each field in the workspace	Expected. If you needed a different label in one place, create a second field
The field’s name will not edit	It is one of the three display-only built-ins — the editor says Built-in field — name can’t be changed	Nothing to do. Most other built-ins can be renamed
Database config saved, but the new field is not a column	It was created in a section with its eye off	Turn its eye on — see Choose and pin your table columns
A half-made field has no way out	While a field is being created the Remove control is not rendered	Press Cancel in the editor footer
A toast reads Couldn’t create the field. Check your connection and retry.	The create request did not reach the server	Check your connection and press Create field again
A toast reads Field created. Syncing…	The field was created but the server did not echo its identity back in time	Nothing — the draft is dropped and the real field loads in
You pressed Discard and the field is still there	Create field had already written it	Open it and use Delete permanently