# Role corrections

> Source: https://docs.trailspark.ai/docs/role-corrections

When the automatic role assignment is wrong — the system missed someone, or matched the wrong person — you can correct it directly from that person's record. Editors and admins can add a role that wasn't assigned, or reject a role that shouldn't be there. Corrections persist through re-evaluations.

## Who can correct roles

The add and reject controls are visible only to **editors** and **admins**. If you have viewer access, you can see the Buying Group Roles section but the controls are hidden.

## Where to make a correction

Open the person's record — a lead or a CRM-only contact. The **Buying Group Roles** section shows every role the person currently holds, organized by ICP. Each section is headed by the ICP's name, with an **+ Add role** button at the top and a **Reject** link on each role card.

## Adding a role

Use **+ Add role** when someone should be in a role but wasn't assigned to it automatically. This is common for:

- Stakeholders who engage primarily through offline or untracked channels (phone, email outside your tracked domain, in-person meetings)
- People whose titles don't match any configured keyword but whose actual responsibilities fit the role
- Late-identified stakeholders who joined the buying process after the last evaluation

**How to add a role:**

1. On the person's record, find the section for that ICP.
2. Click **+ Add role**.
3. A dialog opens with a dropdown listing the roles defined for that ICP that the person does not already hold. Pick the role from the dropdown.
4. Click **Add as correction**.

The role is added immediately and the person's coverage at the account level is recomputed. The role card shows a **Corrected** badge where the Behavioral / Demographic / Mixed basis would normally appear, and the right-hand label reads **Set by user** instead of a confidence percentage.

The add dialog only shows roles the person doesn't already hold — you can't create a duplicate assignment.

## Rejecting a role

Use **Reject** when the system assigned a role that doesn't reflect reality — the person changed jobs, the title match was coincidental, or the signal activity was noise.

**How to reject a role:**

1. On the person's record, find the role card you want to remove.
2. Click **Reject** at the bottom right of the card.

The role is removed immediately and coverage is recomputed. The rejection is recorded so the system skips this assignment on future re-evaluations — if the person would otherwise qualify for the role again based on updated signals or a profile change, the rejection holds and the role is not reinstated automatically.

Rejecting and adding are mutually exclusive per role: if you reject a role you previously added manually, the add is retracted and the person loses the role. If you add a role you previously rejected, the rejection is cleared and the correction takes effect.

## How corrections are badged

When a role was set by a team member, the role card reflects that.

| What you see | What it means |
|---|---|
| **Corrected** badge | This role was added manually by a team member |
| **Set by user** (right-hand label) | Replaces the confidence percentage for corrected roles |
| No basis chip | The Behavioral / Demographic / Mixed chip is hidden for corrected roles — it doesn't apply |

A role assigned by evaluation (not corrected) shows its basis chip — **Behavioral**, **Demographic**, or **Mixed** — and a confidence percentage. See [Role attribution](/docs/role-attribution) for what those mean.

The **Primary** badge works the same way whether a role was assigned automatically or added manually. Primary is determined by the ICP's tiebreak order across all roles the person holds.

## How corrections hold through re-evaluation

Corrections are durable. They are not overwritten the next time the account is evaluated.

- **An added role** is kept as an authoritative override. The system treats it as final and does not remove it when it runs the automatic matching logic again.
- **A rejected role** is suppressed. Even if the person would qualify for the role based on new signals or updated profile data, the rejection blocks the assignment.

This means a correction you make today is still in effect after the next nightly evaluation, after a manual coverage refresh, and after the ICP's signal thresholds are adjusted.

## What corrections affect

Adding or rejecting a role recomputes the account's coverage immediately — the percentage-of-required-roles figures and the role states (Engaged / Identified / Missing) on the [account coverage card](/docs/account-coverage) update to reflect the correction. If the person is the only one filling a required role and you reject them from it, that role moves back to Missing. If you add someone to a role that was Missing, it fills.

## Next steps

- [Buying groups overview](/docs/buying-groups-overview) — how roles, coverage, and the buying-group model work end to end
- [Role attribution](/docs/role-attribution) — how the automatic matching works and what the Behavioral / Demographic / Mixed basis means
- [Account coverage](/docs/account-coverage) — the coverage picture that role assignments produce at the account level
- [Defining roles](/docs/defining-roles) — adjust the title keywords and targeting criteria to reduce the need for corrections
- [Signal and role attribution](/docs/signal-role-attribution) — configure which signal events carry points toward which roles
- [Lead detail](/docs/lead-detail) — the full person record where the Buying Group Roles section lives