Set up war rooms

War rooms run on the chat connection you already use for incident notifications. Point them at a Slack or Microsoft Teams channel, decide who gets invited, and optionally let KloudMate create a conference call for each incident.

The settings live on Incidents → Chat Ops, under Incident War Rooms, below the chat connection they use. You need the Developer role to change them. Everyone else sees them read-only.

Before you start

Your plan includes Incident Management.
Your workspace has a Slack or Microsoft Teams channel under Incidents → Chat Ops. See Slack Integration.
For a conference call that’s created per incident, you’ve connected Microsoft 365, Google Meet, or Zoom under Settings → Connections.

Set up Slack rooms

Slack needs more permissions to open a war room than it does to post a notification. Creating a channel, reading a member’s email address, and inviting people all sit behind permissions that a notifications-only install was never granted.

Open Settings → Connections and find your Slack connection.
Click Edit, add Workflows under Can be used for, and save. Those are the permissions a war room needs.
Click Reconnect beside the connection and approve the Slack install again. Approving again only adds permissions, so you don’t lose what Slack already had.
Open Incidents → Chat Ops, set Chat provider to Slack, and pick the channel under Chat channel.

KloudMate checks the channel’s permissions as soon as you pick it. If anything is missing, a Reconnect Slack to open war rooms banner lists the exact scopes, and Start war room stays disabled until you fix it. These are the ones it checks:

Scope	Why it’s needed
`chat:write`	Post and update the incident card.
`users:read` and `users:read.email`	Match a KloudMate user to their Slack account by email address.
`groups:write`	Create a private channel and invite people to it.
`channels:manage`	The same, for public channels.

Set up Microsoft Teams rooms

A Teams room is a group chat, created by the Microsoft 365 account you sign in with. That account owns every room, so use a service account rather than a person’s.

Open Settings → Connections and connect Microsoft 365 / Teams. Sign in as the account that should own the rooms.
Approve the permissions on the Microsoft consent screen.
Add a Microsoft Teams channel under Incidents → Chat Ops.
Set Chat provider to Microsoft Teams and pick that channel under Chat channel.

A Microsoft 365 connection is granted for Notifications and Meetings when you make it, which is what a Teams war room needs. The room and the call come from the same grant, so one consent screen covers creating the chat, posting to it, looking a member up by email address, and creating the online meeting.

Add a conference call

Conference call decides where the Join Call button points:

Option	What happens
No call	No call link, unless whoever opens the room pastes one.
The same link every time	KloudMate uses your Call link, rendered per incident, plus an optional Dial-in. Use a standing bridge, or a link with the incident key in it, such as `https://meet.google.com/lookup/inc-{{ key }}`.
A new meeting per incident	KloudMate creates a fresh meeting on the connection you pick.

For a new meeting per incident, connect one of these under Settings → Connections and select it in the war room settings. The picker lists connections granted for Meetings, so a Slack or AWS connection never shows up there.

Microsoft Teams

The Microsoft 365 connection you set up above also creates the meetings. Nothing else to connect. A Teams meeting comes with a dial-in number when your tenant has audio conferencing.

Google Meet

Connect Google Meet and sign in as the Google Workspace account that should own the meeting spaces. The consent screen asks to create meeting spaces, plus your name and email address to label the connection. The meeting permission reaches only the spaces KloudMate creates itself, not the rest of your Workspace. Google Meet returns no dial-in number, so rooms show the Join Call button on its own.

Zoom

Connect Zoom and install the KloudMate app. Every war room meeting is created as the account that installs it, so install it from a Licensed Zoom account: meetings hosted by a Basic account cut out after 40 minutes, which is not what you want halfway through an incident. Zoom rooms don’t show a dial-in number.

Removing the KloudMate app from Zoom revokes the connection. KloudMate erases the stored credential, marks the connection Revoked, and switches it off, so rooms open without a call link until the app is installed again. Reconnect beside the connection re-runs the install with the same connection id, so the war room settings keep pointing at it. Then turn Enabled back on under Edit. See Zoom for the full install and removal steps.

Set the defaults for every room

Setting	What it controls
Room name template	The channel name or chat topic. Use `{{ number }}`, `{{ key }}`, `{{ title }}`, `{{ severity }}`, and `{{ service }}`. The default is `inc-{{ number }}-{{ title }}`. Slack names are lowercased and stripped to letters, numbers, hyphens, and underscores, up to 80 characters. A Teams topic can run to 50.
Private room	Opens Slack rooms as private channels, which people have to be invited to. Turn it off to open public channels anyone in the Slack workspace can join.
Incident responders	Invites whoever is assigned to the incident.
On-call engineers	Invites whoever is on call. Leave the schedule picker empty to follow the incident’s escalation policy, or name specific schedules to use those instead.
Always invite	People who join every room, on call or not. An incident commander, for example.
After the incident resolves	How long a resolved room stays open before KloudMate archives it. Keep the room open turns the automatic archive off.

If a name is already taken by another incident’s channel, KloudMate adds a short suffix and uses that. A name you type yourself is never changed for you, so you’re told it’s taken instead.

Anyone who has no chat account for their KloudMate email address is listed on the card under Could not add, and tagged Unmapped on the incident panel. The room still opens, and everyone else is still invited.

Open a room automatically

Opening a room by hand is fine for the first few. After that, let the rule that creates the incident do it.

From a routing rule. Add the Start War Room action to the rule. Every incident that rule creates opens with a room. The rule uses the workspace roster unless you turn on Customize member roster for this rule, which replaces it for incidents this rule creates. See Routing Rules.

From an escalation step. Check Start War Room on this step in the step editor. The room opens when the incident reaches that step, and only on the policy’s first pass, so a policy that repeats won’t open a second room. See Escalation Policies.

Both paths are worth scoping tightly. A rule that matches everything opens a channel for every incident, and archived channels still count towards your Slack workspace limits.

War rooms overview: what responders see once a room is open.
Troubleshooting: scope banners, connection states, and missing call links.
Connections: where the Slack, Microsoft 365, Google Meet, and Zoom credentials live.