Get Guard ready.

Apply Balanced protection, enable whitelist exemptions and automatically fill missing log destinations.

Who can use it

Server owner, active delegate or configured bot operator

Usage

/autoconfig | !autoconfig

1. Move Guard’s highest role to the top of the server’s role list and give it Administrator permission, then run /autoconfig.
2. Guard applies Balanced protection with invitation-only link filtering, keeps existing action quotas and log destinations, and uses six grouped log channels for missing destinations.
3. Use Add to whitelist to select members or bots, then confirm. You can also use /whitelist later. Click the diagnostic button to check the setup privately.

Setup takes effect immediately. Only add accounts you trust: they bypass protections with whitelist support. This does not grant command or dashboard access. Existing owner, independent and role exemptions are kept. Anti-DDoS, captcha, badword and honeypot activation stays unchanged. Existing log channels are not deleted.

Check Guard’s permissions, role position, active protections and log destinations.

Who can use it

Server owner or active delegate

Usage

/check | !check

1. After setting up Guard, run /check in the server. The result is visible only to you.
2. Read the items to review and follow their instructions. Use /panel for individual settings or /presetlogs for log channels.
3. Run /check again after making changes. Large reports have page buttons.

/check replies privately; !check replies publicly in the channel. Both require the server owner or an active delegate. Unauthorized text commands receive no reply. This command does not change settings, punish anyone or simulate a raid. None is a valid sanction choice.

Set up Guard inside a guided Discord activity.

Who can use it

Server owner or active delegate · Guard Public only

Usage

/guard-setup

1. Run the slash command in the server you want to protect, using its owner’s account or an active delegated administrator’s account.
2. Follow the activity, choose your protections and allowed users, then review the changes.
3. Choose whether Guard should create your logs, and confirm to apply your settings.

This activity belongs to Guard Public. On a personal Guard bot, use /setup. If the activity cannot open, /setup remains available.

Choose a profile, customize it and apply it after reviewing the changes.

Who can use it

Server owner, active delegate or configured bot operator

Usage

/setup

1. Choose Essential, Balanced, Reinforced or Maximum, or start from the current configuration.
2. Review the enabled protections, sanctions and limits. You can choose allowed-user lists for all or selected modules.
3. Open the review, check what will change, then confirm. You can also save and reuse a custom profile.

All four standard profiles include voice protection. Applying a profile can change existing module settings; read the review before confirming.

Adjust one protection without applying a complete profile.

Who can use it

Server owner, active delegate or configured bot operator

Usage

/panel [v2:true]

1. Choose a module, then enable or disable it.
2. Choose its sanction, allowed users and logs. Supported modules also have an action limit and time window.
3. Use the buttons to edit a value. Review the updated module before moving on.

The familiar panel opens by default. Set v2 to true for the newer interface. The /owner list alone does not grant access to /panel.

Keep logs together, group them by topic, or use a separate channel for each protection.

Who can use it

Server owner, active delegate, Guard owner list or configured bot operator

Usage

/presetlogs

1. Run /presetlogs and choose one channel per protection, grouped channels, or one channel for everything.
2. For each destination, let Guard create a channel or select an existing text channel. Grouped logs cover channels, roles, members, messages, server events and voice.
3. Review and confirm to apply. If old log channels were replaced, keep them or confirm their deletion separately. Doing nothing keeps them. Channels still in use are kept; cleanup stops during raids or recovery.

New channels are private under @Logs. Existing channels keep their permissions. All protections, including Anti-DDoS, are included; only log settings change. Guard needs access to selected channels and permission to create new ones.

Choose a private shuffled keypad or web verification before members receive an access role.

Who can use it

Server owner, active delegate or configured bot operator

Usage

/captcha | !captcha

1. Create a verification channel and a normal Verified role below Guard. Restrict other channels to verified members using Discord permissions.
2. Choose the channel, role and verification type in /captcha, then enable it. Guard prepares only that channel: newcomers can view but not write, and the Verified role hides it. Use Message to customize the embed and save your changes.
3. Members click Verify. Web verification can report shared networks and VPN signals; enable anti-alt only if you want linked newcomers kicked.

Disabled by default. Network checks require web verification; a shared connection does not prove two accounts belong to the same person. Detected VPNs can be asked to disconnect and retry. Configuration is separate from /panel and presets.

Choose a clearly marked channel where non-exempt members must not post, and decide what Guard should do.

Who can use it

Server owner, active delegate or configured bot operator

Usage

/honeypot | !honeypot

1. Choose an existing text channel under Rules. Clearly label it as a channel where members must not write.
2. Choose delete only, timeout, remove roles, kick or ban. Set Exemptions and an optional separate Logs channel.
3. Select Enable and confirm. Changing the trap channel disables protection until you confirm again.

Disabled by default. The server owner and active delegates are exempt. Bots, plain webhooks and system messages are ignored. Threads are excluded unless you opt in. Configure this separately from /panel and preset profiles.

Choose ready-made language lists, add your own words and preview matches before enabling the filter.

Who can use it

Server owner, active delegate or configured bot operator

Usage

/badword

1. Choose one or more starter languages in Lists. Use Your words and Allowed words to adjust them.
2. Choose an optional sanction, ignored channels, exemptions and a Logs channel. Try a message privately with the test button.
3. Enable protection when ready. Every saved change takes effect immediately.

Disabled by default. Whole words and phrases are matched without case or accent differences. The server owner and active delegates are exempt; use the test button to test as an owner. This filter is configured separately from /panel and preset profiles.

Manage trusted accounts in Guard’s owner list for this server.

Who can use it

Server owner, active delegate or configured bot operator

Usage

/owner [action:add|remove|clear] [user:@member]

1. Run /owner to inspect the list.
2. Use action add or remove and select a member. Clear removes the whole list.
3. In each protection, enable Owner list only where those accounts should be exempt.

This list is not Discord server ownership. It can grant access to commands such as /antiddos, /whitelist and /presetlogs, but does not grant /setup, /panel or dashboard access.

Keep a list of accounts that selected protections may trust.

Who can use it

Server owner, active delegate, Guard owner list or configured bot operator

Usage

/whitelist [action:add|remove|clear] [user:@member]

1. Run /whitelist to inspect the list.
2. Add or remove a selected member. Use clear only when you want to empty the list.
3. Open /panel and enable Whitelist under Exemptions for the modules where it should apply.

Being whitelisted does not automatically exempt an account from every protection and does not grant dashboard access. A module’s own list and role exemptions are separate.

Give up to two trusted administrators access to Guard on this server. They can configure protections, use the dashboard and are exempt from Guard’s protections while their delegated access is active.

Who can use it

Server owner only

Usage

/delegate [action:add|remove|clear] [user:@member]

1. The server owner opens /delegate. The person you want to add must already be a server member with Discord’s Administrator permission. Guard refuses the addition if that permission is missing.
2. Choose Add an administrator and select the person. Changes save automatically. There are two slots per bot and server. Delegates can use /panel, /setup and /antiddos, plus the dashboard. On Guard Public, they can also open /guard-setup.
3. To revoke access and free a slot, use Remove an administrator or the remove command below. Clear removes every delegate. Delegates cannot manage this list themselves.

Losing Administrator immediately suspends delegated access, including open menus. The person keeps their slot and becomes active again if Administrator is restored. This command does not give Discord permissions. Guard’s /owner and /whitelist lists are separate; delegation never grants internal bot commands or Manager access.

Manage voice protection for occupied voice channels across the server.

Who can use it

Server owner, active delegate, Guard owner list or configured bot operator

Usage

/antiddos

1. Open /antiddos in the server. No voice-channel argument is needed.
2. Check whether protection is enabled and select a Logs channel.
3. Use Scan when you need Guard to check the occupied-channel list again. Review the incident report after a disruption.

Voice protection is disabled by default. Enable it explicitly when needed. Guard may refresh a channel’s region; it never disconnects or sanctions participants.

Choose the server’s language from the supported languages.

Who can use it

Server owner, active delegate, Guard owner list or configured bot operator

Usage

/langue

1. Run /langue, then select a language in one of the two menus.
2. Use the server language for shared bot output and text commands.

Slash-command replies automatically follow the user’s Discord language when supported. Changing your VPN does not select a Discord language.

View, add, remove or reset the prefixes used by text commands.

Who can use it

Server owner, active delegate, Guard owner list or configured bot operator

Usage

/prefix [action:add|remove|reset] [prefix:text]

1. Run /prefix to inspect the current prefixes.
2. Choose an action and enter the prefix, or use the menu buttons.
3. Try a permitted text command with the new prefix. Slash commands stay available.

Text commands are restricted. Most require the server owner or a configured bot operator; !antiddos also accepts Guard’s owner list. Unauthorized text commands deliberately receive no reply.

Find the available commands and their usage from inside Discord.

Who can use it

Members with access to the slash command

Usage

/help [command:name]

1. Run /help to open the command menu.
2. Select a command, or pass its name in the command option, to see its description and usage.

A command being listed does not grant permission to use it. For setup and security settings, start with the server owner.

Check Guard’s connection and API response time.

Who can use it

Members with access to the slash command

Usage

/ping

1. Run /ping and read the Gateway and API values.
2. Use Refresh for a new reading if needed.

These values describe Guard’s Discord connection. They do not measure a particular voice channel or confirm a voice attack.

An operator control for enabling or disabling raid mode and pausing server invites.

Who can use it

Server owner, active delegate or configured bot operator

Usage

/raidmode [statut:true|false]

1. An authorized owner, delegate or operator opens the command to inspect its state.
2. Enable or disable using the buttons, or pass the optional statut value.

Guard’s /owner list alone does not grant this command. Automatic anti-raid responses are handled by the protections.

Protect channels from unauthorized deletion.

Guard can recreate saved channel structure and settings. Deleted messages cannot be recovered.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Control the creation of new channels.

Unauthorized created channels can be removed.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Protect channel settings and permissions.

Saved channel settings and permissions can be restored.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Protect roles from unauthorized deletion.

Saved regular roles can be recreated. Roles belonging to integrations are handled by their integration.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Control the creation of new roles.

Unauthorized created roles can be removed.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Protect role permissions and settings.

Saved role settings and permissions can be restored.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Control who can grant Administrator permissions.

Guard handles both Administrator role assignments and changes that grant Administrator to an existing role.

Available sanctionsBanKickRemove rolesTimeoutNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Control the assignment of roles to members.

An unauthorized role assignment can be removed.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesTimeoutNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Limit bans performed by one account.

Affected bans can be reversed according to Guard’s incident recovery rules.

Anti-Ban already has its own action limit and time window. There is one quota to configure, not a second Anti-Mass switch.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Control the removal of member bans.

An unauthorized unban can be reversed by restoring the ban.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Protect members from abusive kicks.

A kicked member cannot be automatically brought back to the server.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Control who can add bots to your server.

An unauthorized added bot can be removed.

Available sanctionsBanKickRemove rolesNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Control sensitive changes to members.

Supported member changes can be reverted.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesTimeoutNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Stop repeated messages from one account.

Messages are cleaned up in groups. The sanction is handled separately; Guard does not wait for cleanup to finish before attempting it.

The maximum counts messages by one account in the selected time window. For example, 6 / 5s means a message limit over five seconds, not minutes.

Available sanctionsBanKickTimeoutNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Remove unauthorized links and invitations.

Unauthorized links or invitations are removed according to the selected control. Configure the scope and exemptions for your community.

Available sanctionsBanKickRemove rolesTimeoutNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Control the creation of new webhooks.

Choose how Guard handles the unauthorized webhook. Review the control before selecting channel recreation.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesTimeoutNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Protect message embeds from being hidden.

Controls the deletion of server integrations. This does not recover deleted message content.

Protect the server name, icon and settings.

Supported saved server settings can be restored.

An optional Anti-Mass quota limits actions by one account over a configurable time window. Seconds, minutes, hours, days and weeks are supported, up to four weeks. Review the saved values before enabling it.

Available sanctionsBanKickRemove rolesTimeoutNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Limit forced disconnections from voice channels.

A disconnected participant may need to rejoin voice themselves.

Available sanctionsBanKickRemove rolesTimeoutNone

Allowed-user lists and role exemptions are configured separately for this module. Understand exemptions →

Monitor occupied voice channels across your server.

Covers occupied voice and stage channels across the server. A region refresh does not guarantee a different voice endpoint.

Enable it and choose its logs with /antiddos. Occupied channels are checked across the server; there is no per-channel command argument.