Get started
Permissions and hierarchy
Understand why an action is allowed or denied.
An action must pass Pup access checks and the relevant Discord checks. A Pup
permission does not override Discord’s native permissions, role hierarchy,
channel visibility, or a missing bot permission.
Pup uses permission sets bound to individual users or Discord roles. The server
owner has a recovery path; being a Discord administrator does not automatically
grant every custom Pup capability. Review access in the dashboard.
Moderation operations require access to the moderation module plus the relevant
action capability. The command reference lists the native actor and
bot permissions. Member actions also apply actor/bot/target hierarchy checks.
Protected subjects, disabled interactions, missing resources and stale access
can prevent an action even when a role appears high enough.
When access is denied, check the specific diagnostic before retrying. Refresh
stale state, correct the narrow missing permission or binding, and retry only the
intended operation. Do not repeatedly submit a destructive command to work around
a denial. Configuration changes are revision-checked and successful policy
changes are audited.