Onboarding radios and devices with admin-approved pairing

Rolling out PTT is two problems. Getting audio working. Knowing which physical device belongs to which officer. Shared logins cause chaos. Pairing ties each handset to one user and makes it obvious which device reported which blip on the map.

The flow that works

Create user accounts first. Assign talkgroups. Hand the device to the field user only after an admin approves pairing in the tenant console. They sign in once on that hardware. If the device is lost, unassign it without resetting everyone's password.

Most teams start on standard Android phones over Wi-Fi or mobile data. That proves coverage and training before anyone orders PoC hardware. Radios slot into the same pairing model later, so there is no second process to learn when a team decides it needs dedicated hardware for part of the operation.

Why shared logins cause problems later

It is tempting, especially on a tight rollout timeline, to set up one login per shift rather than per person. This causes two problems that only show up after the fact. First, the map cannot tell you who is actually carrying which device, which defeats much of the point of having live positions at all. Second, when someone leaves the team, you cannot revoke their access without resetting the login for everyone still using it.

Pairing at the individual level costs a little more setup time upfront and saves considerably more time later, particularly around staff turnover.

Getting the sequence right

Keep a simple register matching asset numbers to users. Pair in the office before the shift, not at the gate with fifty people behind you. Test PTT and GPS on the actual site, not just the car park, since coverage and signal behaviour can differ meaningfully between a depot and a real route.

A practical sequence looks like this: create the account, assign the correct talkgroups, pair the specific device in the admin console, then hand the device over with a short walkthrough of the PTT button and how status shows on the app. Doing this in order avoids the most common rollout headache, which is a device paired to the wrong person because pairing happened after handover instead of before.

When someone leaves

When someone leaves, disable the user and unassign devices the same day. Pairing is only as good as your leaver process. A handset that stays paired to someone who no longer works for you is both a security gap and a source of confusing map data, since their old device may still report a position under an account nobody is actively managing.

Build this into whatever offboarding checklist your organisation already uses, rather than treating it as a separate IT task that might get missed during a busy week.

Scaling beyond a pilot

MDM helps on large fleets, particularly where devices are shared assets rather than individually owned. It is not mandatory for a two-user pilot. Start with pairing discipline, and add device management tooling once headcount and device count make manual tracking genuinely difficult rather than just slightly more paperwork.

For teams considering dedicated hardware rather than staff phones, see our hardware page for what pairs through the same admin console.

A short checklist worth keeping

Most rollout problems come from skipping a step under time pressure, not from the process itself being wrong. A short checklist pinned in the depot office tends to prevent more issues than any amount of after-the-fact troubleshooting: create the account, assign talkgroups, pair the device, confirm PTT and GPS on a real route, then hand it over with a two-minute walkthrough.

Keep the same checklist for every new starter, even once the process feels routine. Rollouts that skip steps for "just one quick addition" are where shared logins and unassigned old devices tend to creep back in.

Common questions

What happens if a phone is lost or stolen? Unassign the device in the admin console immediately. This does not require resetting anyone else's password, only removing the pairing for that specific hardware.

Can one person be paired to more than one device? Yes, for example a supervisor with both a phone and a tablet, though most field roles only need one paired device.

Do PoC radios pair differently to phones? No. The pairing flow is the same regardless of hardware, which is deliberate so teams can mix phones and dedicated radios without learning two processes.

How long does pairing take per device? It is a short admin approval followed by one sign-in on the device itself, typically a few minutes per handset once the user account already exists.

Use the free tier with two phones on one site before a wider rollout, and use that pilot to write down the sequence that worked for your team rather than relying on memory when you scale up.