> For the complete documentation index, see [llms.txt](https://docs.securitybot.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.securitybot.gg/anti-nuke/anti-nuke/dangerous-permissions.md).

# Dangerous Permissions

Security monitors these Discord permissions because they can be used to damage or take over a server.

## Permission List

| Permission           | Risk Level | Why It's Dangerous                                |
| -------------------- | ---------- | ------------------------------------------------- |
| **Administrator**    | Critical   | Grants all permissions, bypasses all restrictions |
| **Manage Server**    | Critical   | Can change server settings, region, and features  |
| **Ban Members**      | High       | Can remove members permanently                    |
| **Kick Members**     | High       | Can remove members from the server                |
| **Manage Channels**  | High       | Can delete/modify all channels                    |
| **Manage Roles**     | High       | Can create/delete roles and change permissions    |
| **Manage Webhooks**  | Medium     | Can create webhooks to spam or impersonate        |
| **Manage Messages**  | Medium     | Can delete messages in bulk                       |
| **Manage Threads**   | Medium     | Can delete/modify threads                         |
| **Manage Nicknames** | Low        | Can change all member nicknames                   |

## How Security Uses This List

Security monitors when these permissions are:

1. **Granted to a role** - Triggers "Dangerous Permissions" action
2. **Role with these permissions assigned to a user** - Triggers "Dangerous Roles" action

## Protection Behavior

When someone grants dangerous permissions:

* The action counts toward their Anti-Nuke limit
* If they exceed the limit, they receive the configured punishment
* The action may be logged (if logging is enabled)

## Recommendations

* Only grant dangerous permissions to roles held by highly trusted users
* Use Security's permission system instead of Discord permissions for moderators
* Regularly audit who has dangerous permissions in your server
* Consider using the whitelist for administrators who need these permissions

## Related

* [Moderation](/other-modules/moderation.md) - Use Security's safe permission system
* [Whitelist](/whitelist/whitelist.md) - Exempt trusted users from monitoring