-
Turn the service on. On the dashboard, open your server's Services page and switch on the Moderation card. Until it is on, every moderation command answers "Sentinel is not enabled for this server." and the automod does nothing. The first time a server turns it on, Sentinel also switches on anti-nuke with quarantine, restore and the hold, so list the admins you trust as exempt on the Anti-nuke page before anyone tidies up channels or roles in bulk.
-
Open Sentinel. Until it is set up, Home says "Sentinel is not set up yet" with a Run setup button; later, the Setup card on the Settings page has "Run setup again". Only dashboard managers of the server can run it; the Setup page tells anyone else that the Manage Server permission is needed. The "What setup does" list on that page is the plan for the run.
-
Wait for the Readiness check. It confirms "The bot is in this server", "It can create the log channels (Manage Channels)" and "It can create the Quarantined role (Manage Roles)", then says "Ready to run setup." Grant the bot any permission marked No before you continue, or the run stops at that step.
-
Choose how strict: Relaxed (spam and known scam links), Standard (preselected, balanced protection for most communities) or Strict (for servers that get raided or targeted). Leave "Act right away" off. The new filters then start in Testing: the bot notes in the mod log what each filter would have done without touching anyone, so you can check them before they act. Home's How strict dial can switch the level later.
-
Click Run setup and confirm. In order, setup: checks what already exists; reuses a category with "mod" in its name or creates a private "Moderation" category; creates #sentinel-logs and makes it the moderation log channel; creates a "Quarantined" role with no permissions and denies it sending messages, reacting and using threads in every text, announcement and forum channel; detects moderator roles (roles named with mod, admin, staff or moderator that hold Kick Members, Ban Members or Manage Messages); saves those settings; creates #message-log and #server-log, points the message log and the server logs at them and turns them on; turns on the recommended protection (anti-nuke with quarantine, restore and the hold, the bot-add rule, escalating timeouts and the message log); adds the filter packs of your level; and posts a "Sentinel Moderation Active" card in #sentinel-logs.
-
Read the result page. Under What happened, every step shows Done, Skipped or Failed with its reason. An error is almost always a missing bot permission; fix it and run setup again. Steps that succeeded are not repeated, and channels or roles that already exist are reused.
-
Open Settings and check Your team. If setup found no moderator roles, add them here: until you do, only Administrators can run the staff commands. Confirm the mod log channel and the quarantine role. Under Moderator commands, set a default timeout if you want /timeout to work with the duration left empty, and decide whether to hide which moderator acted and whether to ask before bans, kicks and timeouts.
-
Try it. Run /warn on a test account with a reason. You should see "Warning issued to @member. Case #1", the test account should receive the warn DM, and a "Warning Issued" card should appear in #sentinel-logs. Run /history on the same account to see the case and the warning count.
-
Confirm on the dashboard. History lists case #1 under Cases, and Home shows your shields with Lock down at the top. Once the filters have run in Testing for a while and their notes look right, open Spam & scams and switch it from Testing to On: every filter then acts. To keep one filter testing, open it and turn on "Test this filter on its own".
If the Setup page also shows "Or describe your server", you can describe your community and how strict you want moderation, preview the filters drafted for you and apply them instead of a level.