Guard documentation
Keep private staff warning records and review a member’s recent history.
On this page
A ready workspace for Guard.
Sign in as the server owner or with Manage Server permission. Open Guard, choose the correct server inside the app, and check its connection. Each app needs its own Discord installation consent.
New to Guildryx? Follow Getting started first
Configure the required channels, roles, and access before enabling and saving. Saving applies to this app in the selected server.
Prepare the staff workflow
- Install Guard and open its workspace for the correct server. Review the connection and enable Guard, then save.
- Warning records require live Manage Messages or Moderate Members access, or the server owner. Discord command visibility may also be restricted by your server’s integration settings.
- To record a warning, both the moderator’s highest role and Guard’s highest role must be above the target member. Server owners have the moderator hierarchy exception.
- Any staff-role or log-channel preferences do not bypass permissions or activate public warning delivery. Current warnings are private command replies.
Record and review a warning
- Use /guard-warnings and choose the member in Discord’s member field to check their latest retained records.
- Use /guard-warn, select the member, and enter a clear reason between 1 and 500 characters.
- The reply confirms the private record. No direct message, timeout, kick, ban, or role change is performed.
- You cannot warn yourself, the owner, a bot, or an administrator. History is isolated to the current server.
Understand retained history
- The history command shows up to the ten latest retained warnings for the chosen member.
- Records are retained for up to 90 days, with at most the newest 500 per server. This is not a permanent case archive.
- Pause Guard and save when your team should stop using its current features. Automatic protection is unavailable.
Commands & controls
Use these controls for the current release inside the relevant Discord server. Discord’s command picker supplies required options; app-specific permissions still apply.
/guard-warnRecord a private staff warning with a reason.
/guard-warningsReview recent private warnings for a member in this server.
What this app needs and keeps
Discord access
Warning commands require live moderation permission and hierarchy checks. Records are server-specific and are not a public reputation score or a shared blacklist across communities.
Stored information
Guard stores the subject, acting staff member, reason, and time. The current release retains up to the newest 500 records per server and queries records within a 90-day window.
Guard records and retrieves private staff warnings. It does not automatically moderate, punish, kick, ban, run AutoMod or provide raid protection. Selecting a staff role does not grant new Discord permissions.
Troubleshooting
The warning command is not visible
Confirm Guard is installed, review Discord integration command permissions, and check your moderation permissions. Dashboard Manage Server access alone does not grant every moderation command.
A target is rejected
Check the target restrictions and both role hierarchies. Do not move Guard above protected roles just to bypass a legitimate boundary.
No warnings are found
Check the selected server and member. Records from other servers, older than the retention period, or outside the newest retained records are not included.
Still stuck? Check Service Status, then contact private support with the app, server ID, and the error. Never send a password, bot token, or backup code.