A practical explanation of the latest additions, without unnecessary technical language.
Updated
Verification Gate
New members receive a verification prompt and automatically get the access role after passing. Choose a button or CAPTCHA, set a timeout, reject very new accounts, and use a fallback channel when DMs are closed.
Operations per minute
Instead of points, every protection has an allowed operation count over the last 60 seconds. For example, a limit of 3 applies the selected punishment when reached while unauthorized changes are still reverted.
Restore roles and members
Backups record roles and who held each role. If a role is deleted during an attack, the bot recreates it and attempts to return its previous members.
Collaborators and permissions
The owner can add people to the server dashboard by Discord ID, then grant only the permissions each person needs: viewing, protection, lists, logs, backups, or role links.
Trust card
An optional public page showing protection coverage and backup status without exposing sensitive configuration. You can disable it or rotate its link to invalidate the previous one.
Operations Center
The admin dashboard combines platform, bot, server, license, support, and recent-event status. Sensitive details are visible only to the owner.
Configure the Verification Gate correctly
1
Create a role such as “Verified Member”; keep it below the bot role and do not grant Administrator.
2
Remove “View Channels” from @everyone and grant it to the access role.
3
Open “Verification Gate” in the server dashboard, then select the access role and verification type.
4
Set the timeout and fallback channel as needed, enable the gate, and save.
5
Test with another account: passing verification should grant the access role and reveal the channels.
If @everyone can still view the channels, members can enter without actually needing verification even while the gate is enabled.
Stable role link explained — the latest feature
Discord assigns a new role ID when a deleted role is recreated. This feature gives your website one permanent address from which it can request the current ID, so you do not edit the website after every restoration.
What goes in each field?
Reference name
A label for your own organization, such as “Store customer role” or “VIP subscription”.
Site name
Optional; the name of the website that consumes this role, such as “My Store”.
External site URL
Optional and for organization only; enter the customer website itself. This is not the stable link generated by the system.
Current Discord role
Select the Discord role whose current ID should be tracked.
Which generated URL should I use?
JSONhttps://your-domain/role-ref/TOKENThe JSON URL returns the current ID plus the role name, connection state, and revision.
Plain IDhttps://your-domain/role-ref/TOKEN/idThe /id URL returns only the Role ID; it is simplest when your website fetches the number programmatically.
Example: create “Store customer role” and select Customer. The store requests the /id URL and receives the role ID. If Customer is deleted and restored with a new ID, the response updates automatically while the URL itself stays unchanged.
Important: the external website must support fetching this URL as an API. If it only has a field that accepts a fixed number and makes no API request, the link cannot update that field by itself.