Moderation
Warning, timeout, kick, and ban actions with durable case history, staff notes, and evidence.
Start here
Set up warnings and decide who can use timeouts
PulseOne → Dashboard → select your server → Modules → Moderation
Open PulseOne, choose your Discord server, then open Modules → Moderation using Set up or Manage.
Under Warning records, press Enable warning records. Confirm the status changes to Warning records enabled.
Scroll to Action configuration. Switch Timeout on or off; when enabled, set Min minutes, Max minutes and Required permission.
Set Kick, Ban, Staff notes and any Exempt role IDs or Exempt user IDs as needed, then press Save configuration and wait for the saved confirmation.
From Discord, have an authorized staff member try /warn on a test account. Return to the Case history section to confirm the recorded case.
Practical example
To stop PulseOne’s manual timeout action, turn off Timeout under Action configuration and save. This does not turn off AutoMod action ladders, Security rules or existing Discord timeouts.
Before you begin
- No module dependency listed.
- Discord bot permissions for the operational slice: ModerateMembers, KickMembers, BanMembers.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Choose trusted moderation roles and confirm the bot can act below its highest role. Review which punishments each staff tier may use.
Configure
Use a test member to create a warning case, then review its reason, evidence link, actor, subject and case history. Try an expiry-based action separately.
Test and verify
Open the moderation history and ensure the case is recorded. Confirm user/role exemptions, hierarchy denial and temporary-ban expiration behave as expected.
Features explained
What each feature does and what to check before publishing or installing the result.
Warning records through /warn
Use /warn for a documented warning without a Discord timeout; include a clear reason staff can audit.
Timeout, kick, and ban actions with native Discord enforcement
Timeouts, kicks and bans are enforced by Discord. Confirm role hierarchy and permissions before escalating from a warning.
Staff notes and URL/text evidence on any case
Attach staff notes or textual/URL evidence to the appropriate case; do not put private information in public evidence links.
Durable, guild-scoped case history
Filter and open cases to reconstruct the sequence of actions on a member; retain only evidence needed for the investigation.
Per-guild action toggles, permission-tier overrides, and role/user exemptions
Action switches and exemptions are per server. Test both an authorized moderator and an intentionally exempt member.
Temporary bans with automatic, scheduled unban
For temporary bans, enter an expiry and confirm the scheduled reversal; a permanent ban does not expire on its own.
If it still does not work
- Still timed out after turning Timeout off? Open Discord Server Settings → Audit Log and check who or what applied the timeout. The actor identifies whether PulseOne, another bot or a moderator performed it.
- If PulseOne applied it, inspect AutoMod → Actions & exemptions for a timeout action and Security for coordinated anti-raid protection. Those are separate settings.
- Check that Save configuration succeeded; an unchecked or unsaved field does not change the live policy. Existing timeouts remain until they expire or an authorized moderator removes them.
Troubleshooting and safety checks
- Action refused? Check the acting staff tier, target hierarchy, the bot's Discord permissions and any server-specific exemption.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.