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

# Decline reasons and tags

> The two vocabularies analysts pick from, and how the API uses them.

export const Shot = ({id, alt, caption}) => <Frame caption={caption}>
    <img className="block dark:hidden rounded-lg" src={`/images/guides/${id}.light.png`} alt={alt} loading="lazy" decoding="async" />
    <img className="hidden dark:block rounded-lg" src={`/images/guides/${id}.dark.png`} alt={alt} loading="lazy" decoding="async" />
  </Frame>;

Both tabs need `risk:write` to edit; the `senior-analyst` template has it.

## Decline reasons

**Settings → Decline Reasons** holds the reasons analysts choose when declining; a reason (or a note) is mandatory to decline. Type a reason, press `Enter` or **Add**, remove with the bin, and click **Save changes**. Duplicates are rejected.

<Shot id="admin/reasons-01-list" alt="Decline Reasons" caption="Reasons analysts pick from." />

<Shot id="admin/reasons-02-duplicate-toast" alt="Duplicate reason toast" caption="Duplicates are refused." />

Reasons are plain text without codes or categories; keep them short and current.

## Tags

**Settings → Tags** holds the managed tags. Each has a label, one of seven colours (chosen when created) and an enabled switch. Disabled tags stay on cases that already carry them but are no longer offered.

<Shot id="admin/tags-01-list" alt="Tags" caption="Label, colour, enabled." />

<Shot id="admin/tags-02-color-picker" alt="Colour palette" caption="Seven fixed colours." />

## Where they appear

Tags show as chips on Decision Queue rows, on Cases and on the Tags line of the console. Decline reasons appear in the decision rail, in the queue's Decision History and in the case timeline.

## Tags and the API

Your systems can tag cases through the API, but only with enabled tags from this list; anything else is rejected.