Skip to Content

Views and Columns

The left side of the table toolbar controls what you see, not what the table stores. Hiding a column or switching a view never deletes data and never stops an action from running.


The three controls

ControlWhat it showsWhat it does
Default viewThe view you are currently inSwitch to another view of the same table
2 / 2 columnsVisible columns / total columnsOpen the column list and toggle columns on or off
6 rowsRows in the current viewReflects your active filter and search

Hiding columns

Wide tables get unreadable fast — a sourcing table can carry 20+ enrichment columns.

  1. Click x / y columns in the toolbar
  2. Untick any column you are not working on
  3. The count updates to show how many are still visible

Hidden columns keep their data and keep running. Unhide them any time from the same list.


Switching views

  1. Click Default view
  2. Pick the view you want

A view remembers a layout — which columns are visible, and the sort, filter, and search applied on top of them. Everyone opening the table lands on Default view unless they switch.

Useful splits:

  • Sourcing view — input columns only, for checking what came in
  • Enrichment view — email and phone columns, for spotting gaps
  • Export view — only the columns your CRM or sequencer needs

Reading the row count

The row count is the number of rows in the current view, not in the table. If it drops after you set a filter, that is the filter working — the rows are still there.

To check the true total, clear your filter and search.


Common use cases

  • Hide enrichment columns while you check what actually came in from a source
  • Build an export view holding only the fields your CRM or sequencer needs
  • Give each stage of the workflow its own view — sourcing, enrichment, QA, export
  • Check coverage fast by showing only the columns that are meant to be filled

Best practices

  • Name a view after the job it does, not after who made it
  • Remember hidden columns still run and still cost credits — hiding is display only
  • Keep the input key column visible in every view; it is how you identify a row
  • Read the row count as “rows in this view” — clear filter and search before treating it as a total
  • Switch back to Default view before comparing counts with a teammate

Where to next

  • Filter — narrow rows down to a working set
  • Sort — order them
  • Table — columns, rows, and dynamic variables