> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clustr-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account States

> Tags, tier, owner, and dismiss — one control each

Every account carries four independent things: its [tags](/tags), a
[tier](/tiers), 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.

| Question                                                          | Control        |
| ----------------------------------------------------------------- | -------------- |
| Where is the conversation, and what else is true of this account? | [Tags](/tags)  |
| How good a fit is it, in your own words?                          | [Tier](/tiers) |
| Whose account is this to work?                                    | Owner          |
| Stop showing me this                                              | Dismiss        |

## 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](/hubspot#owner-sync),
[Salesforce](/salesforce#owner-sync) or [Attio](/attio#owner-sync). 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](/api-reference/set-account-state) and
[Bulk Set Account State](/api-reference/bulk-set-account-states) over the API.
Tags have their own endpoints, because they are shared by all three record
types: [Set An Account's Tags](/api-reference/set-account-record-tags).

A [Workflow](/workflows) 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](/record-activity) — who did it
and when, whether it was you or a Workflow.