Documentation
Set up Sentinel.
Installation, permissions, configuration and troubleshooting, all based on what the bot’s source code actually does.
Installation & invitation
The bot’s public invitation link is not configured on this website. The bot code does not contain its application ID, so a valid link cannot be built here. Ask in the support server for the current link. Site owner: see assets/js/config.js.
- You need the Manage Server permission on the server you want to add Sentinel to.
- Open the official invitation link only from this site or the support server, and check that it asks for the scopes
botandapplications.commands. - Choose your server, review the permissions and authorise.
- In Server Settings → Roles, drag the Sentinel role above the roles it must manage and below your staff roles.
- Run
/utility help, then follow the configuration section below.
Privileged intents
The bot requests the Server Members, Message Content and Presence intents (used for welcome events, AutoMod, leveling and status-based roles). They must be enabled for the application in the Discord Developer Portal, and Discord requires approval of privileged intents once a bot is in 100 or more servers. This matters to the bot operator, not to server administrators.
Permissions
Sentinel works best with the permissions its features use. The simplest option is Administrator; to follow least privilege, grant only what the modules you enable need:
| Feature | Discord permissions |
|---|---|
| Moderation | Ban Members, Kick Members, Moderate Members, Manage Messages, Manage Roles, Manage Nicknames, Manage Channels |
| AutoMod | Manage Messages (delete), Moderate Members (timeout), Kick/Ban Members, Manage Roles (quarantine), Manage Channels (lockdown) |
| AntiNuke | View Audit Log, Ban/Kick Members, Manage Roles, Manage Channels, Manage Webhooks |
| Verification / roles | Manage Roles, Manage Channels |
| Tickets / TempVoice / Honeypot | Manage Channels, Manage Messages |
| Music | Connect, Speak, View Channel |
| Everywhere | View Channel, Send Messages, Embed Links, Attach Files, Use Application Commands |
This table is derived from the permission checks and actions found in the code; it is guidance, not an official minimum. The default invite permission value in config.js is a placeholder for the site owner to review.
Who can run what
Many admin commands declare a required member permission (usually Manage Server). It is shown as a “Requires” badge in the command directory. Server owners can further restrict commands in Server Settings → Integrations.
Configuration
Sentinel is configured from inside Discord. Start with /panelsetup for the configuration dashboard, then set up the modules you need:
- Security first:
/verify setup,/automod setup,/antinuke setup. - Welcome:
/welcome setup. - Support:
/ticket setup, then/ticket diagnose. - Community:
/levelset settings,/economy panel,/tempvoice setup. - Test in a private channel before announcing changes (
/automod test,/flow test).
The command prefix defaults to ! for the commands that also work as prefix commands.
Module guides
Each feature has a description, getting-started commands and requirements on the Features page:
- Moderation —
/moderation - AutoMod —
/automod - AntiNuke —
/antinuke - Verification —
/verify - Tickets —
/ticket - Music —
/music - TempVoice —
/tempvoice - Economy —
/economy - Flow —
/flow - Backups —
/backup
Command examples
Syntax as defined in the code. <name> is required and [name] optional; Discord shows each argument as you type.
/moderation ban <member> [reason]/moderation warn <member> [reason]/moderation clear <amount>/automod test <text>/giveaway create [channel] [prize] [duration] [winners]/music play <query>/utility remind set <duration> <message> [destination]/economy pay <member> <amount>/levelset reward add <level> <role>/notify add <platform> <account> <channel> [role] [message] [style] [proxy]/flow test <workflow_id>/backup create [name]
Troubleshooting
Slash commands do not appear
Check the bot was added with the applications.commands scope, that you have the “Use Application Commands” permission in the channel, and wait a little: the bot registers its commands globally when it starts.
“Missing permissions” or the bot cannot act on someone
Compare the command’s “Requires” badge with your permissions, and make sure the Sentinel role sits above the target role or member in the role list.
Music does not play
Music needs a reachable Lavalink node. Administrators can run /music admin status, /music admin nodes and /music admin diagnostics. Make sure the bot can Connect and Speak in your voice channel.
AutoMod does not react
Run /automod status and /automod diagnostics. Check whether the module is in monitor mode (it only logs), whether the member, role or channel is exempt, and whether the Message Content intent is enabled for the bot.
Tickets, verification or notifications misbehave
Use /ticket diagnose, /verify config and /notify status to see the current configuration and errors. Social notifications depend on external platforms that can throttle or block requests.
Still stuck? Contact support.
FAQ
Is there a premium plan?
No premium system exists in the code. See the Premium page.
Is there a web dashboard?
Not yet. Configuration happens in Discord through interactive panels; see the Dashboard page.
Which languages does the bot support?
The code supports English and French for its language setting, and the ticket system ships with both languages. Many other messages are in English only.
What data does the bot store?
See the Privacy Policy draft for the categories identified in the code.