A preset is a moderation policy. It contains a name, a description, a default level, an optional failure policy, and up to 25 categories. Each category has a description, optional allow and block examples, a severity from 1 to 10, and two thresholds.

<Figure src="/docs-media/presets.webp" alt="Presets page with eight cards in a bordered scroll frame. System and team presets show their category tags, active version, and publish date, with the gallery controls above the grid." caption="Centered gutters and a visible scroll frame. System cards are read-only starter templates; team cards belong to the active workspace. Shown with synthetic QA data." />

## System presets and team presets [#system-presets-and-team-presets]

- **System preset.** A read-only starter template seeded into the deployment. Open it to review its rules, then **Fork** it to make an editable team preset. System presets are never edited in place.
- **Team preset.** A preset owned by the active workspace. Owners and admins can edit, test, publish, fork, and roll back.

A system preset with no published version means the deployment has not run the system preset seed. It cannot be used or forked until the operator seeds it.

## Categories and thresholds [#categories-and-thresholds]

Scores run from 0 to 1. For each category:

- **Allow** when the score is below the flag threshold.
- **Flag** when the score reaches the flag threshold but stays below the block threshold.
- **Block** when the score reaches the block threshold.

The final verdict is conservative: any blocked category makes the decision `block`; otherwise any flagged category makes it `flag`; otherwise the decision is `allow`.

Severity does not change those bands. It contributes to escalation and tie-breaking. Severity 8 and above is high severity.

<Callout type="info" title="Levels shift the band">
`light` raises both thresholds by up to 0.10, `standard` leaves them unchanged, and `heavy` lowers
them by up to 0.10. The shifted thresholds are clamped into a valid band. The editor shows one
threshold table, not one per level.
</Callout>

## Versions and publishing [#versions-and-publishing]

A published version is immutable. Your edits stay in the browser tab until you publish. Publishing creates the next version and points the preset at it.

- The editor never saves an unpublished draft on the server.
- Creating a preset, forking a preset, and publishing a new version each need a completed test of the exact policy at its default level. The test must run a real decision, not a degraded fallback.
- **History** shows published versions. Opening a version loads it into the draft; it does not change the active version. Rollback moves the active pointer to an existing version.
- New requests that reference the preset by `preset_id` use the active version.

<Callout type="tip" title="Fork before you experiment">
Forking a system preset is the safe way to learn the editor. The fork can be tested and published
without touching a template other workspaces may rely on.
</Callout>

## Next [#next]

- [Import from GitHub](/docs/repository) for loading one policy file pinned to a commit.
- [Preset editor](/docs/preset-editor) covers editing, testing, and publishing in detail.
- [Playground](/docs/playground) runs one message against a published preset.