Skip to content
EFA Projection · Docs

Remote control (desktop side)

The desktop app can be controlled from the mobile app during your service: someone with a phone can advance slides, show the logo, send the screen to black, play audio, and more.

The flow is split in two parts: the desktop side (what this page covers) and the mobile side (covered in Mobile remote control).

How it works in short

Section titled “How it works in short”
  1. When the desktop app connects to the server, it generates a 4-digit PIN that shows up in its top bar.
  2. Someone with the mobile app, signed in to the same organization, opens the remote control screen and enters the PIN.
  3. If the PIN is correct, commands from the phone reach the desktop in real time.

Where the PIN appears

Section titled “Where the PIN appears”

In the top bar of the desktop app, next to your username, you’ll see:

PIN: 4271

It’s a 4-digit code generated at random each time the app connects to the server.

Share the PIN with the team

Section titled “Share the PIN with the team”

For a phone to connect, someone has to see the PIN on the desktop in person and type it on the phone. Practical tips:

  • Before the service: the desktop operator tells the PIN to the preacher or whoever will control from the phone.
  • Operator change: if the person holding the phone rotates, share the current PIN with them.
  • Show the PIN to the team: the app doesn’t have a dedicated “show PIN” screen, but you can temporarily increase the zoom or take a photo of the screen if needed.

When the PIN changes

Section titled “When the PIN changes”

The PIN regenerates automatically in these cases:

  1. Desktop app restart — when it reconnects to the server, it generates a new PIN.
  2. Manual click on “Regenerate PIN” in the top bar — useful if you suspect someone unauthorized has the code.
  3. Reconnect after losing internet — if the connection dropped and came back, the PIN may change.

When the PIN changes, all already-connected phones lose authorization and have to enter the new one. The mobile app warns them with a “Session revoked — enter the new code” message.

See connected controllers

Section titled “See connected controllers”

When a phone authenticates successfully, the desktop app shows:

  • The username that connected (next to the PIN).
  • A visual “remote control active” indicator.

You can have several phones connected at the same time (e.g. operator

  • preacher). They all share the same PIN and can all send commands.

What the phone can control

Section titled “What the phone can control”

From the phone you can run the following actions on the desktop:

Section titled “Navigation”
  • Next / previous slide.
  • Jump to a specific slide.
  • Black screen (toggle).
  • Clear screen.
  • Show logo full screen.

Load content

Section titled “Load content”
  • Project a song from the repertoire.
  • Project a Bible passage.
  • Project a presentation.
  • Project media (image, audio, video).
  • Project a YouTube video.
  • Project a text slide.

Audio and video

Section titled “Audio and video”
  • Play / pause / stop / restart the background audio.
  • Toggle audio loop.
  • Play / pause / restart an active video.

Themes

Section titled “Themes”
  • Switch to an animated or static theme.
  • Set a solid color as the background.
  • Clear theme.

Limitations

Section titled “Limitations”

The phone has a few limits on what it can do:

  • It can’t create songs, programs, or presentations from the remote control screen (it can from the mobile admin section — see Mobile admin).
  • It can’t edit themes — only apply existing ones.
  • It can’t access content not yet synced to the desktop. If the desktop doesn’t have the song yet (because someone uploaded it from the web 30 seconds ago and the sync is pending), the phone receives an error.

Security

Section titled “Security”
  • The PIN is ephemeral — it only lives while the app is open and connected.
  • The phone has to be authenticated in the same organization to even reach the PIN — it’s not just the 4-digit code.
  • The PIN is transmitted via WebSocket over HTTPS/WSS (encrypted in transit).
  • If you suspect unauthorized access, regenerate the PIN from the desktop app — all active phones are de-authorized automatically.

Common problems

Section titled “Common problems”

The phone says “incorrect code”

Section titled “The phone says “incorrect code””
  • Check you’re looking at the current PIN (it may have changed due to a restart or reconnect).
  • Check the phone is in the same organization as the desktop.

The phone says “connected” but the desktop doesn’t respond

Section titled “The phone says “connected” but the desktop doesn’t respond”
  • Make sure the desktop app has internet (check the connection indicator in the top bar).
  • Try restarting the desktop app.

The PIN isn’t shown in the top bar

Section titled “The PIN isn’t shown in the top bar”

If you don’t see the PIN field:

  • The desktop app hasn’t connected to the server yet (check the connection status).
  • Your account doesn’t have an organization assigned — the PIN is tied to the active organization.
  • Refresh the app from View → Reload.

Next step

Section titled “Next step”

To set up the mobile side, Mobile remote control. For the rest of the desktop shortcuts, Keyboard shortcuts.