Add Personal Cover
Personal cover is anywhere-panic for a person rather than a property: someone who has no monitored premises, or whose cover needs to follow them off the property. They carry your app, and a panic reaches you from wherever they are with their live position attached.
Add personal cover sits on the Sites page, next to Create site, and does in one run what would otherwise be six separate pieces of setup. Its tooltip is "Anywhere-panic for a person with no monitored premises", and the modal opens with:
Anywhere-panic for a person with no monitored premises. From a name and a mobile number this creates their base (a site marked as a person), links it to your control room with full monitoring, adds a Panic App hub, puts the person on it with location panic switched on, and sends them the app invitation.
The button follows the same permission as Create site — it creates a site, so a scoped team member needs the customers key (or workspace admin) on top of company membership. Operators who can browse sites don't see it.
Location panic only works for an app user on a site with a linked hub, and that site quietly does three jobs nothing else can: it is how the person resolves to your control room, it is what the per-app-user billing line is scoped by, and it is where the person's own record lives (their panic scope, medical alerts, photo and call-list position). So personal cover still creates a base — the base is just a site marked as a person rather than a property.
Before you start
Two things are worth checking first, because neither is fixed from inside this modal:
-
Your control room's location-panic opt-in must be on. Settings → General → App panic → Offer location panic.
This run does not switch the opt-in on for youAdd personal cover grants the person location panic, but it does not touch your control room's opt-in. With the opt-in off, everything below still succeeds and the cover is inert — a person given Site + location falls back to site panic only, and a no fixed address person (whose premises panic is deliberately off) is left with no working panic at all.
Selling Panic app cover through an onboarding journey does switch the opt-in on; this button does not. Switch it on first.
-
A published app, if you want the invitation sent from here. The modal checks up front and tells you before you create anything — the same reasons as Settings → App onboarding: no branded app, built but not live, rejected, paused, or no verified store listing. With no app, the base, hub and person are still set up and only the invitation step is skipped.
If the Panic App hub product isn't available to your environment at all, the modal refuses before creating anything rather than leaving you a half-built base.
Filling in the form
| Field | Notes |
|---|---|
| Person's name | Required. Names the base site, and the customer if you create one from it. |
| Mobile · WhatsApp / SMS | Required — it is where the invitation goes and how the control room reaches them. |
| Optional. Adding one enables the email invitation tickbox below. | |
| Customer | Only shown with the CRM module on. Either New customer named "…" (created from the person's name, with their number and email as the billing contact) or Existing customer via the picker. Without CRM the step is skipped entirely. |
| Where do they need cover? | The two scopes below. |
| Home address | Only in At home and anywhere. Search or drop the pin, then the address lines, city, province and country. The pin is required — a premises panic is dispatched to it, and it is what places the base in a suburb. |
| App invitation | WhatsApp (on by default; falls back to SMS if WhatsApp can't deliver) and/or Email (needs an address above). Untick both to just mint a link you can pass on yourself. |
The two scopes
- At home and anywhere — a panic at the house is dispatched to the pin; anywhere else uses their live location. This is the normal choice for someone who has a home you would actually send a vehicle to.
- Anywhere only — no fixed address — for someone with no premises at all. Location panic only: the premises panic is switched off, so nobody is ever dispatched to a placeholder address. No pin is asked for and no address is stored.
The App panic select on the person's row (Site → People → edit person) reads Location panic only (no premises) for someone created this way, and the option is in the list, so the scope can be read, changed and set back from there like any other. The base this run builds is typed Personal (panic), which is where the option is offered; it also appears on anyone who already carries the scope, wherever their record sits.
What the run does
The six steps run in order, and each reports its own result on screen as it completes — including anything skipped and why:
| # | Step | What it creates |
|---|---|---|
| 1 | Customer | The customer, or reuse of the one you picked. Skipped when CRM is off. |
| 2 | Base (a site marked as a person) | The site itself, typed as a person. No groups, no zones, no site image and no installation window — there is nothing to install, and an installation window would suppress the very dispatch the cover exists for. |
| 3 | Control room link | The site↔control-room link: approved, primary, full monitoring. |
| 4 | Panic App hub | A Panic App hub, claimed to your control room, given its billing account, then linked to the base. |
| 5 | Person | The person as a keyholder on that base, with their panic scope set and app push limited to panics and panic updates. |
| 6 | App invitation | Sent by WhatsApp/SMS and/or email, or minted as a link. Valid 14 days. |
A No monitoring site has every one of its events dropped before it reaches the control room. A location panic would survive that (it has no site at all), but the site panic that the panic-first Home screen sends would be silently lost — the person would press the button, see it sent, and nothing would arrive. Personal cover therefore always creates the link at full monitoring. Changing that base to no monitoring later breaks half their panic.
When the app invitation can't be sent
The base is complete whatever happens at step 6. If your control room has no published app, the step is marked skipped with the reason, everything else is kept, and you invite the person later from the site's People tab (Onboard). If a channel simply fails to deliver, the per-channel result is listed and the invitation link is still shown for you to copy and pass on.
When a step fails
Nothing is rolled back. Every step before the failure succeeded and is kept — the run says which step failed and what to finish by hand:
| Failed at | What you're told to do |
|---|---|
| Customer | Nothing was created. Fix the problem and try again. |
| Base | No base was created, so there is nothing to clean up. Try again. |
| Control room link | The base exists but isn't linked, so it won't appear under Sites. Don't just retry — that creates a second base. Ask support to link or remove the orphan (its site id is on screen). |
| Panic App hub | The base is linked but has no Panic App hub, so there's no location panic. Open the site → Add hub → Panic App, then add the person on the People tab with App panic → Site + location panic, and onboard them. |
| Person | The base and hub exist but the person isn't on them. Site → People → Add person (non-app), set App panic, then Onboard to app. |
| App invitation | Everything else is in place. Site → People → Onboard on that person to send it again. |
The modal can't be closed while the run is in flight, so a half-built base is never hidden behind a stray click.
When it's finished
The result screen offers Open site (straight into the new base) and, where one was minted, the invitation link with a copy button.
On the site itself the person appears on the People tab like any other keyholder — same editor, same medical alerts, photo, call order and panel-user fields. The base carries one Panic App hub on Hardware and nothing else.
How it bills
Personal cover bills per app user, as a Panic user line on your billing breakdown — not per site.
Three things worth knowing:
- It starts when the invitation is accepted, not when you send it. An invited-but-not-yet-accepted person doesn't bill.
- The hub must be both claimed to your control room and linked to the base. A complete run does both; a hub left unlinked by a failed step neither bills nor works.
- Someone already billed as an approved member of one of your communities isn't double-counted.
Related
- App panic — the opt-in and the control-room default that decide whether any of this is live.
- Panic App sites — the panic-button-only hub product.
- Site details → People — the person editor, the App panic override, and onboarding a keyholder to the app.
- Create a Site — the normal, premises-based route.
- CleverCommand → Mobile panic events — what a location panic looks like when it reaches an operator.