Skip to main content

​
Overview

pom provides two methods for silencing members: role-based muting and Discord timeouts. Role-based mutes assign a special role that strips messaging permissions across all channels. Timeouts use Discord’s built-in system, which shows a visual indicator on the member and automatically expires after the set duration.

​
Mute (Role-Based)

Assign a muted role to a member, preventing them from sending messages in any channel. The muted role persists until manually removed — it does not expire automatically.
You need the Manage Roles permission to use mute commands.

​
Unmute

Remove the muted role from a member, restoring their ability to send messages.

​
Mute Role Configuration

By default, pom looks for a role to use as the mute role. You can explicitly set which role is used with ,muterole.
Once set, pom uses this role for all ,mute and ,unmute commands. The role should be configured to deny Send Messages, Add Reactions, Create Public Threads, and Create Private Threads permissions in your channel overrides.
Create a role at the top of your hierarchy called “Muted” and deny Send Messages in every channel category. Then set it with ,muterole @Muted.

​
Timeout (Discord Native)

Apply a Discord timeout to a member. Timed-out members cannot send messages, react, join voice channels, or use the stage. The timeout automatically expires after the specified duration — no manual removal needed.
You need the Moderate Members permission to use timeout commands. The maximum timeout duration allowed by Discord is 28 days.

​
Untimeout

Remove a timeout from a member before it naturally expires.
Aliases: ,uto, ,untime

​
Mute vs. Timeout — When to Use Each

For most situations, timeouts are the better choice — they expire automatically, persist even if the member leaves and rejoins, and provide a clear visual indicator. Use role-based mutes when you need indefinite silencing or more granular per-channel control.