> ## 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.

# Tiers

> Your own words for how good a fit an account is

A tier is your workspace's own ranking of accounts — "A / B / C," "Strategic /
Growth / Watch," whatever your team already calls it. Clustr doesn't invent
the vocabulary; you define the tiers and file accounts under them.

## Rank, not color

A tier's only meaning is its position: position 0 is the highest tier, and
everything else ranks below it in the order you set. There's no separate
color to pick — the UI shades a tier by where it sits on that ranking, so
reordering tiers is the whole styling exercise.

## Setting a tier

Set a tier from the account row, the account page, the bulk action bar, or
automatically with a [Workflow](/workflows). Clearing a tier is the same control with
an empty value.

## Tiers feed fit

Tier is one of the inputs to an account's [fit grade](/api-reference/list-accounts#the-grade).
An account on your top tier scores higher for it; deleting a tier clears it
off every account that carried it and those accounts are regraded.

## Managing your tier list

From Settings, create, rename, reorder, or delete tiers. Deleting a tier
doesn't touch the accounts themselves — it clears the reference and reports
how many accounts were affected. Reordering re-ranks every tiered account at
once.

Over the API: [List](/api-reference/list-tiers),
[Create](/api-reference/create-tier), [Get](/api-reference/get-tier),
[Update](/api-reference/update-tier) and [Delete](/api-reference/delete-tier).

## Sending a tier to your CRM

A tier is a Clustr rank, not a [tag](/tags), and it stays one. It can
optionally be mapped to **one** single-select field in your CRM, with each of
your tiers matched to one of that field's options.

Set it up under **Settings ▸ Tiers**, below the tier list, or from the Tier
column's gear on the Accounts table. Both open the same editor, and only admins
can save it. Pick the direction:

| Direction                   | What happens                                                |
| --------------------------- | ----------------------------------------------------------- |
| **Clustr sets the value**   | Your tier is written to the CRM field on each sync          |
| **Your CRM sets the value** | The CRM field is read on each sync and sets the Clustr tier |
| **Paused**                  | Neither                                                     |

There is no "both ways" for tier: one side owns the value.

A tier you leave as "Not in your CRM" is skipped rather than cleared, and so is
an account with no tier. Two tiers cannot share one option, because reading it
back could not tell them apart.

Per provider: [HubSpot](/hubspot#tier-sync), including the built-in
**Ideal customer profile tier** field; [Salesforce](/salesforce#tier-sync);
[Attio](/attio#tier-sync).