Help center

Welcome

SellerBeware connects participating Discord servers so serious reports can be reviewed once and shared responsibly. Approvals and denials are made by SellerBeware’s developers—not by each server’s admins. This guide uses everyday language and matches what you’ll see in Discord.

Add the bot

1. Use the green Add SellerBeware button on our home page (or the link your admin shares).
2. Pick the correct Discord server from the list.
3. Review the permissions Discord shows you. SellerBeware only asks for what it needs to read messages, send alerts, and understand who joins.
4. Complete any verification Discord asks for. You should see SellerBeware appear in your member list.

Connect your server

After SellerBeware joins, a server administrator should run +setup in a channel your staff can access.

1. The bot will ask which channel should receive join alerts. Choose a private moderator room—not a public lobby.
2. You can paste the channel ID, or type channel followed by a #mention of that channel.
3. When setup succeeds, try +settings (with Ban Members) to confirm the binding looks right.

If your team later moves alerts elsewhere, admins can run +setchannel with the new channel.

Roles & permissions

• Administrator is required to run setup and change the alerts channel.
• Ban Members is required to file reports (+add) and read configuration (+settings).
• None — lookup (+search) and general help (+help, +invite) do not require those permissions.
• SellerBeware’s developers approve or deny each case in the central review queue (not your server’s admins).

Discord still enforces who may kick or ban someone in your server. SellerBeware never overrides Discord’s own rules.

Filing a report

Use +add with the user’s ID or mention, then a clear explanation. Short or vague reasons may be rejected by the bot so the SellerBeware team gets usable context.

Writing a strong reason

• Describe what happened and why it matters to your community.
• Mention patterns (“third chargeback this week”) rather than insults.
• Link to evidence hosted elsewhere if your server rules allow it (paste URLs in the reason text).

When duplicate reports happen

If that user already has an open case in the queue, SellerBeware will stop a second submission until the first case is finished. That keeps the team focused and prevents conflicting stories.

Review & decisions

SellerBeware’s developers see a card with every detail: who filed it, from which server, the reason, and whether the person was seen before. Approve adds them to the shared list used for join alerts. Deny closes the case without broadcasting it to other servers.

Whenever possible, the original reporter receives a private summary of the outcome so your moderators stay aligned.

Join alerts

Once a case is approved, other servers hear about it only when that Discord account actually joins. The alert lands in the channel you configured during setup.

Each alert explains who joined, summarizes the accepted reason, and shows where the original report came from.

Kick & ban buttons

Alerts may include optional shortcuts. Only people who already have kick or ban rights in your server will see those buttons succeed. If Discord says your role is too low, elevate the bot’s role or ask a higher moderator.

Looking someone up

+search accepts a user ID and shows every row on file: pending, approved, or denied. It’s intentionally public inside your server so members can verify claims instead of spreading rumors.

Changing settings later

• +settings — confirm the alerts channel and see when the link was created.
• +setchannel — move alerts without redoing the entire setup flow.

Public database page

The Database page on this site lists the same public records you can already see with +search in Discord—search, filter, and skim rows in your browser whenever that’s easier than scrolling chat.

Troubleshooting

• The bot never responds. Check channel overrides: SellerBeware needs permission to read and send messages where you’re typing commands.
• +add says the server isn’t configured. Ask an admin to finish +setup.
• No join alert arrived. Confirm the case was approved, the member actually joined (not just renamed), and the bot still has access to your alerts channel.
• Buttons on an alert failed. Make sure the bot’s role sits above the target member and that you personally have kick/ban rights.

Common questions

Community & appeals

Join the official support server for onboarding help, appeals, and best practices. For legal notices, review our Privacy and Terms pages.