Overview
Customer-visible capability is shaped by four layers: subscription presence, account type (Base / Dispatch / Admin in Console), role (Mobile User / Dispatch / Admin in User Management), and device model. Most "missing feature" tickets trace back to those layers — not defective hardware.
Navigator Mobile feature matrix
| Feature | No Subscription | Subscription |
|---|---|---|
| Compass voltage / current settings | ✓ | ✓ |
| Receive emergency event SMS messages | ✓ | ✓ |
| Detect and send emergency events | — | ✓ |
| Emergency map + chat features | — | ✓ |
| Receive emergency event notifications (in-app) | — | ✓ |
| Compass Pro configurations and administration (Console) | — | ✓ |
Navigator Console feature matrix
| Feature | No Subscription (Base) | Sub. (Base / Dispatch) | Sub. (Admin) |
|---|---|---|---|
| Account data | ✓ | ✓ | ✓ |
| Delete account | ✓ | ✓ | ✓ |
| Emergency map + chat | — | ✓ | ✓ |
| User management | — | — | ✓ |
| Organization management | — | — | ✓ |
| Compass Pro device configuration | — | — | ✓ |
Roles in plain language
- Mobile User (Base account): Navigator Mobile workflows — pairing, monitoring tabs and Tools, firmware (when permitted), and mobile emergency participation when enabled.
- Dispatch: Navigator Console operational surfaces such as Emergency Map and dashboards. Dispatch users have "Always Included In Emergencies" checked by default.
- Admin: user, group, and organization configuration; Compass Pro Configurations; everything Dispatch can do.
Groups and seats
Groups affect emergency routing — users only receive emergency alerts for the group they are in (unless they have "Always Included In Emergencies" checked). Seats are allocated per group via Edit Group Subscriptions in User Management.
Device model layer
Compass Core, Compass Pro, and Compass Pro IS are not interchangeable for every procedure — especially admin configuration, firmware packages, and certain field behaviors. Always capture model and hardware version (V4 or V5+) when escalating.