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.
Settings#
| Setting | Description |
|---|---|
| Protected roles | Up to 30 roles from the dashboard (the in-Discord bot command menu only fits 25, a Discord limit). |
| Exempt members | Members whose protected roles are never removed, whether they use the web client or appear offline. |
| Remove roles when offline | Off by default. Some tools hide using invisible/offline status to bypass web detection; this option removes the roles the moment the account goes offline or invisible. |
| Restore roles automatically | On by default. When off, the bot never gives roles back and logs what was removed so you can re-add them manually. |
| Restore delay after leaving web | From 0 to 60 minutes (default 5), plus a random 5 to 20 second delay. It applies only to roles removed because of the web client; roles removed because of going offline return as soon as the member comes back on an app. |
| Log channel | A dedicated channel for this protection's logs from the Logs tab; if left empty they go to the Security Logs channel. |
Interaction with role commands and !down#
A role that was removed and is waiting to be restored stays 'owed' to the member in the protection record even though they don't actually hold it in Discord. The commands therefore treat it as if it were theirs:
!addrole,!removeroleand!togglerole(prefix and slash): a pending role counts as held by the member, so running the command on it removes it and cancels its restore permanently instead of granting it again, and the reply says so.!down: pending administrative roles are included in the down punishment, so they don't return to the member after it ends.- If a member leaves, is kicked or banned, their pending-role record is deleted immediately so they can't get the roles back if they return.
Safety guarantees#
- Removed roles are stored in the database, so they aren't lost when the bot restarts.
- Removal and restore for a single member run one at a time, one request per role, so operations never overlap and the member's other roles are untouched even if their connection flaps quickly.
- Roles the bot can't edit (above its own role, or the member is the server owner) aren't retried endlessly; the bot pauses on them instead of flooding Discord with rejected requests.
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.