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

# Channel views

> Separate surfaces that have different tolerances

## The problem

Support chat and public reviews run through the same project, but they aren't the same
job. A frustrated customer swearing in a support ticket is normal; the same words on a
public review page are not. Reviewed in one undifferentiated list, moderators apply the
stricter standard to both — or the looser one.

## The view

Filter **Channel → Support chat**. Repeat for each surface that deserves its own
attention.

This lines review up with the way content was already handled: a
[channel](/get-started/concepts#channel) has its own policies and its own flagging
thresholds, so a channel view shows you the output of one specific rulebook rather than
a mix of several.

## Pairing it with settings

Channel views are a natural place for per-surface workflow settings:

* Support chat, where recency matters: **Ordering → Newest first**.
* Listings, where a backlog is fine but nothing should rot: leave **Oldest first**.

<Tip>
  If your channels map onto teams, this is also the cleanest way to scope access — give
  each team their channel's view when you
  [invite them](/review/inviting-moderators).
</Tip>