Getting started

Get the mobile app

Obtain an authorized WarnFire build, sign in on an iPhone or iPad, and receive incident pages.

The WarnFire mobile app is the responder companion for iPhone and iPad. It shows your on-call status, delivers incident pages, opens the exact incident associated with a notification, and records your response.

Before you begin

Your WarnFire administrator must add you under On-call → People and enable both:

• Can be paged, so WarnFire can include you in schedules and escalation policies.
• An enabled Sign-in (console) role and password, using the same email address as your responder profile. Viewer is sufficient for mobile sign-in, and only a tenant owner can grant this access. See Tenant console roles .

You also need access to a currently authorized WarnFire build. Ask your WarnFire administrator for the active installation method and follow the link or invitation they provide. Distribution may use TestFlight or another approved channel; this documentation does not claim that WarnFire is publicly listed in the App Store.

For installation access, use the distribution invitation supplied by your WarnFire administrator. If the current invitation is unavailable or expired, contact WarnFire support rather than installing an unverified build.

An authorized production-configured build connects to https://api.warnfire.com. It does not ask for a server address.

Install and sign in

1. Open the installation link or invitation provided by your administrator and install the authorized WarnFire build.
2. Open WarnFire.
3. Enter your WarnFire Email and Password.
4. Tap Sign in.
5. When iOS asks whether WarnFire may send notifications, choose Allow.

If you cannot sign in, check the message shown by the app:

WarnFire signs the device out if the account, responder, or organization is disabled. Once access is restored, sign in again.

The app tabs

• Status shows whether you are on call, the current response team, active invitations, shifts, cover and swap controls, and incident counters.
• Incidents is your incident inbox. Open an incident to see its summary and unified Activity record, including updates, paging events, response actions, and war-room activity.
• Settings contains appearance, alert sound, Stay reachable, diagnostics, account details, and Sign out.

Compatible status-page builds also have a Pages tab. Open a page to read its components and customer updates. Owners and administrators can use one Pause / Resume button per component: Pause takes a tap and confirmation, defaults to 30 minutes, and expires automatically; Resume takes one tap. Other workspace members can read pages. See Status pages for maintenance behavior, including shared services and existing incidents.

Enable and manage Critical Alerts

In a WarnFire iOS build that supports Critical Alerts, incident pages can play a sound through silent mode and Focus, including Do Not Disturb. This requires your permission on each device and Critical Alerts support on the server. Reminders and resolution notices remain ordinary notifications. Incident severity and iOS Critical Alerts are separate: this permission applies to incident paging notifications, not just incidents labelled Critical.

1. Install the current authorized build and sign in.
2. Allow ordinary notifications when prompted.
3. Allow Critical Alerts when iOS asks. If you already allowed ordinary notifications in an older build, the new build can request this additional permission separately.
4. In WarnFire, open Settings → Critical alerts and tap Request Critical Alerts permission if you need to request it again.
5. Tap Open iPhone Settings. Under Notifications, check that Allow Notifications and Critical Alerts are enabled. You can also reach this from iPhone Settings → Notifications → WarnFire (or WarnFire Preview if that is your installed app).

To stop pages from bypassing silent mode or Focus, turn off Critical Alerts in iPhone Settings. Ordinary notifications remain available while Allow Notifications stays enabled. Turning off all notifications prevents ordinary push alerts too. The permission is specific to the installed app and device; WarnFire and WarnFire Preview have separate settings.

If the Critical Alerts section or iPhone toggle is missing, your build may not support the capability. Ask your administrator for the current authorized build. Changing a console setting cannot add this capability to an older installed app.

Test delivery through Focus

After enabling both permissions, put the device in silent mode and turn on Focus. In WarnFire Settings, use Send test incident under Stay reachable, then put WarnFire in the background. Confirm that the incident notification arrives and plays a sound. This creates a test incident and may sound loudly; choose an appropriate time to test. Respond to or resolve the test incident when finished.

A message marked sent by the server does not prove that the phone played a sound. If the test stays silent, check the permissions for the exact installed app, its selected alert sound, network connectivity, and whether your server has the Critical Alerts update. Keep your SMS and voice contacts confirmed as additional paging channels.

Acknowledge a page

Open an incident and tap Acknowledge. WarnFire asks for Face ID, Touch ID, or the device passcode before recording the action. This prevents an accidental tap from stopping an escalation.

Acknowledgement identifies who owns the response and stops further escalation for that incident. It does not close the incident.

The mobile app does not resolve incidents. A monitoring-system resolve event closes an incident automatically, or an authorized operator can use Force resolve in the web console with a recorded reason.

Answer an invitation

An assistance push opens an authenticated, one-page invitation brief for the exact incident. The brief includes the requester, requested role, severity, source, current summary, target team, and request message.

The same invitation appears under You’re needed on Status. Available actions are:

• Join incident now
• In 15m, In 30m, or In 60m
• Decline request
• Leave incident, after joining

The decision becomes part of the incident activity record. Responders answer invitations in the mobile app. An authorized responder can create an invitation from the incident’s Response view in mobile, or an authorized console user can create one from the web incident workspace.

Notification behavior

WarnFire handles notification taps when the app is open, in the background, or fully closed. The destination is the incident or invitation identified by that notification. If the incident has already resolved, WarnFire opens its resolved record instead of a different active incident.

If the same responder is signed in on multiple devices:

• Each registered device can receive the page.
• Received and Opened evidence is recorded per device.
• Acknowledgement and incident state synchronize across signed-in devices.
• Signing out unregisters only that device; the other signed-in devices continue to receive pages.

iOS ultimately controls whether and when a notification is displayed. Keep notifications enabled and use Settings → Diagnostics when troubleshooting delivery.

Stay reachable

In Settings, open Stay reachable and choose Add WarnFire to contacts. If the contact already exists, the app offers Update contact or Re-save contact. Saving WarnFire’s paging numbers helps calls and texts pass unknown-caller screening.

See Make sure WarnFire can reach you for the complete onboarding check.

Verify it worked

Before sending the test, an administrator must confirm that an enabled schedule and escalation policy select this responder and that a non-production service uses that policy. Follow the configuration-readiness test . The test follows the selected channels; SMS and voice consume their respective allowances or prepaid credits.

1. Open Status and confirm that it loads your responder identity and current on-call state without an authentication error.
2. In iOS Settings, confirm that notifications are allowed for WarnFire.
3. Ask an administrator to send a test incident through a non-production service.
4. Confirm that the notification appears, then tap it and verify that WarnFire opens the same test incident rather than the general incident list.
5. On the test incident, tap Acknowledge, complete device authentication, and confirm that the incident records you as the acknowledging responder.

Next step

Complete the reachability checks before joining a production on-call rotation.

Compatibility before sign-in

WarnFire checks the server’s supported client versions before sign-in. If your app is no longer compatible with the API, update it using the button shown; the update screen cannot be dismissed. Compatible older versions can continue. If the server cannot be reached, retry the compatibility check once your connection is available. Preview builds open TestFlight on iOS; production builds open the App Store or Google Play.