Notifications
Push, SMS, and voice fallback delivery paths.
Overview
When a call arrives, Core notifies residents via Knock workflows:
- Push to registered Device tokens (FCM / APNs via Knock).
- SMS approve/deny links when
fallbackSmsEnabledis true. - Voice fallback to
phoneNumberwhenfallbackCallEnabledapplies.
See Notifications architecture.
Device admin API
| Method | Path | Description |
|---|---|---|
GET | /api/admin/devices | Audit devices |
POST | /api/admin/devices/:id/test-push | Send test push |
Mobile clients register tokens via POST /devices/register on Core directly.
User fields
| Field | Role |
|---|---|
preferredNotificationSound | default, urgent_chime, intry_chime |
phoneNumber / phoneVerified | SMS + voice fallback eligibility |
fallbackCallEnabled | Voice call on entry |
fallbackSmsEnabled | SMS with action links |
Operational notes
- Token rotation: expect periodic FCM/APNs updates from the app.
- Do not log raw device tokens — treat as secrets.
- DND in app/portal blocks notifications silently.
Last verified: 2026-06-21 (commit 293c4a7)