# Map a plugin's roles

> Decide which tier, or which models, each plugin's jobs run on.

A role is one job a plugin needs a model for, named like `clusters.extract` or `chat.ask`. The plugin registers its roles with a default tier. You can move a role to another tier or give it models of its own, and the plugin's code never changes.

## See every role

Open **Settings → Model Hub → Roles**.

- **Note chat** lists Model Hub's own two roles: `chat.ask` (Balanced) and `chat.research` (Research).
- **Other plugins** lists each plugin's roles and the tier each runs on, or *Its own models*.

Other plugins' roles are changed in each plugin's own settings, which open the same editor.

## Change a role

1. Open the role editor: the sliders button beside a Note chat role, or the models button in the other plugin's settings. The dialog is titled *Models for* and the plugin's name.
2. Each role shows what it uses now, for example *Now: openrouter · Claude Sonnet 5.5* with its price, and how many models it can fall back on.
3. Choose a **Tier** from the dropdown. Or select **New tier…** to make one for this job.
4. To skip tiers for this role, turn on **Use its own models** and build its list. They are tried in order, as in a tier.
5. To undo your changes, select **Back to the plugin's default**.

Limits stack: a call must fit the role's limits and the tier's.

## When a role names a tier that doesn't exist

If a role asks for a tier that was deleted or not made yet, it runs on **Balanced** and the Roles tab says so: *Asks for "…", which doesn't exist, so it runs on Balanced.* Pick a tier for it, or make the missing one with **New tier…**.

## Related

- [Set up tiers and limits](tiers-and-limits.md)