Skip to main content
Every account carries four independent things: its tags, a tier, an owner, and whether it’s dismissed. Each answers a different question, and none of them hides a row as a side effect of answering a different one.

​
Tags describe, dismiss hides

A tag is any label: Contacted, Meeting booked, Common investor, Renewal Q3. What used to be a status is one of them — a tag in a single-choice group, usually still called Status. A tag never removes a row from a table. A tag marked “closes” sorts its row to the bottom and draws with a neutral pill, but the row stays visible and filterable. Dismiss is the one control that removes a row from view. Dismiss an account and it — and every path there, current and future — moves to the Dismissed view. Restore brings it back. The write reports intros_moved, so you can say how many warm intros went with it rather than estimating. Keeping these separate means tagging an account never surprises you by making it disappear, and dismissing an account never gets confused with an outcome you’re tracking in the pipeline.

​
Owner

An owner is whoever is accountable for the account. It’s a plain assignment, filterable and sortable, independent of tags or tier. Where a CRM is connected, the owner can sync with a CRM owner field your workspace picks — see HubSpot, Salesforce or Attio. Writing the owner into the CRM is always a deliberate act: send push_to_crm with the write, and the response’s crmPush says what happened there. The owner is saved in Clustr either way.

​
Setting state on one account or many

Tier, owner and dismiss are set from the account row, the account page, or across a whole selection with the bulk action bar — Set Account State and Bulk Set Account State over the API. Tags have their own endpoints, because they are shared by all three record types: Set An Account’s Tags. A Workflow can set any of them automatically when a record enters or leaves a view.

​
Every write is traced

Setting tags, a tier, or an owner, or dismissing or restoring an account, logs an entry on the account’s activity timeline — who did it and when, whether it was you or a Workflow.