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

# Review queues

> Named, prioritised lists of cases waiting for analysts; flows route to them by name.

export const Clip = ({id, caption}) => <Frame caption={caption}>
    <video controls muted playsInline preload="metadata" className="w-full aspect-video rounded-xl" poster={`/videos/guides/${id}.poster.png`} src={`/videos/guides/${id}.mp4`} />
  </Frame>;

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>;

**Settings → Queues** manages **Review Queues**. Needs `queues:write`.

<Shot id="admin/queues-01-list" alt="Review Queues" caption="standard is the default; escalated receives escalations." />

<Clip id="admin/create-queue-route-review" caption="Create a queue, then pick it on a Review node." />

## What a queue is

A queue is where a Review node parks cases. Analysts see cases from every queue their role may see, merged in the Decision Queue.

## Create a queue

**Create Queue** opens the dialog: **Queue name** (lowercase letters, digits and hyphens, up to 50, fixed after creation), **Description**, **Priority** (higher surfaces first), **Escalation target**, **Visible to roles** and **Default queue**. **Create** saves it.

<Shot id="admin/queues-02-create" alt="Create Queue dialog" caption="Name, priority, escalation target." />

<Shot id="admin/queues-05-name-error" alt="Queue name validation" caption="Lowercase letters, digits and hyphens." />

## Default queue

Cases whose Review node names no queue land in the default. Only one queue is the default; setting another replaces it.

## Escalation target

The queue a case moves to when a flow escalates it; keep **escalated** for that purpose or point to your own.

## Visible to roles

Leave all unchecked to make the queue visible to every role. Tick roles to restrict who can see and work it; admins always see every queue.

<Shot id="admin/queues-03-visible-roles" alt="Visible to roles" caption="Restrict a queue to senior analysts." />

## Edit and delete

The pencil edits everything but the name. **Delete queue** warns that flows routing to it will fail until updated; a queue with pending cases cannot be deleted.

<Shot id="admin/queues-04-delete-confirm" alt="Delete queue dialog" caption="Delete." />

## Use a queue in a Review node

Engineers pick the queue on the Review node; a deleted queue makes the flow fail validation with **review queue "x" ... does not exist**.