> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lsreality.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dispatch console

> Sign in, monitor channels, transmit, and use the LSR Radio dispatch workspace.

Use the dispatch console in your browser or the [desktop app](https://docs.lsreality.com/desktop-app.md).
Both use the same console interface; available actions depend on your permissions.

## Sign in and check your identity

1. Open the console address supplied by your staff.
2. Select **Sign in with Discord** and use the Discord account authorized by staff.
3. Check the operator name at the top right before starting your shift.

There is no self-registration or password fallback. Access is tied to your exact Discord ID, not just your Discord display name.
If sign-in fails, you used the wrong account, or an expected permission is missing, contact staff with the error shown and the Discord account you used.
Changing your console display name does not authorize a different Discord account.

Open **Edit → Preferences…** to change **Display name**, hide yourself from radio channel member lists, or adjust **TMS notification volume**.
Choose a callsign-style name such as `DSP1 - Central` if you need TMS replies, then select **Save preferences**.
Use **File → Sign out** when finished, especially on a shared workstation.

## Read channel tiles

Choose a zone tab, then click a channel name to select it and expand its inline details.
The details show affiliated units and channel controls; selecting a channel alone does not make it your transmit destination.

| Indicator | Meaning | Control |
| - | - | - |
| **MON** | You are monitoring this channel. | Speaker button. |
| **PRI** | This is your primary channel, used as the general-PTT fallback. | Star button or **Edit → Set as primary**. |
| **TX** tag | This channel belongs to your general transmit group. | **TX** button. |
| Live **RX** / **TX** | Receive or transmit activity, rather than group membership alone. | Watch the live indicator. |

Setting a primary channel also selects it and enables monitoring for it.
TX-group membership is separate from monitoring and primary selection; adding a channel to TX does not turn its speaker on.
The primary star is also separate from the **Priority** menu's channel/zone priority controls.

## Monitor and transmit

* Use a tile's speaker button or **Radio → Monitor selected** to toggle listening.
* **Radio → Monitor visible zones** adds the channels in the currently visible zone tabs.
* **Radio → Stop all monitors** clears your listening selection.
* Expanded details include a speaker control and volume slider.

For general PTT, add up to **8 channels** using their **TX** buttons.
Hold **TX group / PTT** or your **General transmit (hold)** shortcut, then release to stop.
When the TX group is nonempty, general PTT targets that group, not every monitored channel and not an extra primary channel.
With an empty group, it targets your primary channel; if no primary is set, it falls back to the selected channel.
The large transmit control in expanded channel details also uses general-PTT routing.

To talk to just one channel, hold its tile's lightning-bolt button, labeled **Hold to transmit on this channel only**.
This bypasses your TX-group selection for that press without changing the group.
[Channel PTT shortcuts](https://docs.lsreality.com/dispatch-keybindings.md) provide the same single-channel targeting.
Only one PTT can be active at a time; release before changing destinations.

Allow microphone access when prompted and check the status bar for **PTT failed** messages.
A busy or unavailable member can prevent a TX-group transmission; do not assume every press was accepted.
A single-channel target still follows any active system patch routing and normal access checks.

## Choose a layout

Use the top layout selector or **File → Open layout** to switch workspaces.
Open **Edit layout** or **File → Edit layout…** to name the layout and choose its channel folders.
Use **Add folder**, adjust folder names/colors and channel selections, then select **Save layout**.
**Save as new** saves a separate layout; **File → New layout…** starts the new-layout workflow.
Layout channels come from the live radio system: a layout is not a way to create channels or gain access.
If saving or deleting is unavailable or denied, ask staff rather than assuming the layout is private to your browser.

## Panic, messages, and unit actions

For authorized operators, **Panic** / **Radio → Send panic** acts on the selected channel, falling back to primary if none is selected.
Use **Clear panic** to return that channel to normal traffic. These are operational alerts, not test sounds.

Open **Radio → Text messages (TMS)**, enter **To radio callsign** and **Message**, then select **Send message**.
Use **Important** or **Request reply** when appropriate; opening a thread marks it read locally, while a reply is a separate message.
Select the recipient's conversation and inspect the outgoing message's delivery status. For an unresolved send, use **Retry original send** or deliberately choose **Start new send (may duplicate)**; the dispatch console has no separate Sent folder.
Expanded unit details also offer **Actions… → Send TMS** when a callsign is available.

**Actions… → Move to channel…** requires **Dispatch console** and **Dispatch admin** permissions, or developer access, and an eligible powered, affiliated, uninhibited radio.
Choose **Destination zone / channel**, select **Move radio**, and wait for the result.
The player's radio state, codeplug, coverage, and receive permissions still apply; success confirms server affiliation, not client audio.
Closing the dialog does not cancel an already submitted move.

## Manage patches carefully

A patch is a system-wide routing action, not your personal TX group or monitor selection.
If authorized, select **Add patch** in the **Patch** pane, choose **2–5 distinct named channels**, and select **Add group**.
Channels cannot belong to overlapping new groups; remove the existing group before regrouping its members.
Patching routes traffic between group members but does not turn them into one shared busy/transmit lock.
Use the group's **Remove** button to remove that exact group and wait for confirmation.
If removal is staged, follow **Stage removal** and **Apply removals**; a staged selection alone changes nothing.

## Dispatch administration and shift checks

Dispatch admins can open **File → Manage dispatch users…** to manage dispatch accounts and grant **Dispatch console** or **Dispatch admin** access.
Dispatch admin includes console access, but this menu cannot grant main-admin access or other non-dispatch permissions, or manage main-admin accounts.
Staff may also use the shared **Users** directory in the main admin panel; dispatch-user access alone does not open that panel.
Account edits can end affected sessions immediately; sign in again if staff changes your access.

Use **View → Activity & patch pane** to show the activity log, patches, and **Connected dispatchers**.
Dispatcher presence reflects recent console contact, not proof that a microphone or voice connection is ready.
See [keyboard shortcuts](https://docs.lsreality.com/dispatch-keybindings.md), [recordings](https://docs.lsreality.com/recordings.md), or [troubleshooting](https://docs.lsreality.com/troubleshooting.md) for the next step.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.