Server Panels
Learn what each server panel does and what controls its availability.
How panel visibility works
A panel appears only when:
- the connected server supports the required feature
- your role and server access allow you to use it
- your current plan includes the panel
The server entry page is Overview. Direct panel routes open the requested panel; an invalid panel identifier falls back to Console.
Panel reference
| Panel | Appears when | Purpose |
|---|---|---|
Info | Always available as the base panel | Runtime identity, environment details, host metadata, and diagnostics. |
Statistics | System metrics are available | TPS, memory, CPU, and other runtime or host metrics. |
Players | Player capability is available | Live player list and player-scoped actions. |
Console | Minecraft console capability is available | Live logs and command execution. |
Events | Event-stream capability is available | Structured live server events. |
Files | Filesystem capability is available | Browse and edit files. |
Shell | Terminal capability is available and the plan includes host terminal access | Interactive host shell sessions. |
Processes | Process capability is available | Inspect and control local processes. |
Services | Service capability is available | Inspect and control local services. |
Users | User capability is available | Inspect local system users. |
Docker | Docker capability is available and the plan includes Docker management | Docker containers, images, volumes, networks, Compose projects, Swarm resources, daemon details, and events. |
Podman | Podman capability is available and the plan includes Podman management | Native Libpod containers, pods, images, volumes, networks, events, exec sessions, and system information. |
Kubernetes | Kubernetes capability is available and the plan includes Kubernetes management | Kubernetes resources, CRDs, custom resources, rollout status, metrics, YAML actions, pod logs, exec, port forwarding, debug containers, and diagnostics. |
Databases | Database capability is available and the plan includes database management | Configured database sources and database browsing. |
Plugins | Plugin capability is available | Installed plugins, linking, updates, and related plugin metadata. |
Automations | A server workspace is available | Automation definitions and run history. |
Verification | Player-verification capability is available | Hosted verification challenge history and risk signals. |
Permissions | LuckPerms capability is available and the plan includes the permissions editor | LuckPerms groups, nodes, tracks, and editor operations. |
EssentialsX | EssentialsX capability is available | Player utility state such as homes, warp, jail, mute, or AFK data. |
Chunky | Chunky capability is available | Pregeneration status and Chunky controls. |
Factions | FactionsUUID capability is available | Faction, player, and land lookups. |
Audience | Player analytics capability is available | Audience and player-activity analytics. |
Practical notes
- Host panels do not appear on every Minecraft server.
- A plugin panel requires an active plugin on the target.
- Team members can see different panels because they can have different server access.
- Plan features also control panels for the whole organization.
- Some container features require tools on the agent host.
- For example, Kubernetes YAML comparison is native. Metrics require the metrics API; Helm needs its CLI and maintenance actions can require kubectl.
Related pages
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on