> ## 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 keybindings

> Customize console shortcuts and single-channel hold-to-talk keys, including desktop background PTT.

Open **Help → Keyboard shortcuts** in the [dispatch console](https://docs.lsreality.com/dispatch-console.md).
The dialog is titled **Keyboard shortcuts · this browser** or **Keyboard shortcuts · desktop app**.
These are dispatch-console shortcuts, not in-game radio keybindings.

## Edit a general shortcut

1. Find the action and select **Edit**.
2. Press the key or combination you want, including any Ctrl, Alt, or Shift modifiers.
3. Read the status message to confirm it was saved or resolve a conflict.
4. Select **Close** before trying the shortcut.

Capture uses physical key positions, so the printed character can differ on another keyboard layout.
No transmission occurs while the shortcut dialog is open, including while capturing a PTT key.
**Cancel capture** or Escape cancels capture; Escape again closes the dialog.
Tab cancels capture and keeps normal focus navigation within the dialog.

Use **Clear** to leave a general action unbound, or **Default** to restore that action's original key.
**Reset all defaults** restores general shortcuts **and removes all Channel PTT assignments**.
There is no separate Save button: accepted changes are applied and saved immediately.
If storage is unavailable, the status warns that changes apply only to the current page and will not survive a reload.

## Useful defaults

These are defaults, not a guarantee of your current assignments. The editor and menu labels reflect your saved keys.

| Action | Default |
| - | - |
| General transmit (hold) | Space |
| Open selected resource | Enter |
| Toggle selected speaker | Ctrl+L |
| Set selected as primary | Ctrl+1 |
| Add / manage patch groups | Ctrl+P |
| Save layout | Ctrl+S |
| Refresh | F5 |
| Full screen | F11 |

Next/previous visible channel, TX-group toggle/clear, TMS, preferences, and close-resource-details actions start **Unbound**.
Assign them in this same editor if you want keyboard access.
Operational actions still require the appropriate permissions and channel selection.

## Function keys and conflicts

**F1–F24** are supported, including Ctrl/Alt/Shift combinations.
Before assigning F5 elsewhere, clear or rebind **Refresh**; do the same for **Full screen** before reusing F11.
A key cannot be assigned to two general actions, two channels, or both a general action and a channel.
Clear, remove, or change the existing assignment first, then retry capture.

Reserved combinations such as **Alt+F4** are rejected.
Escape and Tab remain navigation/cancel keys; Meta/Command, AltGraph, and text-composition input are not supported for capture.
On laptops, use Fn or Fn Lock if needed to send a function key instead of a media key.
Acceptance in the editor does not override the operating system: a browser, OS, or other app can intercept a key before the console receives it.

## Assign Channel PTT

Use **Channel PTT** in the lower part of **Help → Keyboard shortcuts**.

1. Choose the destination from the **Channel** selector; check its name and TG number.
2. Select **Assign key…**, then press your hold-to-talk key or combination.
3. Check that the channel row and its key appear without an error.
4. Close the dialog, hold that key to talk, and release it to stop.

Each channel has one assignment, with up to **32 channel assignments** in total.
Assigning an already-bound channel again replaces its key rather than creating a second assignment.
Use the row's **Edit** to change its key or **Remove** to delete the assignment.
At the 32-assignment limit, edit an existing row or remove one before adding another.

A Channel PTT key targets **that single channel**, independently of your TX group, and does not change the group.
General PTT still targets the TX group of up to 8 channels; with an empty group it uses primary, then selected channel if no primary is set.
Only **one PTT** can be active at a time: release the current key before pressing another.
Channel keys do not bypass sign-in, channel access, microphone permissions, busy checks, or active patch routing.

## Where assignments are saved

Bindings are local to the device/browser or desktop profile and the exact console origin: its scheme, host, and port.
They are **not account-synced** across devices, browsers, profiles, or console origins.
Different dispatch logins using the same local profile and origin share these assignments.
Review them on a shared workstation; signing into your own account does not load a separate shortcut set.

## Browser focus and desktop background PTT

In a browser, shortcuts require the console page to be focused and visible; background browser capture is not supported.
Typing in fields, focusing interactive controls, or opening a dialog can suppress shortcuts.
If a key does nothing, close dialogs and click a non-interactive area of the console before retrying.
Leaving or hiding the browser page releases active keyboard PTT; holding a key is not a latch.

Background **Channel PTT** on Windows/macOS requires **desktop app 1.3.9 or later with native bridge v6**, plus the updated hosted console.
Keep the desktop app running and signed in. Existing keyboard-hook permissions still apply; on macOS, retain or grant the app's **Accessibility** permission.
This does not make every console shortcut global: background support here is for PTT.
If the dialog says channel keys work only with the console focused, use focused PTT and ask staff about the desktop app/console compatibility.
Reloading the hosted page alone cannot upgrade an older native bridge; see the [desktop app guide](https://docs.lsreality.com/desktop-app.md).

## If a key will not work

If you see **Desktop PTT could not be synchronized**, do not assume background PTT has your new assignment.
Choose another key or reopen **Help → Keyboard shortcuts** to retry synchronization, then check the status again.
For background-only failures, check the desktop version and OS permissions; for capture failures, resolve conflicts or choose a key the OS does not intercept.
If PTT starts but transmission fails, read the console's **PTT failed** message and check microphone permission and channel availability.
Use the tile's single-channel hold button or top **TX group / PTT** control while resolving a keyboard issue, taking care to choose the intended route.
Contact staff with the exact error, whether the console was focused, and whether you used browser or desktop; see [troubleshooting](https://docs.lsreality.com/troubleshooting.md).


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