Terminate vague permissions.
Discord gives you one switch for "Manage Roles." Perminator gives you 24. Every add, remove, edit, and ban is its own permission — assignable, auditable, revocable.
One switch is not a permissions system.
Discord's native Manage Roles permission is a single on/off toggle. Grant it, and a moderator can rename any role, reshuffle the entire hierarchy, and rewrite what every other role is allowed to do.
All-or-nothing. One grant unlocks everything below.
Seven independent permissions. Grant only what the job requires.
Five domains. Total control.
Every server action lives in one of five domains. Each domain has its own tab in the dashboard, and its own set of granular permissions.
Roles
Create, edit, reorder, and assign roles as separate, revocable permissions.
Channels
Control creation, deletion, overrides, and reordering independently per channel.
Members
Split kicking, banning, timing out, and renaming into distinct grants.
Permissions
A live matrix of every role against every granular permission, in one view.
Actions
Every allowed and denied action is logged with actor, target, and permission.
A second, stricter layer on top of Discord.
Discord's permission model was designed for communities of a few dozen people. Once a server has a real staff team, a single "Manage Roles" or "Administrator" toggle becomes a liability. Perminator adds a policy layer that sits in front of sensitive actions and checks them against the granular permissions you define.
- 01
Invite the bot
Sign in with Discord and add Perminator to a server you manage. It asks only for the permissions needed to carry out the actions you allow.
- 02
Define granular permissions
Open the permission matrix and decide, role by role, which individual actions are allowed: create, delete, rename, reorder, assign, kick, ban, and more.
- 03
Enforce and audit
Sensitive actions are checked against your rules before they happen. Every allowed and denied attempt lands in the Actions log with actor, target, and time.
Perminator never asks for the Administrator permission it is trying to help you avoid handing out. The bot requests only the Discord permissions it needs to carry out the actions your policy allows, and every decision — allowed or denied — is written to an audit log that shows who attempted what, against whom, and when. Server owners keep the final word: you can inspect the full role-by-permission matrix at any time and change a single cell without touching the rest of the hierarchy.
Free guides for Discord admins.
A permission reference, a staff planner, and long-form guides on how Discord permissions really behave. All of it is public. You do not need an account, and you do not need Perminator, to use it.
Every permission flag, and the mistake attached to it.
When to grant a flag, when to leave it off, and what the toggle does not do. Checked against Discord's current permission list.
Open the referencePlannerWhat each staff job should be allowed to do.
Grant and withhold lists for members, hosts, moderators, admins, and the bots that sit in the same hierarchy.
Open the plannerDiscord roles and permissions explained
How roles, the @everyone base, and permission flags combine to decide what each member can do — and where the model starts to strain.
Read guide12 min readA Discord staff ladder you can copy
A complete role order, permission set, and channel map for a mid-size server, including the powers Discord still refuses to split.
Read guide11 min readWhen a Discord permission does nothing
A symptom-by-symptom diagnostic for kicks that fail, private channels that leak, denies that do not deny, and bots that cannot assign a role.
Read guideFrequently asked
- Does Perminator replace Discord's permission system?
- No. It runs alongside it. Discord's permissions still apply — Perminator's bot adds a second, stricter check in front of every sensitive action, enforced through granular rules you define.
- What happens to actions that aren't covered by a granular permission?
- They fall back to Discord's native permission for that action, so nothing is ever left unprotected during rollout.
- Can I copy a permission set between roles or servers?
- Yes. Any role's granular permission set can be duplicated to another role, or exported as a template for other servers you manage.
- Is every action really logged?
- Every allowed and denied attempt is written to the Actions log with the actor, target, permission, and timestamp — including attempts that were blocked.
- Do I need an account to read the guides?
- No. The guides, the permission reference, and the staff planner are public. An account is only for the dashboard that enforces permissions on a server you manage.
Give your staff exactly what they need. Nothing more.
Invite the bot, connect the dashboard, and rebuild your role permissions one precise toggle at a time.