Why Am I Not Seeing Emergency Features?
Entitlement-first triage anchored to the Mobile and Console feature matrices: subscription / seat, role, org setup, app version, and model support.
Last updated Updated Estimated reading time 5 min read
emergencymissingentitlements
Overview
Emergency menus are gated by subscription and configuration. Confirm each layer below before assuming hardware failure.
Placeholder — replace with an entitlement-triage diagram showing the layers that gate emergency feature visibility.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 | — | — | ✓ |
Self-diagnose
- Subscription / seat: confirm the user has a subscription seat assigned (Subscribed checkbox in User Management).
- Role: confirm the role matches the feature you expect (Mobile User / Dispatch / Admin).
- Group membership: confirm the user is in a group that should receive the relevant alerts.
- "Always Included In Emergencies": for users who should receive every event (Dispatch by default), confirm the checkbox on their profile.
- App version: confirm Navigator Mobile is current per org policy — MDM may pin old builds.
- Admin setup: confirm the organization has completed emergency service settings and team configuration.
- Device model: confirm the model supports the workflow you expect (Compass Core does not have Smart Adaptive Mode, for example).