Mobile setup

Set up one responder device, prove incident delivery, and then use the same checklist for the rest of the on-call team.

Before you start

Ask an OpsKnight administrator to confirm:

the deployment is served over HTTPS;
production PWA generation is enabled (DISABLE_PWA is not true);
/manifest.webmanifest and /sw.js are reachable;
Web Push has a valid public/private VAPID key pair; and
your account can receive notifications for a test service and escalation policy.

PWA and push behavior varies by browser and operating system. Use a currently supported browser and keep the device screen lock enabled.

Open https://YOUR_OPSKNIGHT_HOST/m and sign in with the same credentials or OIDC provider used on desktop. OpsKnight may route a recognized mobile browser to /m automatically unless the device previously selected desktop mode.

Confirm that Home, Incidents, Services, Alerts, and More appear in the bottom navigation.

2. Install the PWA

iPhone or iPad

Open /m in Safari.
Open Share.
Select Add to Home Screen.
Confirm Add, then launch OpsKnight from its icon.

Android

Open /m in Chrome.
Open the browser menu.
Select Install app or Add to Home screen.
Launch the installed app.

Desktop Chrome or Edge

Use the install control in the address bar or browser menu when it is available. Desktop installation is optional; /m remains the mobile-oriented route.

If the browser does not expose installation, continue using /m in the browser and ask an operator to check HTTPS, manifest, service worker, and PWA build settings.

3. Enable push

In the mobile app, open More.
Find Push Notifications under Preferences.
Enable it and accept the browser or operating-system permission prompt.
Use the built-in test action and keep the app installed while testing.

If permission was denied, change it in the browser/site or operating-system settings. OpsKnight cannot reopen the permission prompt after the browser has blocked it.

4. Test the responder path

Trigger a synthetic incident for a service whose policy targets your account or current schedule.
Confirm a notification arrives while the app is in the background.
Open it and verify it lands on the intended mobile incident or Alerts route.
Acknowledge the incident.
Reload the detail page and confirm the timeline and status changed on the server.
Resolve the synthetic incident with a clear resolution note.

Do not onboard the rest of the team based only on the built-in push test. The synthetic incident proves service routing, schedule resolution, escalation, provider delivery, service-worker display, deep linking, authentication, and the response action together.

5. Record the result

For each supported device/browser combination, record:

operating system and version;
browser and version;
install result;
permission result;
synthetic incident ID and time;
notification arrival time;
deep-link destination; and
acknowledgement reflected on the server.

Repeat this test after proxy changes, certificate changes, VAPID rotation, major browser upgrades, or OpsKnight upgrades.

Common failures

No install option

Use the browser menu, verify HTTPS, and ask the operator to fetch /manifest.webmanifest and /sw.js. Development builds and deployments with DISABLE_PWA=true intentionally disable the production service worker.

No permission prompt

Check existing site and OS notification settings. Permission may already be allowed or denied, or the browser may not support Push API for this installation mode.

The built-in test works but incidents do not page

Check the service escalation policy, current schedule, your notification preferences, notification history, and provider logs. A device subscription does not select the incident's recipient.

Notification opens a sign-in page

Your OpsKnight session expired. Sign in again, then open the incident and verify its current status before acting.

Next steps

Read the mobile route and offline support matrix.
Give operators the PWA production checklist.
Review notification provider troubleshooting.