CONTROL · MANAGE · AUTOMATE
The control center for your Sentinel bot.
Sign in with your Discord account to manage the Sentinel bot.
Login with Discord →SERVERS
SERVERS:
LIVE BOT STATE
EXISTING /PURGE COMMAND
Uses the existing bot purge action and Discord permissions.
EXISTING /SEND COMMAND
EXISTING /TEMPLATE COMMAND
Create a reusable message template to quickly send messages to your server.
SUPPORT DESK
Tickets created from your Discord panels will appear here.
Choose a ticket from the list to read its conversation and manage it.
TICKET PANELS
Create your first ticket panel so members can open support tickets.
RULES ENGINE
Automations run actions when ticket events happen.
Choose a rule from the list, or create a new one to get started.
PERFORMANCE
Analytics appear once tickets start coming in.
LIVE QUEUE
Status boards show live ticket queue depth in Discord channels.
Choose a board from the list, or create a new one to get started.
BLOCKED MEMBERS
Nobody is blocked from opening tickets in this server.
AUDIT TRAIL
Ticket actions taken in Discord and on this dashboard are recorded here.
REAL PROJECT CONFIGURATION
TEMPLATE
Create a reusable message template for the selected server.
Optional Discord embed cards for this template.
TICKET PANEL
Offer another panel of this server on the same message. A member who picks one opens a ticket on that panel, under that panel's own hours, form and rules.
Placeholders: {user} {number} {panel} {guild}.
What each group may do inside a ticket. “Inherited” states nothing: the category and the members' server roles decide that permission.
The people who run tickets rather than answer them. This group has its own lane below, separate from the support roles.
Tickets created from now on are built with these choices. A ticket that already exists keeps the permissions it was created with until you press “Update permissions” on that ticket. Private threads take no per-channel permissions from Discord, so on a thread ticket these choices decide who is on it, not what each person may do inside it.
What the ticket shows the moment it opens. The opening text below is always part of it — these embeds go above Sentinel's own ticket header.
Placeholders substitute when the ticket opens: {user} the member, {number} the ticket number, {panel} the panel name. Support roles are the "Ping on ticket open" list on the Roles tab.
A welcome message cannot carry its own buttons: a control the bot could not answer after a restart would sit in the ticket doing nothing. The buttons inside a ticket are configured on the Advanced tab, and those are the ones Sentinel really builds.
Member-facing messages. Placeholders such as {user}, {actor}, {number} are replaced when the message is sent.
Discord asks at most 5 questions in one form. The Add button stops at 5; a form that already stores more keeps every question and marks the ones Discord will not ask.
Members with these roles can see, claim and answer this panel's tickets.
Roles whose holders are treated as this panel's team, without being added to the Support roles list: they get working access to every ticket it opens, are kept on the channel when claims change access, and make the support permission lane apply to somebody. Nothing here is granted to the member who opened the ticket.
Roles mentioned when a new ticket is opened.
Given to an agent while they hold a claim and taken back when they release or close it.
The message count limits what Sentinel keeps for the record, not what Discord shows: once a ticket's creator has sent that many messages, further ones are left out of the ticket's transcript while the channel itself carries on as normal. Staff are never counted.
Checked on the server every time a ticket is opened. Blocked roles take precedence over required roles.
Members with a bypass role skip role, age and membership checks.
Windows are read in the timezone above, so “09:00 to 17:00” means 9am at the desk, not 9am UTC. A window whose end is earlier than its start runs overnight.
Opens, claims, closes, moves and other lifecycle events go to the log channel above. Turning this on posts them inside the ticket too, and works on its own when no log channel is chosen. Transcripts and private notes are never copied into the ticket.
Off, a transcript keeps the conversation and names nothing that was attached to it; each message that had a file says so, so a reader can tell the difference between an empty message and a withheld one. Discord's own channel is untouched either way.
Offered to the member who opened the ticket when it closes - as a direct message where they accept them, otherwise in the ticket. Turning this off stops the offer; ratings already given stay in analytics either way.
Members see these answers when they press Open Ticket and can still continue to a ticket. Up to 25 entries.
When the main category is full, tickets are created in the next available category (up to 5).
These are the buttons on the ticket message itself. What is set here is what the bot builds — a button switched off is not created, and its name, picture and colour are the ones a member sees and presses.
Every ticket also carries Lock and Unlock on its first row, and the priority menu underneath, whatever these four say.
PUBLISH TO DISCORD
PANEL HISTORY