Build a Discord permission integer by ticking the permissions you want. The total updates live, ready to copy into a bot invite link or a role config.
Each permission is a bit, and the calculator adds them with exact big integer math, so high bit permissions like timeout members stay correct.
0Paste your application client ID to build an invite link with these permissions.
Check the permissions you want to grant.
The permission integer updates live at the top.
Copy the number and paste it where your bot or role config needs it.
Every Discord permission is a single bit, an on or off switch. The permission integer is the sum of the switches you turn on. Tick Send Messages and Embed Links, and the calculator adds their two values into one number that stands for exactly that set.
Bots and role configs read this number instead of a long list. One integer says precisely what a role or a bot is allowed to do, which is why setup tools ask for it.
The most common place is a bot invite link. The permissions value in the OAuth url is this integer, so the invite asks for exactly the access you picked. Many bot dashboards and libraries also take a permissions number when you define a role or a command.
Copy the total from the top of the calculator and paste it wherever the number is needed. It is the same value across the API, so it works in code and in config alike.
A member's access is the combination of every role they have, then adjusted by channel overrides. A role might allow Send Messages server wide, while a single channel denies it. The channel override wins for that channel.
Administrator is the exception. It grants everything and ignores channel overrides, so a role with Administrator can do anything anywhere. Give it only to people you fully trust, and build everyday roles from specific permissions instead.
Start from nothing and add only what the role needs. A regular member usually needs to view channels, send messages, read history, add reactions, and connect to voice. A moderator adds manage messages, kick, ban, and timeout. A bot needs only the permissions its features use.
Keeping roles tight is the safest habit. The fewer powers a role carries, the less damage a mistake or a compromised account can do.
Discord keeps adding permissions, and the newer ones sit on high bits well past what a normal whole number can hold exactly. Timeout members alone is over a trillion. The calculator does the math with big integers, so the total stays correct no matter which permissions you mix.
Handing out Administrator to save time is the big one. It bypasses every safeguard, so one bad actor with that role can wipe a server. Mention Everyone and Manage Roles are also stronger than they look and belong with trusted roles only.
When something is not working, check channel overrides before the role itself. A denied permission on the channel quietly beats an allowed one on the role.
It is a single number that encodes a set of permissions. Each permission is one bit, and the bits add up into the total you copy.
In a bot invite link as the permissions value, or anywhere a bot library or config asks for a permissions number.
Some permissions sit on high bits, so the total can exceed normal number limits. The calculator uses big integer math to keep it exact.
Administrator grants every permission and ignores channel overrides. Give it only to roles you fully trust.
No. The total is the sum of the selected bits, so the order makes no difference.