Staff sign-in
Use the Discord account that manages your server or holds a configured staff role.
Connect your account
I'll check your permissions after you connect.
Discord OAuth
Sign in with the same Discord account you use in your server.
Permissions refresh
If your roles changed recently, log out and sign in again.
Staff dashboard at a glance
Built for moderation teams managing 3698 Bot servers.
7 modules
Overview, records, polls, calendar, settings, and logs in one place.
Role-based access
Admin, Moderator, LabRat beta testers, and view-only Kingdom Member each see what they need.
Audit trail
Dashboard sign-ins, edits, and Discord mod activity stay traceable.
Staff sign-in
Use the Discord account that manages your server or holds a configured staff role.
Connect your account
I'll check your permissions after you connect.
Discord OAuth
Sign in with the same Discord account you use in your server.
Permissions refresh
If your roles changed recently, log out and sign in again.
3698 Bot
Who can log in?
Only server staff get in. You need the bot in your server plus one of the access levels below.
| Access | How you get it | Dashboard powers |
|---|---|---|
| Admin | Discord server owner or Manage Server permission | Full edit, settings, logs, polls |
| Officier R4 | R4 Officer, Council, or BotPerms (configured per server in Settings) | Edit title bans & fort offenses, polls, view settings |
| LabRat | Beta-testing role assigned by an admin in Settings | Same Moderator edit access while testing new dashboard features |
| Kingdom Member | Kingdom Member role only. A separate view-only role your admin picks in Settings | View overview, search, title bans, fort offenses, polls, and calendar (no editing). Calendar shows synced events only. |
LabRat is a beta-testing role with Moderator powers, not view-only Kingdom Member. R4 Officer and Council are standard Moderator access. Kingdom Member is for helpers who only need to read records. Regular members without these roles can sign in but will not see any servers. Ask an admin to assign the correct role, then log out and sign in again.
Getting started for admins
Three steps to onboard your moderation team.
- 1
Invite the bot
Add the 3698 bot to your Discord server so the dashboard can read roles, forums, and logs.
- 2
Configure access in Settings
As an admin, open Dashboard → Settings and set the Kingdom Member role, mod log channel, and forum channels.
- 3
Assign roles & re-login
Give staff their Discord roles, then have them log out and sign in again so OAuth picks up the changes.
3698 Bot
Once those three steps are done, your moderation team can sign in and start using the dashboard.
Why staff use this
Less Discord scrolling, more moderation work done from one dashboard.
Fort offenses & title bans
Review records without digging through Discord threads or forum scrollback.
Audit trail
Track who signed into the dashboard and what changed across moderation actions.
Settings hub
Configure bot roles, forums, webhooks, and channels from one settings panel.
Polls & mod activity
Launch polls and monitor mod activity without switching between Discord tabs.
3698 Bot
Your team gets one place to run the server: fewer tabs, faster responses, cleaner records.
Dashboard modules
Everything your staff can manage from the browser. Hover a module to preview, click to open.
Overview
Server stats, health, audit trail, and recent Discord activity.
Title Bans
Forum records, offenses, edits, and case timelines.
Fort Offenses
Search, edit, and mark fort offenses as active or removed.
Polls
Create timed polls in server text channels.
Calendar
View synced iCal events plus recurring manual entries.
Settings
Roles, forums, mod log, anti-spam, and notification webhooks.
Logs
Dashboard sign-ins, edits, and Discord mod log entries.


