Activity Protection
A private-bot-exclusive feature — choose specific roles you never want active while their holder is connected to Discord via the web browser client. The moment they connect through it, the protected role is automatically stripped, and restored once they close it.
Why?#
Some servers prefer sensitive roles (admin, trusted, or anything with real permissions) to never be active on their holder specifically while connected via the web client — for the server's own security or organizational reasons. It's entirely opt-in: nothing is protected unless you explicitly choose it.
How does it work?#
- Choose the protected roles from the dashboard, or via the !protection / !defense command ("Activity Protection" section).
- The moment a member holding one of these roles connects via the web client, their protected role is stripped instantly and logged in the security channel.
- It's automatically restored a short while after they close the web client — not instant on purpose, to avoid rapid back-and-forth toggling.
- Any attempt to grant the protected role to a member while they're still connected via the web client is blocked and reverted immediately — whether it's re-granted to them while still connected, or granted for the first time while they're already connected.
- Trusted users are fully exempt from this protection — their roles are never stripped, even while connected via the web client.
The one exception#
If the server owner or a trusted user is the one who granted the protected role to a member connected via the web client, it's left as-is — the protection trusts their explicit decision and doesn't try to 'correct' an intentional action.
Private-bot exclusive
This feature relies on Discord's Presence Intent (knowing a member's live connection status) — a permission unavailable to the main bot entirely due to its scale (thousands of servers). It's therefore exclusive to private bots. See Main vs Private Bot for the rest of the differences.