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

# Bans

> Record detailed, feature-scoped ban information for your players.

export const Scope = ({children}) => <Info>
    <b>Scope:</b> {children}
  </Info>;

Flock bans are **informational**. A ban derives from your **feature configuration** and is applied
on a **per-feature** basis: Flock gives you the tools to record rich ban details and expose a
player's ban status, but **what to do about a ban is up to your game** — we don't block anything for
you.

<Scope>bans derive from **feature config** and are applied per **feature**.</Scope>

<Tabs>
  <Tab title="Dashboard">
    Bans are driven by your **feature configuration** (Configurations → Features). Create and manage
    detailed ban records on the **Manage Bans** page, scoped to the relevant feature.

    <Frame caption="Create detailed ban records in the dashboard.">
      <img src="https://mintcdn.com/qwacks/TGGmq_oWzDacAqHl/images/guides/bans.png?fit=max&auto=format&n=TGGmq_oWzDacAqHl&q=85&s=cd9a010ccfa21645179da909c30abb11" alt="Manage bans" width="1440" height="866" data-path="images/guides/bans.png" />
    </Frame>
  </Tab>

  <Tab title="SDK">
    Read a player's ban status and the detailed ban information through the SDK, then **decide what
    to do in your game** — restrict a feature, show a message, or anything else. Flock surfaces the
    status; the enforcement is yours.
  </Tab>
</Tabs>

<Note>
  Bans are purely informational — Flock provides the data, your game decides the action. Acting on a
  player's ban status is implemented by you, within the game.
</Note>