Sentinel Add to Discord

One blacklist. Every server that opts in.

Sentinel stops known scammers, raiders and hacked accounts before they do damage. A user removed from one protected server is flagged in all of them. It does nothing until an admin runs /setup.

#sentinel-log · example alerts
Blacklisted user joinedCategory: Scammer · Case #214
Action: banned · added by a Sentinel developer, proof saved
Honeypot triggeredPotentially compromised account
Removed, messages wiped, DM sent with rejoin invite
Lockdown ended12 channels restored to their original permissions

What it does

🚫

Global blacklist

Only the Sentinel developers can blacklist. Every entry has a category, reason and saved proof, and users can appeal. You pick ban, kick or alert, and can whitelist people in your own server.

🪤

Honeypot

A trap channel for hacked accounts. Whoever posts there is removed, their recent messages are wiped, and they get a DM on how to secure their account. Scam links caught are blocked across protected servers.

🚨

Raid and AutoMod

Anti-raid, new-account filter, and invite, spam, mention, caps, link and emoji rules. All off until you turn them on.

🔒

Lockdown

Lock a channel or the whole server, then restore the original permissions exactly. Plus ban, warn, timeout and purge.

🛡️

Security tools

/security audit grades you A to F, /drill simulates a raid, and /threat scores any account 0-100.

🎮

Roblox and ER:LC

Verify accounts with a code in the Roblox bio, pull risk reports, and get alerted when a blacklisted player joins your ER:LC server in-game.

One ban reaches every server

Each dot is a server that opted in. Click one to ban a scammer there and watch the blacklist spread. Example network.

Watch it stop a raid

Quiet. Nobody is joining.

Start in three steps

1Add Sentinel
Keep its role above the roles it should moderate.
2Run /setup
One panel holds every setting. Nothing happens until you do.
3Scan now
Check the members you already have against the blacklist.

Commands

Admin means Manage Server. Staff means Ban Members or Manage Server. Run /command info in Discord for the same guide.

Setup (admin)

/setup settings panel

/scan check current members

/config /automod view settings

/whitelist allow a user in your server

/raidmode manual join lockdown

/verify-channel post a verify button

Moderation

/ban /unban /tempban /kick

/warn /warnings /delwarn /clearwarns

/timeout /untimeout

/purge /slowmode

Lockdown

/lockdown /unlockdown whole server

/lock /unlock one channel

Allowed for admins or the lockdown role set in /setup.

Staff lookup

/blacklist check /blacklist info

/threat /trace /alt-check

/roblox profile /roblox alts /roblox-lookup

/report send someone to the developers

Security (admin)

/security audit /perms exposure

/incident report /drill

/erlc connect /erlc status

Everyone

/appeal start /appeal status

/verify /unverify /link-check

/help /about /stats /ping /status view /invite /support

Automatic protection

No commands needed. Turn these on in /setup: the blacklist, anti-raid, new-account filter, chat AutoMod, honeypot, and the shared scam-link feed.

Setup guide

  1. Invite Sentinel. Use the Add to Discord button and accept the permissions.
  2. Move Sentinel's role up. It can only act on members whose top role is below its own.
  3. Run /setup. Turn on Blacklist protection and pick a log channel. Use the page menu to reach AutoMod, Punishments, Moderation and Lockdown, Honeypot and the Security Log.
  4. Press Scan now. This checks everyone already in the server.
  5. Try /drill. It shows what would happen in a raid and nothing is punished.

Permissions it asks for

Ban, Kick, Moderate Members, Manage Messages, Manage Channels, Manage Roles, View Channel, Send Messages, Embed Links, Attach Files and Read Message History. Administrator is not required.

Chat AutoMod and the honeypot read message content, so Sentinel needs the Message Content and Server Members intents.

Common problems

Nothing gets banned. Blacklist protection is off until /setup is run. "Missing permissions". Move Sentinel's role higher. Still stuck? Ask in the support server.

Blacklist policy

How the shared blacklist works. Last updated September 30, 2026.

Who can blacklist

Only the Sentinel developers. Server owners and staff cannot add entries, but they can send a report with proof through /report, and the developers decide.

What gets someone listed

Conduct that harms other communities, recorded under one of these categories: Scammer, Raider / Nuker, Harassment, NSFW, Impersonation, Alt Account, Exploiter, or Other. Each entry stores a reason and, where available, proof saved by the developers.

What servers see

Protected servers see the category, reason, case number and proof link for the user concerned. Each server picks its own action (ban, kick or alert) and which categories it acts on.

Temporary and permanent

Entries can have an expiry date. Expired entries are removed automatically and users we banned are unbanned.

Watchlist

The developers can watch an account. Protected servers get an alert when it joins, but nobody is banned for being on it.

Appeals

Blacklisted users can appeal from the DM they receive or with /appeal start. The developers review each one and reply by DM. After a denial, you can appeal again after 14 days. If an appeal is accepted, the entry is removed and the user is unbanned in servers where Sentinel banned them.

Mistakes

If you believe an entry is wrong, appeal, or ask a developer in the support server.

Privacy policy

Effective September 30, 2026. Draft for legal review before publishing. Operator: the Sentinel developers (two individuals). Contact: the support server.

What we collect

  • Discord data: user IDs, usernames, server IDs, channel and role IDs, and account creation dates.
  • Blacklist data: reasons, categories, proof files, case history, watchlist entries, developer notes, reports and appeals.
  • Moderation data: warnings, tempbans, channel lock records and server settings.
  • Honeypot data: when someone posts in a honeypot channel, we save their ID, username and the message text.
  • Roblox data: the link between a Discord account and a Roblox account, verification codes, and verification attempts. Roblox profile details are read from Roblox's public API when requested.
  • ER:LC data: if an admin connects a server, its API key and a join-log position.
  • Scam links: domains posted in honeypot channels or added by the developers.

What we read but do not keep

AutoMod reads message content to detect spam, invites, links and similar. Messages are not stored, except honeypot catches as described above.

How we use it

To run the blacklist, enforce server settings, review reports and appeals, detect raids and scams, and keep the bot secure. We do not sell data or use it for advertising.

Who sees it

Blacklist entries and basic network records (such as whether an account was stopped elsewhere) are shared with servers that use Sentinel. Server names are only visible to the Sentinel developers. Data is processed on our hosting provider's servers and, for Roblox and ER:LC features, sent to those services.

How long we keep it

Blacklist and case records are kept while the entry is active and for audit history afterward. Honeypot logs keep the latest 500 entries per server. Other data is kept until a server removes Sentinel or you ask us to delete it.

Your choices

You can unlink your Roblox account with /unverify. To request access to or deletion of your data, join the support server and message a developer. Blacklist records may be kept where needed to protect other communities or we are required to keep them, and you can appeal an entry at any time.

Security

We limit access to the database to the Sentinel developers. No system is perfectly secure, and we cannot guarantee absolute security.

Children

Sentinel is for people 13 and older, the minimum age for Discord. We do not knowingly collect data from younger children.

Changes

We will update the date above when this policy changes.

Terms of service

Effective September 30, 2026. Draft for legal review before publishing.

Using Sentinel

By adding or using Sentinel you agree to these terms and to Discord's Terms of Service and Community Guidelines. You must be 13 or older.

Server owners and admins

You decide what Sentinel does in your server, and you are responsible for those settings and for actions taken by your staff. Do not use Sentinel to harass, discriminate, or break the law.

Blacklist and reports

Reports must be honest and supported by real evidence. False or abusive reports can lead to being blocked from using Sentinel. The Blacklist policy explains how entries and appeals work.

Things you may not do

  • Abuse, overload or attempt to break Sentinel or its data.
  • Collect blacklist data to publish or use outside Sentinel.
  • Evade a blacklist or bot ban with alternate accounts.

Our right to act

We may bot-ban users, remove servers, or end access at any time if these terms are broken or to protect other communities.

No guarantees

Sentinel is provided as is. Detection is not perfect, so it may miss bad actors or flag someone by mistake. We do not promise uninterrupted service.

Liability

To the extent the law allows, we are not liable for indirect or consequential losses from using Sentinel, including loss of server data, members, or reputation.

Changes and contact

We may update these terms and will change the date above. Continued use means you accept them. Questions: ask a developer in the support server.