Console administration

Console administration

Administer workspace membership, response configuration, integrations, service defaults, and billing boundaries.

The WarnFire console separates operational administration from account ownership. Tenant administrators can manage day-to-day response configuration; tenant owners additionally control membership credentials and billing.

Build and verify a response path

Create operational configuration in dependency order:

1. Add responders and console access .
2. Create an on-call schedule .
3. Create an escalation policy .
4. Create a service and integration key .
5. Clear configuration-readiness issues and run a test incident .

Each service must point to a policy with at least one reachable target before WarnFire can report Configuration ready.

Administrative areas

• People and access: add people and understand tenant console roles .
• Schedules and policies: define on-call rotations and escalation steps .
• Services and integrations: issue and rotate service-scoped integration keys , then connect a monitoring adapter or the Events API .
• Workspace settings: configure notification channels, war rooms, acknowledgement defaults, and usage warnings .
• Maintenance: schedule a quiet period for planned work .
• Delivery review: find a delivery attempt and inspect its provider or device evidence.
• Billing and usage: review the workspace’s billing state and notification balances and its plan limits . Billing controls require tenant-owner authority.

Configuration changes are audited and generally apply to incidents created after the change. An open incident keeps its frozen response plan so an edit cannot silently change paging that is already underway.

Start with Services and integration keys when the people, schedule, and policy already exist. Otherwise follow the complete Getting started path.