Choose and pin your table columns
Being in a database and being a column in its table are two different things — which is why a field you just added can be missing from the table but present on the record card. This page sorts out which is which, and how to freeze the columns you always want in front of you. About 10 minutes.
Before you start
- You can open Database Configuration and click a database’s chip
- You have the Views permission. Without it the eye buttons are replaced by blank space and rows will not drag — there is nothing to hover and nothing to click
- The field is already in this database. If it is not, add it first with Add, edit and remove a field
The three states a field can be in
Per database — the same field can be in a different state in each one.
| State | Where it shows | How you set it |
|---|---|---|
| Pinned | Frozen at the left of the table, in the record card’s always-visible strip, and on the identity block of the mobile card | In the Pinned in Leads group |
| Shown | A normal scrolling column, and in its section on the record card | In a section group, with its eye on |
| Shown but not a column | On the record card only, in its section | In a section group, with its eye off |
| Not in the database | Nowhere | It is not in the list at all |
Steps
Open the database’s field list
Open Database Configuration and click that database’s chip along the top. Every field the database holds is listed: the Pinned in Leads group first, then a group for each section.
Turn a column on or off
Every field row carries an eye button at its right. An open eye in a filled coloured chip means the field is a column. A struck-through, flat and muted eye means it is not.
Hover it and the tooltip tells you which way it will go:
- Shown in the Leads table — click to hide it (stays in the card)
- Hidden from the Leads table — click to show it
The same eye sits in the top right of the field’s own editor, so you can flip it from either place.
Hiding a column never hides the field from the record card — the tooltip says so on purpose
Freeze the ones you always want in front of you
Drag a field into the Pinned in Leads group, or open its editor and set Section to Pinned. The group is fixed at the top of the list and carries a lock, the database’s name, and a count that reads out of three.
An empty Pinned group shows a dashed drop zone reading Drag a field here to pin it.
Name counts toward the three. A database showing Name, Phone and Status is already full
Pinning here and freezing a column in the table are one and the same thing. Freeze a column from its header menu and it shows up in this group; pin it here and it freezes in the table.
Put the columns in the order you want
Order in this list is the column order. Drag rows to change it. Pinned fields come first, then each section’s fields in section order — so moving a section moves a run of columns with it.
Save
Click Save changes. A toast reads Database config saved, and the table behind the screen redraws.
Three is the limit, and Name counts
Pinned takes three fields, and Name is one of them — so a database showing Name, Phone and Status already reads 3/3. The counter is not styled as an error when it is full, so read the number rather than looking for red.
At the cap, three things change:
- Pinned disappears from the Add to… dropdown in the add-field popup.
- A field editor’s Section dropdown shows Pinned (max) and refuses the pick.
- Dragging a fourth field over the group refuses the drop. The count turns red, the group dims, your cursor says no, and an advisory appears underneath: Pinned is capped at 3 — unpin one to add another.
All four refusal signs at once — red count, dimmed group, no-drop cursor, advisory line. Nothing is broken: drag one of the three out first, then bring the new field in
A pinned column that is not frozen
The table freezes at most three columns, and fewer when the window is too narrow to leave a usable scrolling area. A pinned field that does not fit still appears — it just scrolls with the rest, in its natural position.
Open that column’s header menu and it says so inline, with a not frozen here note: Pinned in this view, but the window is too narrow to freeze it here — it scrolls with the other columns and re-freezes when there’s room. Widen the window and it re-freezes on its own.
The other way in: a column’s header menu
You do not have to open Database Configuration to change one column. Click a column header’s chevron in the table.
Pin column and Hide column write the same settings as the eye and the Pinned group
| Row | What it does |
|---|---|
| Pin column or Unpin column | Freezes or unfreezes the column, exactly as the Pinned group does |
| Hide column | Takes it out of the table, leaving it on the record card |
| Edit field… | Opens Database Configuration with that field’s editor already open |
| Add column… | Opens Database Configuration on a blank new field in the Other section |
On the Name column the pin row reads Pinned and is disabled (Name is always pinned — the record’s identity column), and Hide column is disabled too (Name is always shown — the record’s identity column).
If the table has no room to freeze another column, Pin column is disabled with Can’t pin more — the scrollable area would get too narrow. Unpin a column first.
Pin column and Hide column need the Views permission; Edit field… and Add column… need Table Settings. Each row is hidden, not greyed out, without its permission.
If something goes wrong
| What happens | Why | What to do |
|---|---|---|
| Database config saved, but the table looks unchanged | The field is in a section with its eye off, so it is on the record card only | Turn its eye on |
| The eye buttons are gone and there is blank space where they were | You do not have the Views permission, so the click that could only fail was removed | Ask a Workspace Owner for Views in Settings → Roles |
| A field row shows a lock instead of an eye | It is Name — Always shown as a column — the record’s identity | Nothing to do. Name is always a column and always pinned |
| Cannot pin a fourth field. The counter goes red and the drop bounces | Pinned is capped at three, and Name counts toward it | Drag one of the three out of Pinned first |
| The Section dropdown shows Pinned (max) and will not take the pick | Same cap, from the other control | Unpin something, then try again |
| A pinned column is not frozen at the left of the table | The window is too narrow to freeze that many, so the table demoted it to an ordinary scrolling column | Widen the window — it re-freezes on its own. The header menu says not frozen here |
| Pin column in the header menu is greyed out | The scrollable area would get too narrow | Unpin a column first |
| Rows will not drag, but the field editor works | You have Table Settings but not Views. Reordering, hiding and pinning are written by the other permission | Ask for Views |
| A column is in the wrong place and dragging it in the list does not seem to help | Pinned fields always come first, then each section in section order | Move the field between sections, or reorder the sections — see Group fields into sections |
Next
- Group fields into sectionsA section is a group of fields on a contact's record card — the block headed
- Set up the row action buttonsRow actions are the buttons welded to the right-hand edge of every row — WhatsApp,
- Add, edit and remove a fieldA field is one piece of information on a contact — a budget, a car model, an