Skip to main content
Seshy’s Moderation module gives your staff team a complete toolkit for managing members, with every action automatically logged to a searchable case history. From informal warnings to permanent bans, each moderation action is timestamped, attributed to the moderator who issued it, and stored in a case record that any authorized staff member can look up. This creates a transparent, auditable record that keeps your team accountable and helps you spot repeat offenders before small problems become large ones.
Moderation commands respect the Permission Hierarchy configured in /settings → Permissions. Only roles assigned the appropriate permission level can run each command — for example, only senior staff may be able to issue bans while junior staff are limited to warns and mutes.

​
Available Actions

Seshy covers the full range of standard moderation actions. Each action accepts a required target and an optional reason that is recorded in the case log and included in the audit log embed.
Issue a formal warning to a member. The warn is logged as a case in the member’s history and posted to your audit log channel. Use warns for first offences or minor rule violations where removal from the server isn’t warranted yet. Warns feed into the infraction escalation system configured in the Staff Module.

​
Case History

Every moderation action Seshy processes creates a case record automatically. Cases are numbered sequentially and stored in a searchable log. You can look up cases by:
  • User — view all cases against a specific member
  • Moderator — see every action a specific staff member has taken
  • Case type — filter by warn, kick, mute, or ban
  • Date range — narrow results to a specific time window
This makes it straightforward to build a history before escalating action on a repeat offender, to audit a staff member’s moderation conduct, or to pull evidence when handling an appeal.
Cases are permanent records. Even if a member leaves and rejoins your server, their case history is retained and will appear when you search by their Discord user ID.

​
Audit Logging

Every moderation action Seshy processes also posts a structured embed to your configured audit log channel in real time. Each audit log entry includes:
  • Moderator — the staff member who issued the action
  • Target — the member who was moderated
  • Action type — warn, kick, mute, ban, or unban
  • Reason — the reason provided at the time of the action
  • Timestamp — the exact time the action was taken
  • Case ID — a reference number that links back to the full case record
Configure your audit log channel in /settings → Moderation so every action is captured in a dedicated channel your staff can monitor.
If no audit log channel is configured, Seshy will still log cases internally — but your staff won’t see real-time action embeds in Discord. Set up your audit log channel before your moderation team starts using Seshy.

​
Moderation Desk (Dashboard)

The web dashboard’s Moderation Desk provides a live staff panel for managing moderation actions visually — browse case history, filter by action type, review moderator activity, and issue actions without typing commands. The Moderation Desk is part of the v2 dashboard currently in development.

Moderation Desk

Open the Moderation Desk to browse cases, review staff activity, and manage moderation actions from a visual interface.

​
Configuration

Set up your Moderation module in /settings → Moderation:
1

Set your audit log channel

Choose the channel where Seshy will post real-time moderation action embeds. Dedicate a private channel visible only to staff so the log stays clean and accessible.
2

Assign staff roles

Map your server’s staff roles to Seshy permission levels so the right people can run the right commands. Configure this in /settings → Permissions.
3

Configure infraction thresholds (optional)

If you want warns to automatically escalate to timeouts or bans at defined thresholds, configure the escalation ladder in /settings → Staff Module → Infractions.
The Ares Security module handles automated threats such as nukes, raids, and unauthorized bot additions separately — it operates independently of your staff team with a sub-second response time and requires no manual intervention. The Moderation module is for deliberate, manual staff actions against specific members.

​
Key Commands