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 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

Create war rooms automatically controls whether eligible incidents receive a Slack war room. 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.

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.