How it works

1. Someone raises the alarm

In your server, a moderator uses a simple command with the user’s ID (or @mention) and a clear explanation. Only people you trust with Ban Members can do this, so reports stay in the hands of senior staff.

2. The case waits in one shared queue

SellerBeware’s developers see every open case in the same place, no matter which server filed it. If that user already has an open case, the bot blocks duplicates so the team isn’t flooded with copies.

3. The SellerBeware team accepts or declines

The bot’s developers review the facts and press Approve or Deny. The moderator who filed the report usually gets a private summary so your server stays in the loop.

4. What “approved” actually does

If the team clicks Approve, that person’s Discord ID is added to the one shared list SellerBeware uses for join alerts. Every server that uses the bot is looking at the same list—so “approved” always means the same thing: this account should trigger a heads-up when they join.

If they click Deny, this report does not put them on that list. Other servers won’t get SellerBeware join alerts from this case.

5. Partner servers get a heads-up at join time

Each server picks its own alerts channel. When someone on the active list joins, moderators see a rich card with the reason, who filed it originally, and optional Kick or Ban buttons—only if their own role allows those actions in Discord.

6. Anyone can verify the facts

Curious members or staff can always look up a user ID to read the public record: statuses, reasons, and dates—no hidden dossiers.