Private staff warnings
Record a member warning with a reason using /guard-warn. The command creates a staff record; it does not kick or ban the member or send them a direct message.
Keep moderation decisions informed with private staff warning records. Guard gives authorized moderators a server-specific history, with live permission and role-hierarchy checks before each action.
For staff teams that need a shared warning history and need clear, permission-aware staff tools.
A private record helps moderators avoid repeated explanations and make better-informed decisions without publicly calling out a member.
These are the features you can configure and use in the current release. Installation and the required Discord access are still needed.
Record a member warning with a reason using /guard-warn. The command creates a staff record; it does not kick or ban the member or send them a direct message.
Use /guard-warnings to review recent warnings within the same server. Each record includes the member, acting moderator, reason, and timestamp so staff have useful context.
Guard checks the caller’s live moderation permissions and the relevant role hierarchy. Selecting a staff role in settings does not silently give that role new moderation authority.
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.
Here is how the current feature fits into a real community workflow.
Read the Guard guideAn authorized moderator checks the member’s recent warnings with /guard-warnings.
If a new staff record is appropriate, they use /guard-warn with a clear reason.
The record remains private to authorized staff for future review; no punishment is applied automatically.
Good tools should explain what they need, what they store, and what they leave under your control.
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.
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.
Each app has its own Discord installation consent and server-specific settings. Available features stay free. Installing an app does not authorize every module; enable only the features you want and save deliberately.
Explore trust & safetyInstall Guard separately and select its workspace for the intended server.
Review its channel access and place its role above members it needs to process.
Enable and save the app when the staff team is ready to use private warning records.
The important details, without hidden assumptions about what is ready.
No. The current command records a private staff warning. It does not issue a timeout, kick, ban, or direct message.
No. Guard records warnings only; automatic protection is unavailable.
No. A setting cannot override the caller’s live Discord moderation permission or the role hierarchy.
Choose only the apps your community needs. Related apps have separate setup and permissions; an automatic connection between them is not enabled by installing both.
Choose the features your community needs, follow the setup guide and save your server’s settings.