DispatchX logo DispatchX Docs
Set up Manage first, then test each dashboard with one staff member.
Overview / Dashboards and Operations

Dashboards And Daily Operations

This guide explains what each dashboard is for and how to get it ready for a real patrol session. Start in Manage, then test Dispatch, LEO, FD, EMS, and CIV with one staff member before opening it to everyone.

Server Selector

Use the Servers page first so every dashboard knows which workspace to load. The selected server controls calls, departments, ERLC data, settings, profiles, and premium state.

  • If the wrong server opens, go back to Servers and select the correct community.
  • If no servers appear, confirm DispatchX is invited and your Discord account has access.
  • If a page stays on Loading, refresh once after selecting the server.
Open Server Selector

Manage Dashboard

1

ERLC Integration

Paste the private server key so DispatchX can read live players, vehicles, teams, plates, and map data.

2

Discord Integration

Save the employee role, on-duty role, shift log channel, call log channel, and scene/citation log channel IDs.

3

Departments

Create or enable the departments your community will use: Dispatch, LEO, FD, EMS, and CIV.

4

Linked Departments

Use linked department codes only when separate Discord servers need to share one main server's calls and ERLC data.

When the main server ERLC API key is saved, linked department servers inherit it automatically. A linked LEO department and a linked Dispatch department connected to the same main server share calls, live map data, lookup data, and dispatch unit visibility while each linked department keeps its own shift time totals.

Open Manage Dashboard

Roster

The roster is where server managers connect Discord users to department callsigns. It is especially important for linked departments because roster membership controls whether a member sees the Dashboard button for that linked department.

  • Open Servers, choose a server you can manage, then open the Roster page from Manage or the server tools.
  • Add each member with their Discord User ID, department, callsign, unit, Discord username, and roleplay name.
  • Use the roster search bar to find members quickly by name, callsign, department, unit, or Discord ID.
  • Roster cards can be expanded when editing and collapsed when you want a compact list.
  • Save the roster after adding or editing members.

For linked departments, DispatchX checks the signed-in user's Discord ID against the roster. If the user is listed, the linked department Dashboard button appears and their saved roster callsign loads automatically. If the user is not listed, the Dashboard button stays hidden even if they can see the server.

Main servers are management hubs. They do not show a department Dashboard button; members open dashboards from the linked department server where their roster entry applies.

Dispatch Dashboard

  • Create, edit, assign, and close active incidents from the dispatch board.
  • Use Assign Units to attach active LEO units to a call.
  • Use Lookup to search current players by player, callsign, team, postal, or plate.
  • Use the live ERLC map to view active on-shift units and call markers.

Dispatch unit visibility depends on LEO members starting a shift, having a linked Roblox account, and being present in the ERLC server. Unit statuses such as Available, Busy, Enroute, and On Scene update from the LEO dashboard and appear on the dispatch board.

For a real test, have one officer start shift, create one call in Dispatch, assign the officer, then have the officer change status to Enroute and On Scene.

LEO Dashboard

  • Start Shift begins duty tracking and makes the officer available to linked dispatch dashboards.
  • End Shift stops duty tracking and removes the officer from active dispatch units.
  • The shift timer shows the current tracked shift duration.
  • When opened from a linked department, the dashboard loads the user's callsign from the roster automatically.
  • Availability buttons update the officer state shown to dispatch: Available, Busy, Unavailable, Enroute, and On Scene.
  • The call panel shows assigned call origin, status, priority, address, postal, title, description, and attached units.
  • The ERLC map shows the officer and the assigned call location when live ERLC data is available.

FD And EMS Dashboards

FD and EMS use the same operations pattern as LEO, but for fire and medical response. They should be enabled as departments from Manage before members try to open them.

  1. Enable or create FD and EMS departments from Manage.
  2. Make sure the members have the employee role or the department access role your server uses.
  3. Have responders start a shift so dispatch can see them as available units.
  4. Create a fire or medical call from Dispatch and assign the responder.
  5. Confirm their status updates appear on the dispatch board.
Lookup is only available from the LEO dashboard. FD and EMS responders use their dashboard for shift, status, and assigned response work.

CIV Profile Dashboard

The Profile page is where civilian users save the information that appears when LEO clicks Profile from a lookup result. The Profile button opens the saved civilian record in a popup so officers can review it without leaving lookup.

Users can also relink their Roblox account from the Profile page if they need to switch to a different Roblox account. Relinking sends them through Roblox verification again and returns them to the profile page when complete.

Profile FieldShows In Lookup?Notes
Name, DOB, age, sexYesUsed as the core civilian identity.
Residence, ZIP, occupationYesHelpful for roleplay context and dispatch notes.
Height, weight, skin, hair, eyesYesUsed for descriptions during stops and reports.
Photo uploadYesUploads a saved image instead of requiring a photo URL.

Scene And Citation Logs

Scene and citation logs can be created from Discord or from the LEO dashboard. Each log supports a type, notes, and an optional image upload.

  • Slash command: /log with Citation or Scene, notes, and an optional uploadable image.
  • Prefix command: use the log command from Discord to submit scene or citation notes.
  • LEO dashboard: open Log, choose Citation or Scene, add notes, optionally upload an image, then save.
  • Discord delivery: set the Scene & Citation Logs Channel ID in Discord Integration.

LEO Lookup

LEO Lookup searches live ERLC player and vehicle data without showing player location. Results include player identity, team, vehicles, plates, recent activity, linked civilian profile details, and whether a user or vehicle has an active BOLO.

  • Search by player name, callsign, team, postal, or plate.
  • BOLO state appears directly in the lookup result as BOLO or CLEAR.
  • Vehicle rows also state whether the vehicle has a BOLO.
  • If a matching civilian profile exists, use Profile to open it in a popup without leaving lookup.

Shift Admin

Use /shift admin from Discord when command staff need to review or correct member shift records.

  • Use Set Shift Time to manually set a member's tracked shift total.
  • Use Remove Time to subtract an incorrect amount from a member's tracked shift total.
  • Accepted time examples include 2h 30m, 1:45, or 2.5.
  • Shift changes should be used for corrections, not routine clock-in or clock-out activity.

Linked Departments

Linked departments let communities split LEO and Dispatch into separate Discord servers while sharing the same main server data. Once linked, the main server acts as the shared operational scope.

  • Main server settings carry ERLC API access to linked department servers.
  • Linked LEO, FD, EMS, and DOT active units appear on linked Dispatch unit lists after starting shift.
  • Shift time is tracked separately per linked department instead of as one shared main-server total.
  • Roster membership controls linked department dashboard access and automatic callsign loading.
  • Linked Dispatch assignments appear on the LEO assigned-call panel.
  • Live map and lookup endpoints resolve through the shared main server.