The Operator Dashboard

A tour of what you manage in the web dashboard — players, the world, snapshots, mods, and the live map.

The dashboard is where you run your server day to day. The CLI handles the host (deploy, update, restart); everything about the running game lives here. Open it any time with:

beacon admin

The privilege boundary

The dashboard is intentionally unprivileged — it never holds the Docker socket or RCON-write directly. Every privileged action is brokered through the admin-rpc backend with role checks and an audit trail. That's the same boundary that lets you safely expose the dashboard over Tailscale or a custom domain.

Players & access

Players — your members and their roles. Beacon is the access manager: it maintains the Minecraft allowlist over RCON from this page. Adding or removing someone here updates who can actually join.
Invites — generate invite codes so new players can join through a guided flow, with auto-approve or manual review.
Atlas join policy — when your beacon is listed, choose Gated for invite/review access or Open for public Minecraft-login access that auto-approves verified players. Open is a public access change, not a cosmetic listing label.
Audit log — who did what, and when, for every privileged action.

The world

Worlds — manage worlds and their generation settings (seed, level type, structures).
Snapshots — on-demand and scheduled snapshots with scoped restore. See Backups & Restore.

The server

Console — watch server output and issue commands.
Status — lifecycle state, recent operations, and activity (joins, leaves, deaths, chat) over time.
Settings — difficulty, game mode, PVP, MOTD, view distance, and the rest of server.properties, generated by Beacon from your choices. Also home to in-game chat commands (!wp, !help, and custom operator commands). Allowlist enforcement is always on — see Configuration.
Mods — server-side plugins/mods, plus the client packs players install; client add-on mods fold into every play path automatically.
Loadouts — save and apply named sets of mods/plugins.
Voice — proximity voice chat: one toggle plus the server-side voice settings.
Security — the hardening console: secure-by-default checks and access controls at a glance.
Performance — TPS, memory, and chunk metrics to spot load problems.
Updates — check for and apply new Beacon releases. See Updating Beacon.

The live map

Map embeds a live 3D map of your world, rendered by Vantage and updated as the world changes. It works with any loader and Minecraft version — there's no in-game plugin to install.

Publishing to the Atlas

Atlas is where you optionally list your beacon in the public directory at beacon-mc.io. Listing is opt-in and configured entirely here. The profile editor also owns the Join policy: gated listings use the beacon's normal invite/review path, while open listings let any verified Minecraft login become approved. The dashboard highlights Open mode and requires an explicit acknowledgement before switching from gated to public access. See Publish to the Atlas and Privacy & heartbeats.

What's not in the dashboard

Host-level operations — deploy, upgrade, restart, logs, status — live in the CLI, not the dashboard. The two are complementary: the CLI owns the box, the dashboard owns the game.