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

# Settings

> Badges, leaderboard views, and the wallet blacklist for a point system.

The **Settings** section is a tabbed page for everything that shapes a point system: its general details, its **badges**, its saved **views**, its **blacklist**, and its **team**. This page covers the three that drive rewards — badges, views, and the blacklist.

***

## Badges

Badges are progression markers a wallet earns automatically when it meets a set of conditions. They replace the old flat "levels": a badge **family** is a progression axis (seniority, points volume, activity in a period), and each family holds ordered **tiers** — the evolutions of that badge.

| Concept        | Description                                                                                                                                                       |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Family**     | A progression axis holding ordered tiers (e.g. "Levels", "Seniority")                                                                                             |
| **Tier**       | A step within a family, unlocked when its conditions are met. Order is assigned automatically                                                                     |
| **Conditions** | What a wallet must satisfy: points, level, account age, points in a period, first-activity date, event counts, or leaderboard rank — combined with "all" or "any" |

A tier is awarded the moment a wallet crosses its conditions, and the award is kept (history is preserved). A wallet's **current tier** in a family is the highest one it has earned; the leaderboard shows it next to the wallet.

The **Levels** family is a built-in, system family: it holds your former levels, one tier each (`points >= threshold`). It is what the **Level** condition in an [automation](/app/automations#conditions) and the level filter used by views and campaign cohorts now read, so those keep working unchanged.

***

## Views

A view is a saved, named filter over the leaderboard — a "season" or a segment. The same filter dimensions decide who appears on a public leaderboard tab and who a campaign targets when it's built from that view.

A view can filter by any combination of:

* **Event types** — only points from specific events count.
* **Time period** — a start and/or end date.
* **Rank range** — e.g. positions 1–100.
* **Points range** — a minimum and/or maximum balance.
* **Levels** — one or more level numbers.

<Note>
  A view must set at least one filter — a view with no filters would just be the overall leaderboard. Names are unique within a point system.
</Note>

Views are referenced by name from an automation's **View rank** condition, and they can be used as the cohort source when creating a [campaign](/app/campaigns#whos-included) — so what you see in a view is exactly who gets rewarded.

***

## Blacklist

The blacklist bans a wallet from a point system. A banned wallet:

* is **rejected** by the [trigger API](/api-reference/triggers) — calls that would award it points return `403`;
* is **excluded** from every leaderboard and from all campaign cohorts, however they're built.

Each entry stores the address and a required **reason**. Addresses can be entered as `0x` or as an ENS name; a wallet already banned under either form is detected as a duplicate. Removing a wallet from the blacklist restores it immediately — but past point events it accrued before being banned are retained.

Managing levels, views, and the blacklist is available to **owners, admins, and moderators**.