Mobile
Pairing your phone
4 min read
Pairing connects your phone to your Gateway once; after that the board follows you. The flow is built so the phone ends up holding as little as possible: a key for itself, not your account.
Before you start
- The Gateway is running on your machine (it starts with DevThrottle).
- Your phone can reach that machine - same Wi-Fi is the simple case; from outside, a VPN or an overlay network like Tailscale that makes your machine reachable.
The pairing flow
Open the mobile app from your Gateway
On the phone, browse to your Gateway's mobile address (the Director shows it - the mobile page is served by your own machine, under its /m path).Approve the phone on devthrottle.com
The phone is sent to the approval page, where you sign in with your DevThrottle account and see exactly what is asking: the device name and where it will connect. One button: connect this phone, or deny it.The phone gets its own key
On approval, the phone is handed a per-device key and returns to your Gateway. That key only works against a Gateway signed into your account - your own machine - and it identifies this one phone.Done - the board is in your pocket
The phone shows your sessions, and push notifications start arriving when an agent needs you.
Screenshot coming soonThe Connect this phone approval screen showing the device name before pairing
Why the phone never holds your account
The approval hands the phone a device key, never your account session. The difference matters exactly once - the day the phone is lost. A leaked device key costs you one revocable device: open Devices in your dashboard, revoke the phone, and it is out. Nothing about your account, your other devices, or your code goes with it.
Warning
If a phone is lost or stolen, revoke it in your devices right away. Revocation is the kill switch for that device's access.
Note
Each phone pairs individually and shows up as its own row in Devices, so a family tablet and your phone are separately revocable.