Console administration

Workspace operational settings

Tenant-wide controls for war rooms, notification channels, acknowledgement defaults, and usage warnings.

Before you begin

You need tenant-owner or tenant-administrator access. If you plan to enable automatic Slack war rooms, connect Slack first . Changes to response-plan defaults and permitted channels apply when a new incident captures its plan. Monthly SMS and voice caps are different: WarnFire checks them at each paid send, so lowering a cap can suppress a later paid attempt on an incident already open.

The Configuration → Settings page controls tenant-wide incident-response defaults. Existing incidents keep their frozen targets, steps, and channels so an administrative edit cannot rewrite an escalation already running. Paid credit availability and monthly caps remain delivery-time guardrails and are checked again whenever an SMS or voice attempt is about to start.

Update operational settings

1. Open Configuration → Settings.
2. Under War rooms, choose the war-room provider, whether WarnFire creates rooms automatically, the minimum incident severity, whether resolved rooms are archived, and the archive delay.
3. Under Permitted channels, enable the notification channels policies may use. At least one channel must remain enabled.
4. Under Acknowledgement timing, set the default timeout suggested when new policy steps are created. Existing policy steps retain their explicit value.
5. Under Paid-channel guardrails, set the usage-warning percentage and any monthly SMS or voice caps. Leave a cap blank to use the plan allowance and available prepaid balance.
6. Select Save operational settings.

War rooms

War room provider selects the single provider used for new incidents. Select Slack to use Slack, or None — no war room to prevent room creation. Zoom remains coming soon in the general provider selector. In an operator-enabled development environment, use Integrations → Zoom → Use Zoom for new incidents to select Zoom explicitly. If your operator has enabled Zoom authorization, a tenant owner or administrator can connect an account under Integrations → Zoom. Connection alone does not enable Zoom war rooms. Viewers can inspect the connection but cannot change it. Disconnecting removes WarnFire’s stored credentials and cancels pending authorization; removing the app in Zoom is a separate action. Connecting an integration does not change this choice or create an additional room. Existing Slack behavior is preserved until you change the choice.

Each incident keeps its original choice. Changing this setting affects new incidents; it does not move existing rooms, create a second room, or enable fallback to a different provider. Normal incident notifications are separate from war-room creation.

Create war rooms automatically controls whether eligible incidents receive a room through the selected provider. Automatic creation also requires:

1. an enabled Slack installation; and
2. the war-room switch on that Slack installation.

The tenant-wide switch does not override a disabled or disconnected Slack installation.

Minimum incident severity limits automatic creation to one of these levels:

• Warning and above
• Error and critical
• Critical only

Archive after resolution posts the closing summary and then archives the Slack channel only when Archive the channel when the incident resolves is also enabled under Integrations → Slack → Automatic incident war rooms. Both switches are required. The console offers these archive delays:

• Immediately
• 15 minutes
• 1 hour
• 4 hours
• 24 hours

The delay gives responders time to finish discussion after resolution without leaving resolved war rooms open indefinitely.

Request assistance from a Zoom incident card

In an enabled development workspace, a responder whose Zoom identity is linked and who has access to the incident can select Request assistance on its Team Chat card. Choose Ask beside a responder to send a subject-matter expert assistance request. The card shows up to six additional responders with active push devices. For all responders, teams, a different role or a custom message, open the incident in WarnFire and use Add resource.

The request uses the normal WarnFire assistance notification and response flow. It does not grant incident authority just by adding someone to Zoom. Repeated clicks cannot create another request while that responder’s invitation is pending. Resolved incidents, revoked Zoom identities and unavailable push destinations cannot start a request.

Each request’s card entry shows its assistance status separately from Team Chat access: invitation pending, invited, Zoom identity must be linked, or a recorded invitation failure. An accepted assistance request does not prove a Zoom channel invitation succeeded. Owners can review recorded invitation failures under Integrations → Zoom → Integration health; platform owners can review them in Settings → Zoom tenant health.

Allowed notification channels

The tenant can allow or disallow push, email, SMS, and voice independently. WarnFire requires at least one channel to remain enabled. When a new incident captures its plan, WarnFire removes policy-selected channels that the tenant has disabled. If that would leave a step with no channel at all, WarnFire substitutes the first tenant-permitted channel in this order: push, email, SMS, then voice. The incident records a tenant_channel_fallback entry so the substitution is visible. A usable destination still has to be configured for the responder.

Disabling a channel is a future-delivery control. It does not erase historical delivery attempts or alter the frozen response plan on an incident that is already open.

Default acknowledgement timeout

The default acknowledgement timeout is the suggested wait for newly created response-policy steps. It accepts values from 30 seconds through 60 minutes. Existing policy steps retain their explicit timeout and remain authoritative.

Usage warnings and optional caps

The usage warning threshold can be set from 50% through 100%. WarnFire uses it to show an early warning before the included allowance or configured cap is exhausted.

Optional monthly SMS and voice caps can further restrict paid-channel use for the tenant. Leaving a cap blank uses the plan allowance and any available prepaid balance. SMS and voice caps are separate because the two channels use different credit pools. A changed cap applies to the next paid attempt, including one from an incident already open; it does not undo an attempt already sent.

For plan allowances and velocity limits, see Plans, credits, and rate limits .

Verify it worked

Confirm that the page displays Saved and recorded in the audit log. Refresh the page and verify that each saved value remains selected. If war rooms were enabled, remember that the Slack installation’s own war-room switch must also be enabled.

Next step

Return to configuration readiness and run a test incident after any change that could affect paging or war-room creation.

Development Zoom war rooms

Use Check Zoom setup to verify the connected account. The last successful check time belongs to that connection and clears when it is replaced. Granted scopes alone do not prove meeting host eligibility or channel membership.

After selecting Zoom for new incidents, use Create Zoom war rooms automatically in Zoom settings to control automatic creation. This is the same workspace setting shown in Operational settings. With automation off, open the incident and select Start war room in the console or mobile app. It creates the meeting and private Team Chat channel together. Existing rooms remain available when the switch is turned off. Meeting and channel creation have separate status. Checking a previous creation attempt means WarnFire is reconciling provider evidence and will not issue a replacement create request.

In Zoom connection settings, New meeting defaults contains two switches:

• Waiting room requires the host to admit participants. Turning it on turns off joining before the host.
• Allow participants to join before host lets responders enter before the connected host. Turning it on turns off the waiting room.

Changes save automatically for new room requests. Existing meetings and pending room reservations keep their saved settings. Zoom account policies may restrict these choices. The initial defaults keep the waiting room on and joining before the host off. Meeting passcodes remain enabled.

Once ready, use Join Zoom meeting or Open Zoom Team Chat. Zoom still requires an invitation for other members of the private channel. Meeting started/ended indicators and timeline entries appear only after authenticated Zoom event deliveries; no event means activity is unknown. Operators must subscribe the development Marketplace app to meeting.started and meeting.ended at https://api.dev.warnfire.com/v1/integrations/zoom/events. In Zoom Marketplace, open Features → Access, enable Event Subscription, choose Webhook and add both Start Meeting and End Meeting to the same subscription. Save the subscription after validating its endpoint. Ending a meeting does not resolve the incident. Incident cards are sent automatically to the incident’s private Team Chat channel. Linked, authorized responders can acknowledge, resolve, and add explicit notes. In-meeting chat remains unavailable.

Responders use the mobile incident’s Response tab and its Join war room button. The provider label identifies the reserved Slack channel or Zoom meeting. The app checks current incident access when opening the room; Zoom participant links are fetched only for that action. Zoom meetings use the connected host, and the host must admit participants through the waiting room. Other chat providers are not available yet.

Assistance from mobile and the console

On mobile, Request assistance is directly below Acknowledge on an open incident. Its responder/team, role and message fields expand there; the Response tab shows response activity. In the console War Room, the assistance form opens beside Request assistance. A rejected request keeps the selected target and message and shows the server’s reason.

Assistance delivery requires the recipient to have an active push-enabled WarnFire mobile device. If the request is refused for that reason, ask the recipient to sign in to the mobile app and enable push notifications before retrying. A WarnFire assistance request and access to the private Zoom channel are separate: the recipient also needs a linked Zoom identity for channel invitation.