WarnFireDocs

Getting started

Add your team

Add responders, assign console access, verify phone delivery, and issue personal API tokens.

Version 1.0 Status Needs verification For Tenant administratorsFor Tenant owners respondersaccessonboardingapi-tokens

WarnFire represents each person once. Paging access and sign-in access are separate settings on that person:

  • Can be paged makes the person eligible for schedules, escalation policies, SMS, voice, email, and push delivery.
  • A Sign-in (console) role lets the person sign in to the web console.

Mobile sign-in requires both capabilities under the same email address: an enabled console role supplies the credential, and Can be paged supplies the responder identity.

Enabling paging never grants management access by itself.

Seat and billing impact. Either enabled capability can make a new person a seat. WarnFire counts distinct enabled people by normalized email address, not capabilities: paging only, console access only, or both count as one seat. The console role and password method do not change the count, and adding the second capability to the same person does not create another seat. On an active Team, Business, or per-seat Enterprise subscription, WarnFire reconciles the billed quantity hourly; an increase invoices the prorated added-seat charge at that reconciliation. Trial workspaces count the seat without a per-seat charge. Flat-rate Enterprise and comped workspaces do not incur a per-seat charge. See What counts as a seat .

Before you begin

You need an existing WarnFire workspace . A tenant administrator can create and update paging responders. Only a tenant owner can create or change console membership, roles, passwords, and console tokens. Decide whether the person only needs to receive pages or also needs a console role. Have their name, email address, and phone number available before configuring paid delivery channels.

Add a person

  1. Open On-call → People.

  2. Select Add person.

  3. Under Identity, enter the person’s name and email address.

  4. Under On-call (paging), enable Can be paged if the person should receive incident pages.

  5. If you are a tenant owner and the person needs console or mobile access, under Sign-in (console) choose the smallest role that fits. A tenant administrator must leave No sign-in selected and ask an owner to grant console access. For the complete permission boundaries and API role names, see Tenant console roles .

    RoleAccess
    No sign-inResponder record only; cannot sign in.
    ViewerRead-only console access.
    AdminManages operational configuration.
    OwnerFull tenant administration, including access management.

  6. If granting sign-in, choose how to establish the password:

    • No password yet creates the enabled console identity, but password sign-in remains unavailable until an owner sends a setup link or sets a password.
    • Email a setup link invalidates any previous password for starting a new session and sends a single-use link that expires after 24 hours.
    • Set a password now lets the owner establish the initial credential; enable Require a change at first sign-in when the recipient should replace it immediately.

  7. Select Save changes.

If you set a password directly, WarnFire can require the person to change it on first sign-in. Share generated credentials through a private channel.

Add SMS and voice delivery

Open the person with Manage, enter the phone number in E.164 format, and enable the required SMS-consent confirmation. E.164 means +, the country code, and 8–15 digits with no spaces or punctuation; for example, +15551234567.

Save the person before testing the number. Then choose Send test text. The result shows whether WarnFire handed the message to the provider or why the request was rejected.

A test text consumes SMS allowance or prepaid credits according to its destination and carrier-billed segment count. Complete it whenever a number is first added or changed. See SMS destination bands and segments .

Mobile sign-in

Mobile access requires both Can be paged and an enabled Sign-in (console) role under the same email address. The responder signs in to the iPhone or iPad app with that email and password. No mobile pairing code or server address is required. Follow Get the mobile app for installation, notification permission, and sign-in verification.

If a responder leaves the organization or loses a device, disable the person or reset access as appropriate. The mobile app validates the session and signs out when access is no longer valid.

Personal API tokens

The Responder access tokens section issues bearer tokens for scripts and integrations acting as that responder. These are not tenant-wide viewer tokens and are not required by the mobile app.

  1. Find the person under Responder access tokens.
  2. Select Issue token.
  3. Copy the token immediately. WarnFire shows the secret only once.

Tokens expire after 90 days by default. Rotate replaces the active token, and Revoke invalidates it immediately. Store tokens in a secrets manager and never place them in source control or a shared chat.

Before closing the one-time display, verify that the token authorizes a safe read using the responder API:

curl --fail-with-body \
  -H 'Authorization: Bearer YOUR_RESPONDER_TOKEN' \
  https://api.warnfire.com/v1/me/status

A 200 response confirms the token and returns that responder’s live status. Use only the token belonging to the responder being tested.

Verify it worked

  1. Return to On-call → People and confirm that the person appears once with the expected paging and sign-in state.
  2. Select Manage and confirm that the saved email, phone number, and role are correct.
  3. If you enabled sign-in, have the responder sign in with the configured email and password or complete the emailed setup link.
  4. If you added a phone number, select Send test text and confirm that the responder receives it.
  5. If you issued a responder token, confirm that it appears as active with the expected prefix and expiry, and that the safe status request returns 200.

Adding a person does not make them on call. A team, schedule, or escalation policy must reference the responder before incident paging can select them.

Next steps