Documentation

Sentrix bot docs

Everything you need to set up Sentrix in your server, plus every command it has. Setup takes about two minutes.

1. Add Sentrix to your server

You need the Manage Server permission in the server you're adding Sentrix to.

Add to Discord

The invite asks for these permissions. Sentrix never needs Administrator, so don't give it that.

PermissionWhy
Ban MembersFor the ban action
Kick MembersFor the kick action
Manage RolesFor the quarantine action
View Channels, Send Messages, Embed LinksPosting alerts in your log channel
Attach Files, Read Message HistoryEvidence screenshots and replies
Role order matters. Discord only lets a bot act on members whose highest role is below the bot's own role. In Server Settings › Roles, drag the Sentrix role above your member roles, and above the quarantine role if you use one.

When Sentrix joins, it posts a short welcome message. From that moment every member who joins is checked, but until you finish setup Sentrix only alerts, and it needs a log channel to post those alerts in.

2. Quick setup

  1. Pick a log channel and an action

    /sentrix setup action:quarantine log_channel:#sentrix-log quarantine_role:@Quarantined

    Every option is optional, so you can run /sentrix setup again later to change just one thing. Sentrix checks its own permissions and warns you about anything missing.

  2. Choose categories (optional)

    /sentrix categories

    By default Sentrix acts on every category. Narrow it down if, for example, you only care about cheaters and raiders.

  3. Check members who are already here

    /scan apply_action:true

    Without apply_action, /scan only lists flagged members. With it, Sentrix applies your action to them too.

  4. Confirm

    /sentrix settings

    Shows your configuration and any warnings, such as a missing permission or a quarantine role Sentrix can't assign.

Actions

The action in /sentrix setup decides what happens when a flagged user joins, or is found by /scan apply_action:true. Every action except none also posts an alert in your log channel.

ActionWhat happensNeeds
alert defaultPost an alert in the log channel. Nothing else.A log channel
quarantineGive the user your quarantine role, then alert. Use this with a role that can only see a verification or holding channel.Manage Roles, and a quarantine_role below Sentrix's role
kickKick the user, then alert.Kick Members
banBan the user, then alert. Messages aren't deleted.Ban Members
noneTurn off join checks in this server.—

If the action is quarantine but no quarantine role is set, Sentrix falls back to alert so your moderators still hear about it.

When a user is flagged after they've joined, Sentrix applies your action straight away in every server they're in. You don't need to rescan.

If a user's flags are removed on appeal, Sentrix lifts the bans and quarantines it placed. Kicks can't be undone, but the user can rejoin.

Categories

Every flag has one category. /sentrix categories opens a menu where you choose which ones your server acts on; Watch all resets it. Flags in categories you don't watch are ignored in your server.

Cheating / cheat sellingLeaking Scamming / fraudRaiding Spam / advertising botHarassment NSFW / explicit contentImpersonation Malware / token grabbingOther

Whitelist

Trust someone who's flagged? Whitelisted users are never actioned in your server. Their flag still applies everywhere else.

/sentrix whitelist add user:@someone
/sentrix whitelist remove user:@someone
/sentrix whitelist list

/scan still lists whitelisted members, marked (whitelisted), but never acts on them.

Alerts & DMs

Alerts in your log channel show who was detected, which categories they're flagged for, when they were first flagged, and what Sentrix did. They never include reasons or evidence, which only Sentrix staff can see.

  • Ping a role on alerts: /sentrix setup alert_role:@Moderators. Stop pinging with remove_alert_role:true. The role must be mentionable, or Sentrix needs Mention @everyone, @here, and All Roles.
  • DM before kick or ban: on by default. Sentrix tells the user which server removed them, the categories, and how to appeal. Turn it off with /sentrix setup dm_users:false.
  • Report outcomes are also posted in your log channel once staff review them.

Who can use commands

Each command has a default permission requirement, listed in the command reference. To change who can use a command, go to Server Settings › Integrations › Sentrix, where you can allow or deny specific roles, members and channels.

Command reference

Options in [brackets] are optional. Unless noted, only you see Sentrix's reply.

Server setup Manage Server

/sentrix setup [action] [log_channel] [quarantine_role] [dm_users] [alert_role] [remove_alert_role]

Configure what Sentrix does when a flagged user is detected. Only the options you fill in change.

action
none, alert, quarantine, kick or ban. See Actions.
log_channel
Where alerts go. Sentrix needs Send Messages and Embed Links there.
quarantine_role
Role given by the quarantine action. Must be below Sentrix's role and not managed by another bot or integration.
dm_users
DM users before kicking or banning them (default: on).
alert_role
Role to ping on alerts.
remove_alert_role
Stop pinging a role.
/sentrix settings

Show the current configuration, whitelist size, and any permission warnings.

/sentrix categories

Choose which flag categories Sentrix acts on in this server.

/sentrix whitelist add user
/sentrix whitelist remove user
/sentrix whitelist list

Exempt users from Sentrix actions in this server. See Whitelist.

/scan [apply_action]

Check every current member against the Sentrix database. With apply_action:true, also apply your action to flagged members. Bots are skipped. Once every 10 minutes per server.

Moderation Moderate Members

/lookup user user
/lookup server server

Check whether a user or server is flagged, and for which categories. server accepts an invite link, a server ID, or the server's name. The result is posted in the channel.

Shortcut: right-click a member › Apps › Sentrix Lookup.

/flagged users [category]
/flagged servers [category]

A paged list of everyone flagged, with their categories and first-flag date. Filter by category if you like.

/report user user category reason [evidence] [screenshot]
/report server server category reason [evidence] [screenshot]

Send a user or server to Sentrix staff for review. See Reporting.

user / server
Who you're reporting. For servers, an invite link works best; a server ID or name also works.
category
What they did (one of the categories).
reason
What happened, 10–1000 characters.
evidence
Links: message links, screenshots, videos.
screenshot
An image file.

You must include evidence, a screenshot, or both. Up to 3 reports per 5 minutes per server.

Everyone Anyone, also in DMs

/checkself

Check whether your own account is flagged. Only you see the result. If you are flagged, it links you to the appeal page.

Reporting

Reports are how the database grows, and every one is reviewed by Sentrix staff before anything is flagged.

  1. A moderator runs /report user or /report server with a category, a reason and evidence.
  2. Sentrix staff review it. If they need more information, they may open a ticket and DM the reporter; reply to the bot's DM to answer.
  3. If it's approved, the user is flagged and every protected server they're in applies its action straight away. Staff may pick a more fitting category than the one reported.
  4. The outcome (approved or denied, plus any note from staff) is posted in your log channel.
Good evidence gets reviewed faster. Link the exact messages (right-click › Copy Message Link), add screenshots that show usernames and IDs, and explain the context in the reason.

Each server can have one pending report per target, and a limited number of pending reports in total, so please wait for staff to work through them.

Appeals

Anyone who thinks they were flagged by mistake can appeal at sentrix.gg/appeal by logging in with Discord. Sentrix links there in its DMs and in /checkself.

  • Staff choose which flags to remove. Once no active flags remain, Sentrix lifts the bans and quarantines it placed in every server.
  • One appeal can be pending at a time. The decision arrives as a DM from the bot.
  • Accounts on the Sentrix blacklist (several active flags, 3 by default) can't appeal.

If you're a moderator and trust someone before their appeal is decided, whitelist them in your server.

Troubleshooting

A flagged user joined and nothing happened
  • Is a log channel set? Without one, alert has nowhere to post. Run /sentrix settings.
  • Is the action none?
  • Is the user's category one you watch? Check /sentrix categories.
  • Is the user on your whitelist?
The alert says the action FAILED

Almost always a permission or role-order problem. Make sure Sentrix has the permission for your action (Manage Roles, Kick Members or Ban Members) and that its role is above the member's highest role and above the quarantine role. /sentrix settings lists missing permissions.

Quarantine isn't working

The quarantine role must be below Sentrix's highest role and can't be a role managed by another bot or integration. If the role was deleted, set a new one with /sentrix setup quarantine_role:.

Alerts don't ping anyone

Make the alert role mentionable (Server Settings › Roles › the role › Allow anyone to @mention this role), or give Sentrix Mention @everyone, @here, and All Roles.

Some commands don't show up

Commands are hidden from members without their default permission. Check Server Settings › Integrations › Sentrix to see or change who can use each one.

"This server already has a pending report on that user"

Your server's earlier report on them is still waiting for review. You'll see the outcome in your log channel.

Someone was flagged before Sentrix joined and they're already in my server

Join checks only run when someone joins. Run /scan apply_action:true once to handle existing members. After that, new flags are applied automatically.

Still stuck? Ask in the Sentrix Discord.