Setting Up Roles
Add roles to be assigned when a user joins.
When a user joins, they are automatically assigned the roles you have configured. It is a simple yet effective way to remove less advanced spam bots from your server without impacting the experience of legitimate users.
GateKeeper supports auto-role features without having rule screening enabled — however, we always recommend enabling rule screening on community servers as it provides additional protection against spam bots.
To manage this feature, use the autorole command group. The bot requires permission to manage roles and the target role must be lower than the bot highest role.
/autorole add <role> [invite]Adding roles is quite simple.
Type the command above, select the role you want to assign, and hit enter. The bot will run a couple of checks to ensure it has the correct permissions and then respond with a confirmation message, or explain any issues it found.
If you include an invite code, GateKeeper checks that the invite exists in the server before saving the entry.
We recommend using the list command afterwards to confirm the role has been set up correctly.
Bonus Roles
You can assign up to 5 roles per server. GateKeeper Plus subscribers get an additional 10 roles for a total of 15.
Invite Specific Roles
GateKeeper Plus subscribers can assign different roles depending on which invite link a user joined with. Use the optional
inviteparameter and select from the autocomplete list of your server's active invite codes.
/autorole remove <role> [invite]Removes an auto-assigned role. If the role was tied to a specific invite, pass the same invite code to target that entry. Removing a role deducts it from your total auto-role count.
Remove All Roles
/autorole removeallRemoves all auto-assigned roles for the current server.
/autorole listLists all configured auto-assigned roles, grouped by invite code. Roles with no invite code assigned are shown under Roles added to unspecified invites and apply to all new members regardless of how they joined.
If a role no longer appears in this list, check role order and bot permissions first, then contact the support server if needed.
Last updated