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

# View settings

> Ordering, resolve behaviour, deduplication and columns

**Settings**, next to *Filter*, holds everything about a view that isn't a filter.
Changes save as you make them and apply for everyone.

<Frame>
  <img className="block" src="https://mintcdn.com/moderationapi/MRTaiJ_EUWf575WK/images/view-settings.png?fit=max&auto=format&n=MRTaiJ_EUWf575WK&q=85&s=5a9f0d2f48781653ca0453d8e2b6a770" alt="View settings with ordering, resolve behaviour, deduplication and columns" width="1400" height="1000" data-path="images/view-settings.png" />
</Frame>

## Ordering

| Option               | Use it when                                                |
| -------------------- | ---------------------------------------------------------- |
| **Oldest first**     | The default. Nothing waits forever.                        |
| **Newest first**     | Recency matters more than backlog — live chat, launches.   |
| **Highest severity** | Worst first, when you can't get through everything.        |
| **Random**           | Sampling rather than clearing, e.g. spot-checking quality. |

## Items leave this view when

This is the difference between a shared window and a separate workload.

* **Resolved anywhere** — resolving the item in any view clears it here too. Right for
  views that slice the same work, like a [language view](/review/recipes/language-views).
* **Resolved here only** — the view keeps its own list. An item resolved elsewhere
  still waits here. Right for a second pair of eyes: escalations, appeals, QA.

The inbox is always *resolved anywhere*.

## Deduplication

Repetitive content collapses into one row with a count, so a spam wave is one decision
instead of two hundred.

| Option               | Groups                                                                                                                                                                               |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **By content ID**    | Resubmissions of the same `contentId` — an edited post, a re-checked profile. The newest version's state wins, so content edited after a resolve comes back for review. The default. |
| **Exact duplicates** | Identical content, whoever posted it. Resolving one instance resolves the group.                                                                                                     |
| **Similar content**  | Near-identical wording — reworded spam, small variations. Resolving one instance resolves the group.                                                                                 |
| **Off**              | Nothing. Every submission is its own row.                                                                                                                                            |

## Columns

Each view chooses its own columns. The built-in ones are **Content**, **Channel**,
**Author**, **Submitted**, **Flagged labels**, **Severity** and **Status**, all on by
default.

Under **From your data**, metadata keys found on your recent items are offered too, so
you can put your own order number, room name or plan tier right in the list. Values that
look like a URL render as links back into your system.

Because columns belong to the view, a fraud team's view can lead with author and
metadata while a content team's view stays focused on the content itself.

## Details and deletion

**Edit details** changes the view's name, icon and description. **Delete view** removes
the saved definition only — no content is ever deleted, and everything it showed is
still in the inbox.

The inbox can't be renamed, refiltered or deleted, and only its ordering, deduplication
and columns can be changed.
