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

# Language views

> Route content to moderators who can read it

## The problem

A moderator who doesn't read Portuguese can't judge Portuguese. They'll skip it, guess
at it, or lean on a translation for a decision that turns on tone. Meanwhile the
Portuguese speaker on your team is scrolling past German to find their own work.

## The view

One view per language your team covers:

* Filter **Language → German**.
* Name it for the language, spelled out — *German* reads better in a sidebar than *de*.
* When you [invite moderators](/review/inviting-moderators), give each person access
  only to the languages they read.

Language is detected automatically, so nothing extra is needed at submission time.

## Handling the long tail

You won't have a view for every language. Two options:

* Leave the rest to the inbox, which every item awaiting review reaches, and let a lead
  sweep it.
* Or build one view for the languages you *don't* staff by selecting them together, and
  work it with [translation](/review/translation) turned on.

<Tip>
  Watch for a language view that never empties — that's usually a staffing signal, not
  a filtering one.
</Tip>