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

# Inbox

> The to-do list of gaps in your Context Layer, ranked by what matters most.

The **Inbox** collects everything ClarityQ has noticed is missing or unverified in your Context Layer, so improving it becomes a queue to work through rather than a guessing game. Gaps come from real questions your team asked, which means the list reflects what people actually need.

Find it under **Inbox** in the sidebar. It's for the people who maintain the Context Layer — **Analyst Contributors** and **Admins**.

Analysts without catalog-editing rights don't see the Inbox. Dashboards and answers sent to them for checking stay on their own **Requests for Review** page.

## What's in the List

Each row is one gap:

| Column | What it tells you |
| - | - |
| **Item** | The component involved. Items that don't exist yet are shown in italics |
| **Action Required** | What needs doing: **Add to context**, **Needs approval**, **Needs update**, or **Review suggestion** |
| **Description** | Why it's here, in a sentence |
| **Occurrences** | How many times it came up. A chat icon means people explicitly reported it |
| **Last Reported** | When it last came up |

You can search the list, filter by action required, and narrow it to a time window.

Items that are resolved or dismissed drop off — the Inbox only shows what still needs a person.

## How the List Is Ordered

The most worthwhile work sits at the top. Ranking combines four things:

* **How often** the gap came up
* **How uncertain** it is — something entirely missing outranks something merely unapproved
* **How important** the component type is — a product memory or entity outweighs a single dimension
* **Whether people reported it** — each person who reports it pushes it higher

So a missing metric that five people hit beats an unapproved dimension that surfaced once.

## Working Through It

* **Review** — opens an item that needs approval, where you can **Edit**, **Approve**, or **Exclude** it.
* **Go to Builder** — opens the Builder with the change already described, for items you need to add or update.
* **Fix manually** — for [features](/context-layer/semantic-catalog/features) and their dimensions, which aren't built in the Builder. This takes you to the right page instead.
* **Dismiss** — removes the item from the list.

Opening an item shows who was affected and who reported it, with a link into the chats where it came up, so you can see the question behind the gap before you decide what to do.

Items marked **Review suggestion** work slightly differently: they're fixes someone proposed during a chat, either from a [diagnosis](/ask-anything/diagnosing-answers) or in the Builder. Opening one shows what the agent suggested and the Builder prompt it would send, so you can apply it or dismiss it.

<Note>
  Dismissing isn't final. If the same gap shows up again in a later conversation, the item returns to the Inbox — a dismissal says "not now", not "never".
</Note>

## Items That Close Themselves

You don't have to come back and tick things off. An item disappears on its own when the underlying gap is closed — when you approve the component, deploy a draft that approves it, or create it from the Event Catalog.

## Table Changes

Some items aren't driven by questions at all. When columns change in a table behind one of your entities, ClarityQ raises an item so you can update the entity to match. These show no occurrence count, since nobody had to ask about them for the problem to be real.

## Related

* [Context Coverage](/ask-anything/context-coverage) — where these gaps are first surfaced, inside the chat
* [How the Builder Works](/context-layer/building/how-the-context-layer-builder-works) — where most fixes get made


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.