Tier mapping

Tier mapping lets Plain automatically assign tenants to tiers based on the value of a tenant field. Rather than assigning tiers manually, you define which field drives tier assignment and Plain keeps every tenant's tier in sync as their field value changes.

How it works

When you map a tenant field to tiers, Plain creates a tier for each option in that field. Every tenant is then assigned the tier that matches their current field value. If a tenant has no value for that field, they receive no tier assignment.

Machine tiers behave like any other tier: they can have SLA rules, a default thread priority, and can be used to filter your queue.

Prerequisites

Only single-select (dropdown) tenant fields are eligible for tier mapping. Free-form text, number, boolean, and multi-select fields are not supported, because Plain needs a fixed, bounded set of values to create tiers from.

Setting it up

1. Go to Settings → Tenant fields

2. Find the Tier mapping card

3. Select the field you want to map from the dropdown – only eligible fields appear

4. Click Save

Only one field can be mapped to tiers at a time.

What happens when you save

• Plain creates a new tier per option in the field, named after each option value

• All existing tenants with that field set are automatically assigned to their matching tier

• Tenants added or updated after setup are assigned in real time as their field value changes
  

Keeping tiers in sync

Plain automatically keeps machine tiers in sync when the field schema changes:

• New option added – a new machine tier is created; any tenants with that value are assigned to it

• Option removed – the corresponding machine tier is deleted and affected tenants lose that tier assignment

• Mapping removed or changed – all machine tiers from the previous mapping are deleted and tenants are unassigned.

Changing the mapped field first removes the old mapping (including its tiers), then sets up the new one.