Skip to main content

๐Ÿšฉ Reports & Vote Ban

Reports and Vote Ban put your community's eyes to work. Reports let any member flag a message for admin review โ€” with optional automatic action once enough members agree. Vote Ban goes a step further, letting the community itself vote to remove a problematic member.

Overviewโ€‹

  • Members report a message with /report or right-click โ†’ Apps โ†’ Report Message
  • Admins get a review embed with one-click Ban, Delete, and Ignore actions
  • A report threshold can trigger automatic action once enough unique members report
  • Vote Ban posts a public vote with Ban and Save buttons, with configurable thresholds, windows, and immunity

Configurationโ€‹

To configure both systems:

  1. Open your project in the Fren One webapp.
  2. Select the Discord server you want to configure.
  3. In the sidebar under Agent Configuration, select Moderation, then the Reports & Vote Ban tab.

The tab stacks two independent sections, each with its own master toggle and save.

Reportsโ€‹

Toggle "Allow members to report messages" on.

Automatic actionโ€‹

OptionDescription
Action on Report ThresholdWhat happens when enough members report the same message: No automatic action (notify only), Warn (default), Mute (timeout), Kick, or Ban.
Mute durationShown when the action is Mute. 1 second up to 28 days; default 1 hour. Required.
Reports Before ActionHow many reports trigger the action. Minimum 1; default 3.

Review notificationsโ€‹

"Send review notifications to" controls where the review embed goes:

OptionDescription
A dedicated channelDefault. Reveals a Report channel picker (required).
DM specific rolesReveals Roles to DM โ€” members with these roles get the review DM. Leave empty to DM the server owner.
The reported message's channelPosts the review in the same channel as the reported message.

A read-only list below shows recent reports (up to 30; empty state "No reports").

Vote Banโ€‹

Toggle "Let members vote to ban problematic members" on.

Vote thresholdsโ€‹

OptionDescription
Votes neededBan votes required to trigger the action. Minimum 1; default 5.
Max votes per memberHow many times one member can vote in a session. Minimum 1; default 1.
Vote window (minutes)How long a vote stays open. Default 30. 0 = never expires.
Cooldown (seconds)Minimum time between vote sessions per member. Default 300.

Outcomeโ€‹

OptionDescription
ActionBan (default), Kick, or Mute (timeout).
Mute duration (days)Shown when the action is Mute. 0โ€“28; default 0, where 0 = Discord's maximum (28 days).
Let members vote to save the targetDefault: on. Reveals Saves needed โ€” counter-votes required to cancel a ban. Minimum 1; default 3.
Delete the target's recent messagesReveals Delete message history (days) โ€” 1โ€“7; default 7.

Who can voteโ€‹

OptionDescription
Who can start and cast votesEveryone (default), Only specific roles (reveals Allowed roles), or Everyone except specific roles (reveals Excluded roles).
Immune rolesMembers with any of these roles can't be targeted.

A read-only list below shows recent vote sessions (up to 20; empty state "No vote ban sessions").

How it works in Discordโ€‹

Reporting: a member right-clicks a message โ†’ Apps โ†’ Report Message, or uses /report with the message link. Admins then receive the review embed โ€” in the report channel, by DM, or in the message's channel โ€” with four buttons: Ban + Delete Msg, Ban + Purge 7d, Delete Message, and Ignore. If the same message collects the configured number of reports from unique reporters, the automatic action fires on top.

Vote Ban: a member starts a session via right-click โ†’ Apps โ†’ Vote Ban, or /voteban with a message link. The agent posts a public vote message with Ban and Save buttons. If ban votes reach Votes needed within the window, the action runs; if saves reach Saves needed first, the session is cancelled.

Saving your changesโ€‹

Each section uses a batched save โ€” edits stay local until you select Save in the bar that appears at the bottom of the page. Leaving the page with unsaved changes shows a warning first.

Best practicesโ€‹

Community moderation that stays fair
  • Use a dedicated, admin-only report channel so review embeds (and their one-click ban buttons) aren't public.
  • Keep Action on Report Threshold at Warn or notify-only until you trust the signal โ€” reports can be weaponized in disputes.
  • Leave the save vote on and keep Immune roles covering admins and trusted members so vote bans can't hit your own team.
  • A vote Cooldown stops one member from spam-starting sessions against everyone they argue with.
One click bans

The review embed's Ban + Delete Msg and Ban + Purge 7d buttons act immediately. Route review notifications somewhere only trusted admins can see.

Troubleshooting

Nobody receives review notifications?

  • With A dedicated channel selected, a Report channel must be set and the agent must be able to post there.
  • With DM specific roles and no roles selected, the review goes to the server owner's DMs โ€” check there.

A vote ban ended without any action?

  • The session may have hit Saves needed counter-votes, or the Vote window expired before Votes needed was reached.
  • The target may hold an Immune role.

Members can't start a vote?

  • Check "Who can start and cast votes" and the per-member Cooldown between sessions.