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

# Warnings

> Record a warning, revoke it or respond when a member reaches a limit.

A warning records a moderation case. It does not change the member's Discord permissions by itself.

```text wrap theme={null}
/warn user:@Alex reason:Please keep trip planning in #weekend-walks.
/warnings user:@Alex
```

pup replies privately to slash commands. With `^` saved as your server's prefix, `^warn @Alex Please keep trip planning in #weekend-walks.` records the same warning and replies in the channel. Reasons are optional; an omitted reason becomes **No reason provided**.

Open **Moderation → Cases** to check the warning and its notifications. Retry a failed notification from its case instead of warning the member again. See [Cases](https://docs.pup.run/cases.md).

## Revoke a warning

```text wrap theme={null}
/warning revoke warning:5
```

Use the warning's **server case number**, shown beside its warning number by `/warnings`. Revoking stops it counting toward escalation and keeps its history. Case administration also offers warning edit, rank and clear controls when the warning's status allows them.

## Warning escalation

Open **Protection overview → Warning escalation**. For example, you can time out a member for ten minutes when they reach three active warnings.

**1. Choose the threshold**

Select **Apply the configured member action** and set **Active-warning threshold** to **3**.

**2. Choose the response**

Select **Timeout** and a ten-minute duration. You can instead choose another available member
action. pup needs the Discord permission and role position for that action.

**3. Decide which warnings count**

Set warning expiry to seven days if you want older warnings to stop counting. Leave **Further
warnings** off to avoid repeating the response for every warning at or above the threshold.

**4. Save**

Save the form. Changing these settings never replays old warnings. Check the case after a new
warning triggers the threshold.

![Warning escalation set to a ten-minute timeout in the Juniper Club dashboard.](https://mintcdn.com/pup-15c61ad9/7A8_OyKz3be9aqRt/images/guides/warning-escalation-light.png?fit=max\&auto=format\&n=7A8_OyKz3be9aqRt\&q=85\&s=895d77f3a9672d8a81c53845d65034a2)

Revoked and expired warnings do not count. With **Further warnings** off, pup responds when the limit is reached and no still-active warning has already triggered escalation. With **Further warnings** on, another warning at or above the limit can start a new temporary restriction after an earlier one ends.

## Rule warning shortcuts

In **Moderation → Settings**, save a shortcut such as `rule7`, its title, a rule-message link from this server, one to ten destination channels and a warning reason. Select **Enable this warning shortcut** when it should be available.

With `^` as the saved prefix, reply to a member's message with `^rule7`, or use `^rule7 @Alex`. Mention exactly one member; a bare ID is not accepted. The warning uses the saved reason and counts toward escalation. Its case keeps the rule details used at that moment.

The optional **Public message** controls the reminder. Insert **@Member**, **Rule link** and **#Channels** with the formatting controls. An empty message uses “@member, please check Rule title.” with the rule link. It never exposes the private warning reason.

pup deletes the command and posts one reminder. It needs **Manage Messages**, access to the rule and channels the member can view. If the reminder fails, check the warning’s case before trying again. Disabling a shortcut also stops its pending reminders.

## Who can warn

The moderator needs pup's warning access and Discord's **Moderate Members** permission. [Permissions and hierarchy](https://docs.pup.run/permissions.md) explains target and owner checks. Recording a warning does not require pup to be above the member; an escalation action does.

Configure Warn's shared slash/prefix policy in **Staff access → Command restrictions**. Turning it off or excluding a member or role affects both forms. Turning moderation off stops all moderation commands.

**Warning-bot integration** is separate: authorized bots can use only the supported prefix form, with replies in the configured channel. pup checks that channel when saving.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.