Dashboard tabs

The manage dashboard at gatorsys.xyz/manage is organised into a sidebar of tabs. Tabs tied to a module only appear once that module is enabled in Modules. Press Ctrl+K (or ⌘+K) anywhere in the dashboard to search across every tab and setting.

Server

Tab	What it configures
Overview	Server summary, enabled modules at a glance, and quick links into each section.
Customization	The bot's per-server identity and appearance.
Permissions	Role-based access for commands and dashboard sections.
Logging	The unified bot log channel, critical alerts channel, and verification logs.
Audit Log	A timeline of configuration and staff actions taken on your server.

Workspace

Tab	What it configures
Staff Panel	The staff roster: profiles, activity, and management actions in one table.
Departments	Department profiles, ranks, rosters, resources, waves, announcements, and each department's public page.

Staff modules

Tab	What it configures
Infractions	Infraction channels, the approval system, preset reasons, custom types, and the infraction message.
Promotions	Promotion channels, the promotion system (OG, single or multi hierarchy), cooldowns, approvals, and the promotion message.
Suspensions	Suspension channels and automatic expiry.
Leave of Absence	LOA channels, approvals, and templates.
Message Quota	Quota targets and leaderboard behaviour.
Activity	Staff reports combining shift time, message counts, quota progress, and active leave.
Shifts	On-duty and break roles, the shift log channel, how many people may be on at once, and the default quota.
Staff Feedback	Feedback collection for your staff team.
Training Academy	Training sessions, rosters, and grading.

Community modules

Tab	What it configures
Tickets	Ticket panels, subjects, transcripts, and the AI knowledge base.
Modmail	The modmail inbox channel and SLA reminders.
Suggestions	The suggestions channel and voting flow.
Daily Questions	The question pool and posting schedule.
Welcome	Welcome messages for new members.
Auto Response	Trigger phrases and their automatic replies.
Connection Roles	Roles granted from account connections.
Giveaways	Giveaway defaults.
Reminder	The reminder channel and schedule.
Partnerships	Partnership representatives and ad channels.

Integrations

Tab	What it configures
PRC	Your policeroleplay.community server key and monitoring.
Game Logs	Where ER:LC joins, leaves, kills, and in-game command use are posted.
Sessions	The session status panel, session channel, and role gates for session actions.
Roblox	Roblox account verification for your members.

Content

Tab	What it configures
Commands & Templates	Custom slash commands, message/embed templates, and the template marketplace.
Automations	Rules of the form "when this happens, do these things" — see below.
Resources	Department documents and spreadsheets: the built-in editors, sharing, and link access.
Packages	Package drafts, publishing, and claim logs.

Unsaved changes are guarded — if you navigate away with staged edits, the save bar flashes and the page shakes instead of dropping your work. Immediate actions (like roster moves) apply instantly and never stage.

Automations

An automation is one trigger, any number of guards, and up to ten ordered steps. Rules are built here and managed from Discord with /automation.

Triggers — a member joins or leaves, a staff shift starts or ends, an application is approved or rejected, a form is submitted, a ticket is closed, an infraction or promotion is issued, a leave starts or ends. There is also Run by hand only, for a rule you want to keep on the shelf and fire with /automation run.

Conditions decide whether a run happens at all. Two kinds: the member has (or does not have) a role, and a number about the run compared against a value — how many people are already on shift, how long the shift that just ended was. A rule with no conditions runs every time its trigger fires.

Conditions fail closed. If a condition names a role that has since been deleted, the automation stops rather than running unconditionally — the alternative is a rule that starts firing on everyone the day somebody tidies up their roles.

Steps run in order: give a role, take a role, DM the member, post in a channel, write to a log channel, set a nickname, close the member's open ticket, or wait a few seconds. Each step is attempted even if an earlier one failed — an automation is a list of independent effects, not a transaction, so a DM that bounces is not a reason to skip the role.

Cooldown is the shortest gap allowed between two runs of the same rule. Worth setting on anything that reacts to members joining: a rule with a DM step and no cooldown will try to DM every account in a raid.

The Recent runs list at the bottom shows what the automations actually did. A run with no effects recorded is usually a condition doing its job.

Reviewing an application

Submissions arrive under Resources → Responses, and in the department workspace for department applications. Two signals sit on each answer, and they are different kinds of claim:

Paste and typing are counted by the form while the answer is being written — how much text was typed, how much arrived in a paste, and how long the field was focused. It is a measurement, it travels with every submission, and it says nothing about who wrote the text. Someone drafting in Notes and pasting it in is doing nothing wrong.

AI detection is a judgement, made afterwards, and only when you ask for it. Press Check for AI on a submission you are reading and every long text answer is scored — by an offline check that looks at the shape of the writing, and by the model, with the stronger of the two signals winning. The result is stored on the submission, so reopening it shows the same flags without scanning again.

Both render on the question they describe: a tag beside it, and a note under the answer explaining what was found. An answer that was typed and reads as written shows nothing at all.

Neither signal decides anything. Nothing downstream reads them, they never reach the applicant, and a flag is a reason to read an answer closely — not evidence. Formal writing is not proof of anything, and plenty of applicants write well.