> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cymph.io/llms.txt
> Use this file to discover all available pages before exploring further.

# War Rooms

> Coordinate an incident: bring the right people together, run playbooks and keep every file and decision in one place

A war room is the place where an incident is handled from the first alert to the post-incident review. It brings together the people responding, the playbooks they execute, the files they collect, the updates they send to stakeholders and a complete, timestamped history of everything that happened.

Each war room belongs to a workspace and goes through a simple lifecycle:

* **Preparing**: the room has been created and people are being gathered, but the clock has not started yet.
* **Started**: the incident is being handled. The room moves through the NIST incident response phases (Detection and Analysis, Containment Eradication and Recovery, Post-Incident Activity).
* **Resolved**: the room has reached the Post-Incident Activity phase and the review is being written or is complete.
* **Archived**: the room is closed and read-only. It can be reopened at any time.

> [!NOTE]
>
> War Rooms are a licensed feature. If the section does not appear in your navigation menu, your license does not include it. Contact us to enable it.

# Navigation

War Rooms have their own entry in the navigation menu. Selecting it opens the War Rooms navigator, which has two entries:

* **Current Workspace → All War Rooms**: the rooms that belong to the workspace you currently have open.
* **Across All Workspaces → All War Rooms**: every room you can see in any workspace, plus every room you take part in as a participant or guest, even if you are not a member of that workspace.

The **Start War Room** button at the bottom of the navigator creates a new room in the current workspace.

![War Rooms List Overview](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_list_overview.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=3da0796b4e5423a001af9e4c8ddff43b)

# The War Rooms page

The War Rooms page lists rooms grouped by their state in four tabs: **Preparing**, **Started**, **Resolved** and **Archived**. The number next to each tab is the count of rooms in that state.

Each row shows the following information:

* **Name**: the name of the war room.
* **Workspace** (only in the *Across All Workspaces* view): the workspace that owns the room.
* **Your role**: what you are in this room. Either your incident role (for example Incident Commander or Scribe), *Participant* if you are seated without a role, or *Guest* if you were added as a guest from outside the workspace. Guests also see whether they have opened the room yet.
* **Status** (Archived tab only): the state the room was in when it was archived, Preparing, Started or Resolved. On the other tabs the tab itself is the status.
* **Severity**: Not specified, Low, Medium, High or Critical.
* **Stage**: the NIST incident response phase the room is currently in.
* **Purpose**: **Operational** for a real incident or **Exercising & Testing** for a drill. The purpose is chosen when the room is created and cannot be changed afterwards. Every execution started from an exercise room runs in exercise mode and every notification it sends is clearly marked as an exercise.
* **Participants**, **Executions**, **Files**: counts of the people seated in the room, the playbook executions started from it and the files uploaded to it.
* **Started** and **Started By**: when the clock started and who started the room.

Columns with a sort icon can be sorted by clicking their header.

The filter bar above the tabs narrows the list. Filter by name (which also searches descriptions), severity, incident type, stage, purpose, your role, who started the room and, in the *Across All Workspaces* view, the workspace. Filters apply to all four tabs at once, and the counts next to the tabs follow them. A combination you use often can be saved from the bar and picked again later.

> [!TIP]
>
> A room stays in **Preparing** until someone presses *Start the room* inside it. Use this state to seat the right people and attach assets before the incident clock starts running.

# Actions on the table

Hover over a row to reveal its actions next to the name:

* **Open**: opens the war room in a new browser tab, so you can keep the list and several rooms open side by side.
* The **⋯** menu: shows a summary of the room (name and when it was started) and the actions available to you.

![War Rooms List Row Actions](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_list_row_actions.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=898e049ef0aaa6540bfda9ca44d622bc)

The menu contains the following actions:

* **Edit Details**: change the name, description and meeting link of the room, as well as its incident details (severity, incident type, affected assets and services). Available on rooms that are not archived.
* **Archive War Room**: closes the room. An archived war room is read-only: nobody can add participants, upload files or start executions until it is reopened. You are asked to confirm before the room is archived. Only the Incident Commander can archive; for other participants the action is greyed out and says so on hover.
* **Reopen War Room**: shown instead of *Archive War Room* on archived rooms. Only the Incident Commander can reopen; the action is greyed out for other participants. Reopening restores the room to the state it was in when it was archived.
* **Export War Room**: downloads a zip archive with everything in the room: a timeline PDF with the participants, executions and the full activity log, every uploaded file together with an integrity manifest, a PDF per execution and the chat transcript. See [Exporting a war room](#exporting-a-war-room).

> [!NOTE]
>
> Every participant of a room can edit and export it; archiving and reopening are the Incident Commander's. Guests and workspace members who are not seated in the room can only open it. Starting a new war room requires the right to create war rooms in the workspace, which comes with your workspace role.

# Starting a war room

Press **Start War Room**, either in the navigator or at the top right of the War Rooms page. A four-step dialog collects what the room needs. Only the name and the purpose are mandatory; everything else can be filled in or changed later from inside the room.

> [!NOTE]
>
> Creating the room does not start the incident clock. The room is created in the **Preparing** state and the clock starts when someone presses *Start the room* inside it.

## Step 1: General

![Start War Room General](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_new_step1_general.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=51109d307cd67b8150fc34b14705441d)

* **Purpose**: **Operational** for a real incident or **Exercising & Testing** for a drill. This is set once and cannot be changed after the room is created. Every execution started from the room inherits the purpose, and in an exercise room every in-app notification, email, SMS, Slack or Teams announcement and export is marked as an exercise so nobody mistakes it for a real incident. See [Exercise rooms](#exercise-rooms).
* **War room name**: the name shown in every list, notification and export.
* **Description**: a short summary of what is going on.
* **Meeting link**: a Teams, Zoom or Meet link that participants can join from the room.

## Step 2: Incident

![Start War Room Incident](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_new_step2_incident.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=5b31da980d662b5771cb5b3cac6995a7)

* **Severity**: Not specified, Low, Medium, High or Critical. It uses the same scale and colours as playbook severity.
* **Incident type**: the threat type being handled (for example Phishing or Ransomware), using the same list as playbooks, plus *Other*.
* **Affected assets**: assets from the workspace asset inventory that the incident touches.
* **Affected services**: free text for the business services affected, for example Payroll, customer portal, VPN.

## Step 3: People involved

![Start War Room People](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_new_step3_people.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=e39efe83bdb71a667c8161e651f203e7)

* **Participants**: pick members of the workspace and teams from your organisation. The list shows the people who have access to the workspace, external members included. Adding a team seats its members who belong to the workspace, each as an individual participant. You join automatically as the creator.
* **Roles**: each participant can be given an incident role: **Incident Commander**, **Scribe**, **Comms Lead** or **Technical Responder**. Every room has exactly one **Incident Commander**, and it is you unless you give the role to one of the people you invite; the room cannot be started without one. The Incident Commander commands the room (see [People in the room](#people-in-the-room)). The other roles say who does what and do not change what people can do.
* **Who can see this war room**:
  * **Workspace**: everyone with access to the workspace can open the room. People who are not seated can read it but cannot act in it.
  * **Restricted**: only the people added to the war room can see it, administrators included. The room is hidden from the workspace list. Use this when someone in the workspace may be the subject of the incident.

> [!NOTE]
>
> Guests from outside the organisation cannot be added at this step. Once the room is started, open its **Participants** tab to add guests.

## Step 4: Time target

![Start War Room Time Target](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_new_step4_target.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=8f8568652f28a8e2d3d4c4b9ff7cb0f6)

The time target is the KPI for the incident as a whole, entered as days, hours and minutes. It is measured from the moment the room is started until the incident is resolved, which is when the room enters the **Post-Incident Activity** phase. Tick **Set infinite time** to leave the room without a target.

The room shows the elapsed time against the target in its header and warns when the target is exceeded. The target can be changed later from the room.

Press **Start War Room** to create the room. It opens in a new browser tab in the Preparing state.

# The war room page

A war room opens in its own browser tab, like an execution, so you can keep several rooms and the list open at the same time. The page has five areas:

1. **Header**: the room name and purpose, the room menu, the incident clock and your notifications.
2. **About War Room sidebar** (left): the facts of the incident, counters that jump to each tab and the quick actions.
3. **Incident phases panel**: the three NIST phases the room moves through and the button to start the room.
4. **Tabs**: Overview, Review, Participants, My Tasks, Files, Executions, Broadcasts, Activity History and Access.
5. **Room thread** (right): the live chat of the room.

![War Room Page Overview](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_page_overview.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=e57f9a14e152f1bd8a784ae75d3aba32)

## Preparing state

Right after creation the room is in the **Preparing** state. The header clock reads *Not started*, the Incident phases panel shows a **Start the room** button and the timeline is empty. Use this time to add participants, attach assets and upload what you already have. The incident clock, the time target and the phases do not run until the Incident Commander presses **Start the room**; other participants see the button greyed out, with the reason on hover. Executions cannot be started from a room that has not been started.

![War Room Prepared](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_prepared.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=0932bd801c5006d707027ccfc993d50a)

## Header

From left to right the header contains:

* **Back**: returns to the War Rooms list.
* **Purpose tile** and **room name**, with *War Room (Operational)* in the accent colour or *War Room (Exercising & Testing)* in blue above the name. An exercise room shows a different icon, and hovering it reminds you that everything the room sends out is marked as an exercise.
* **⋯ menu**: the same actions as in the list, that is Edit Details, Archive or Reopen, and Export.
* **Incident clock**: *Not started* with the target while preparing, then the time left against the target (for example *3:56:47 left of 4h*), turning into *Over by …* once the target is exceeded. The pencil next to it changes the time target.
* **Notifications** and your **profile avatar**.

## About War Room sidebar

The sidebar summarises the room:

* **Facts**: mode, severity, current phase, incident type, affected assets and services, started time, time target, deadline, resolved time, incident commander, who started the room, visibility and workspace. If a meeting link was given, a **Join the bridge** link appears here. The pencil at the top opens the edit dialog.
* **Details**: participants with their avatars and the counts of your tasks, executions, files and broadcasts. Each row opens the corresponding tab.
* **Quick actions**: **Start an execution**, **Send broadcast**, **Add participants** and **Log activity**.

Press the chevron at the top of the sidebar to collapse it to icons and give the overview the full width. The quick actions stay available as icons, and the room thread can be collapsed the same way from its own chevron.

![War Room Sidebar Collapsed](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_sidebar_collapsed.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=f9157ed6da30cd5375a8148b578bd7ae)

## Incident phases

Every war room follows the NIST incident response lifecycle, the one most teams already use. The panel shows the three phases, highlights the current one and, on hover, shows how long the room has been in it.

![War Room Phases](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_phases.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=72e9c02d67432a9a574b367699ee275f)

1. **Detection and Analysis**: the room starts here when it is started.
2. **Containment, Eradication and Recovery**: click the phase to move the room forward once the response is under way.
3. **Post-Incident Activity**: entering this phase marks the incident as **resolved**. This stops the incident clock and opens the post-incident review, see [Post-incident review](#post-incident-review). The room cannot enter this phase while an execution started from it is still running.

A room can be moved back to an earlier phase, after a confirmation. Moving back out of Post-Incident Activity withdraws the resolution and the clock resumes from the original start. Every phase change is recorded in the Activity History and announced to the channels configured in the organisation's war room notification settings.

## Overview tab

The Overview tab is the default view of a room and the place to check what is going on at a glance.

### Timeline

The timeline shows the life of the room on one time axis, from the moment it was started to the deadline:

* **Activity** curve: how much happened in each slice of time, counting history entries, execution progress and chat messages. The busiest moment is labelled.
* **Phases** band: when each phase started and ended.
* **Executions** bars: one bar per execution started from the room. A bar turns accent-coloured once the execution is over its own time target, and a dotted vertical line marks each execution's deadline.
* **Markers** above the curve: executions started and broadcasts sent. Click a marker to see what it was.
* The solid accent line is **now**, the solid grey line is the **room deadline**.

The window follows the clock until you pan or zoom. Use the **‹ ›** controls to move earlier or later, **−** and **+** to widen or narrow the window, and the expand icon to show the whole range. **Activity history** opens the full log.

### Cards

Below the timeline the overview shows four cards:

* **My tasks**: the latest steps assigned to you across the executions of this room, each with the execution name and how long it has been waiting. **Open step** opens the execution at that step in a new tab. **All my tasks** opens the My Tasks tab.
* **Broadcasts**: the latest update sent to stakeholders. If the sender promised a next update and it is late, the card shows how long it is overdue with a button to send it now. **All broadcasts** opens the Broadcasts tab.
* **Executions**: one row per execution with its status, who it is waiting on and for which step, its completion bar, and its elapsed time against its time target. **Start an execution** launches a playbook from the room, see [Executions](#executions).
* **People**: the avatars of everyone in the room, participants and guests, split into **Opened** (they have opened the room at least once) and **Not opened yet**. **Add** opens the add participants dialog.

## Room thread

The panel on the right is the live chat of the room, named after it. Participants and guests can write, anyone else who can open the room can read, and an archived room keeps its thread read-only. The thread has two tabs: **Messages** and **Files** for the attachments shared in the chat. The count at the top right shows how many people are in the thread. Messages posted here count as activity on the timeline and are included in the chat transcript of the export.

> [!NOTE]
>
> The voice and video call buttons next to the thread name start a call for the people in the thread. They are shown only when calls are enabled for your organisation.

# People in the room

There are three ways to be in a war room:

* **Participants** are the responders. Every participant can edit the room's details, add people and guests, upload and manage files, log activity, write the post-incident review and export the room.
* The **Incident Commander** is the one participant who commands the room. Only the commander can start the room, move it through its phases (resolving the incident included), send broadcasts and move or withdraw the next-update promise, archive and reopen the room, and give roles to the others. There is exactly one commander at a time. The commander's controls stay visible to every participant, greyed out, and say on hover who can use them, so nobody wonders where an action went.
* **Guests** are people from outside the workspace who get access to this room only, until a date: an incident response retainer, outside counsel, the cyber insurer, or a colleague from your organisation who is not a member of the workspace. Guests read the room, upload files and log activity. They never see files labelled TLP:AMBER+STRICT or TLP:RED.
* **Onlookers** are workspace members who are not seated in a room with *Workspace* visibility. They can open and read the room but cannot act in it.

> [!NOTE]
>
> Scribe, Comms Lead and Technical Responder describe responsibilities and do not change what a person can do. Starting executions from the room follows each person's own right to run playbooks in the workspace, whatever their room role.

## Participants tab

The Participants tab lists everyone seated in the room with their role, job title, teams, when they were added, when they first opened the room (*Not opened yet* until they do) and who added them.

![War Room Participants](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_participants.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=a5efe91474aea69f565a7e5a24e22703)

* **Add participants** opens the same picker as the Start war room dialog: members of the workspace and teams from your organisation. The Incident Commander can give each person a role (Scribe, Comms Lead or Technical Responder) as they join; anyone else seats them without a role. People already in the room are not listed.
* **Role**: the Incident Commander changes a person's role from the select in their row. Giving someone a role notifies them.
* **Handing over command**: the Incident Commander picks **Incident Commander** on another participant's row and confirms. That person takes command and the previous commander keeps their seat with no role. The commander cannot take another role or drop to *No role* directly: naming a successor is the only way out of the seat, so the room is never without command. If a room has nobody in command (for example the commander's account was disabled), any participant can name a commander; until then the room's phases, broadcasts and archiving are on hold.
* **Remove**: hover a row to reveal the remove action. You cannot remove yourself, and the Incident Commander cannot be removed before command is handed over, so a room never ends up without anyone in it. Removed people are notified.

Every addition, removal and role change is recorded in the Activity History.

## Guests

Switch to the **Guests** list in the Participants tab to see who has guest access, whether they have opened the room yet, who they are (for example *IR Retainer*), until when their access lasts and who added them.

![War Room Add Guest](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_add_guest.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=a7f867390d650a2128847fa2fb8d613b)

Press **Add guest** and fill in:

* **Person**: anyone with a Cymph account, in your organisation or outside it. People who have not signed up to Cymph yet cannot be added.
* **Who** (optional): a label for the list, for example the company or the capacity they act in.
* **Access ends**: the date and time the guest access expires. It cannot be more than a year away.

The guest is notified in the app, and by email if the mailer is enabled. Access is immediate: there is nothing to accept. In an exercise room the notice is marked as an exercise.

From the guests list you can **Change** the label and the expiry, **Revoke** the access at any time, and **Add again** someone whose access was revoked or has expired. Revoking works on archived rooms too.

> [!TIP]
>
> Someone from your organisation who is not a member of the workspace can be added as a guest, or added to the workspace first and then seated as a participant.

## Access tab

The Access tab shows who can see the room and what each person can do.

![War Room Access](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_access.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=ec1f8f4300a552387eb8c469805b31ca)

* **Who can see this war room**: switch between **Workspace** (everyone with access to the workspace can open the room) and **Restricted** (only the people seated and the guests can open it; it is hidden from everyone else in the workspace, administrators included). Use Restricted when someone in the workspace may be the subject of the incident. The executions started from the room follow the change. The change is recorded in the Activity History.
* **Who can do what**: one row per person with how they are in the room (Participant, or Guest with their status and expiry), their room role, the war room actions available to them, and whether they can start executions from the room.

## My Tasks tab

The My Tasks tab lists the steps assigned to you across the executions started from this room, with the execution name, the step status and how long it has been waiting. **Open step** opens the execution at that step in a new tab. The count in the tab label is the number of open tasks.

![War Room My Tasks](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_my_tasks.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=20ec461fa470b1ff1b49f992cb62cba1)

# Files

The Files tab is the evidence locker of the room: indicators, screenshots, reports or anything else the team needs at hand.

![War Room Files](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_files.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=71f5405768d2be0abcef80f74d72fa23)

Each file shows its size and type, who uploaded it and when, its fingerprint (a SHA-256 hash, click it to copy) and its labels. The icons at the end of the row edit the labels, remove the file and download it. A crossed-out eye next to the labels means the file is hidden from guests.

## Evidence labels

Press **Upload file** and choose a file of up to 20 MB. Before it is uploaded you are asked for its labels:

![War Room File Upload](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_file_upload.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=25b061e989dfbebe4206c46f5dffd050)

* **TLP level**: the Traffic Light Protocol level, how far the file may be shared. TLP:CLEAR, TLP:GREEN, TLP:AMBER (the default), TLP:AMBER+STRICT or TLP:RED. Files labelled TLP:AMBER+STRICT or TLP:RED are hidden from guests: they do not see them in the list or in the activity history, cannot download them, and cannot upload files with these labels themselves.
* **Classification**: Public, Internal (the default), Confidential or Restricted.

Labels can be changed later from the row. The file is rejected if it is too large or its content does not match its type.

## Chain of custody

Every file action is recorded in the Activity History: the upload (with the fingerprint, labels, size, type and who uploaded it), every download and the deletion. The fingerprint is taken as the file is uploaded and checked again when the room is exported, so the export states for each file whether it is still exactly the file that was uploaded. See [Exporting a war room](#exporting-a-war-room).

# Executions

Playbooks are run from the war room so that the work, the people and the outcome stay attached to the incident. The Executions tab lists every execution started from this room with the same columns, filters and grouping as the workspace [Executions](https://docs.cymph.io/key-features/executions.md) page, plus a **Steps** column with the steps done out of the total and how many are late. Each execution opens in a new tab.

![War Room Executions](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_executions.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=f6ab8313606f487a57dcb073b878bd13)

## Starting an execution

Press **Start an execution** (in the Executions tab, the Overview card or the sidebar quick actions). The run dialog is the same as for a playbook, with three differences:

![War Room Start Execution](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_start_execution.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=7256787080ea1269e67d9dbcec58f945)

* **Runs as** is locked to the purpose of the room: an operational room runs operational executions, an exercise room runs exercises.
* The execution is **linked to the room**: it shows up in the room's Executions tab and timeline, its final outcome lands in the Activity History, and its steps feed the My Tasks tab of each participant.
* **Who can see this execution** (step 2, People involved) is locked to the visibility of the room. The executions of a restricted room are restricted too: only the people seated in the room and the people holding their steps see them. See [Who can see an execution](https://docs.cymph.io/key-features/executions.md#who-can-see-an-execution).
* **Add assignees to the war room** (step 2, People involved, on by default): everyone who gets a step in the execution, or claims a team step, joins the war room automatically as a participant. Nobody is ever removed automatically.

Only playbooks of the room's workspace can be chosen, and starting an execution requires the right to run playbooks in that workspace, the same as outside a war room.

> [!NOTE]
>
> Executions can only be started while the room is **Started** and not yet in Post-Incident Activity. The three *Start an execution* buttons are disabled otherwise, with a tooltip saying why. The room cannot move into Post-Incident Activity while one of its executions is still running.

# Broadcasts

A broadcast is a status update sent from the room to the people who need to know: the participants, the guests, people and teams in your organisation who are not in the room, and external email addresses or phone numbers such as leadership, the insurer or a regulator. Every broadcast is recorded in the Activity History and included in the export, so the communication trail of the incident is complete.

![War Room Broadcasts](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_broadcasts.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=2d9991d81e1ae18a2a707b97afc05da5)

The Broadcasts tab shows every update sent, with its subject and message, the channels it went through, the size of its audience, and whether the next update it promised was **kept**, is **due**, or is **overdue** and by how much.

## Sending a broadcast

Press **Send broadcast** in the tab, in the Overview card or in the sidebar. The dialog has two steps.

![War Room Send Update Step 1](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_send_update_step1.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=21cf3a323d8ad743775d5908ed4124f3)

**Step 1, Message:**

* **Subject** and **Message**: what has happened, what is being done, what is needed from whom. SMS carries the first 600 characters of the message.
* **Send through**: **In-app** is always on. **Email** and **SMS** are offered only when they are set up for your organisation, see [Notification settings](#notification-settings). Slack and Teams announcements follow the organisation settings automatically.
* **When is the next update?**: a promise to the audience. Choose a quick pick from 15 minutes to 4 hours, a custom time within 72 hours, or **None**. The default is 1 hour.

![War Room Send Update Step 2](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_send_update_step2.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=b7b2e86d9d39a03602bf793710a92253)

**Step 2, Recipients:**

* **All war room participants**: on by default. The sender is not notified.
* **All guests**: the guests whose access has not ended. They get the update with a link to the room.
* **People and teams in your organisation**: anyone who should be informed without joining the war room. They are notified in Cymph and by the channels chosen, without a link to the room.
* **External email addresses** and **External phone numbers** (only for the channels chosen): people outside Cymph. Phone numbers must be in international format.

In an exercise room, the subject and the message are prefixed with \[EXERCISE] on every channel.

## The next update promise

When a broadcast promises a next update, the room counts down to it. The header shows a **Broadcast overdue by …** pill when the promise is missed, the Overview card shows the countdown and, if the update is late, a button to send it now, and the Broadcasts tab marks each promise as kept or late. When a promise is missed, the lead of the room (the Incident Commander, otherwise the last sender, otherwise the creator) gets an in-app notice once and the miss is recorded in the Activity History. The Incident Commander can move or withdraw the promise from the Overview card, and sending a new broadcast replaces it.

# Activity History

The Activity History is the complete, timestamped record of the room: who did what and when. It is written automatically by the system and completed by hand by the people in the room, and it is the backbone of the timeline PDF in the export.

![War Room Activity](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_activity.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=671ead76d1436c7aea2f911051659116)

The system records: the room being created, started, moved between phases, resolved, archived and reopened; incident details and severity changes; people added, removed, named to a role, opening the room for the first time, guests added, changed and revoked; files uploaded (with their hash and labels), downloaded, relabelled and deleted; executions started and their outcome; broadcasts sent and next-update promises made, kept, missed or withdrawn; the post-incident review recorded.

The toolbar has three controls:

* **Reported / Happened**: sort by when entries were logged, or by when the thing actually happened. Backdated manual entries are placed where they happened, not where they were recorded.
* **All entries / Manual / System**: show everything, only the entries people logged by hand, or only the entries written by the system.
* **Category**: narrow manual entries to Decisions, Actions, Findings or IOCs.

## Logging activity by hand

Press **Log activity** in the sidebar quick actions to record something that did not happen inside Cymph: a host isolated, a decision taken on a call, a finding from forensics. Manual entries get a **Manual** pill in the history.

![War Room Add Activity](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_add_activity.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=99bf75d882c26e3a6a377ad95d9a2026)

* **What happened?**: the entry text, up to 2000 characters.
* **Category** (optional): Decision, Action, Finding or IOC.
* **When did this happen?** (optional): leave empty if it is happening now, or backdate it. Entries dated before the room was opened are accepted and marked as such, which is fine when detection came first.
* **Link to** (optional): files, assets or executions of this war room that the entry refers to. They appear as chips on the entry.

Participants and guests can log activity. Guests can only amend their own entries.

## Amending an entry

Entries are never edited or deleted. To correct a manual entry, hover it and press **Amend**: you give the corrected text, time, category or links and a reason (for example a typo, or new information from forensics). The correction is added as a new entry, the original stays on the record with the old text struck through, and both are kept in the export. The author of the entry and any participant can amend it, on rooms that are not archived.

# Post-incident review

Moving the room into **Post-Incident Activity** marks the incident as resolved, stops the incident clock and opens the post-incident review: what happened, what it cost and what the team learned, in the team's own words. What Cymph measured (timings, executions, broadcasts) is already in the room; the review adds the human account. The review is the material for the regulatory final report and for the lessons-learned meeting.

The review dialog has three steps. You can **Skip for now** when resolving and write the review later from the **Write the review** button in the Incident phases panel or from the Review tab.

## Step 1: Summary

![War Room Review Summary](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_review_modal_summary.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=e55d6c5196d52b81161a7476f632574a)

The **Summary** is required: a few factual paragraphs on how the incident started or was detected, what was affected, what the team did and how it was resolved. **Draft with Cymph AI** writes it for you from the room's activity history, in the language of your interface, and replaces the text in the box. Read it through before saving: it is a draft from the record, not a verdict. The button is shown when Cymph AI is enabled for your organisation.

## Step 2: Impact

![War Room Review Impact](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_review_modal_impact.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=6187fe6dfd2f0ed97192f5e7a1ae98c5)

* **Affected systems and services**: pre-filled from the affected assets and services of the room the first time; edit freely.
* **Personal data involved**: Yes, No or Unknown, with room for which data and roughly how many people. A yes usually triggers breach-notification duties under the privacy laws that apply to you; check their deadlines.
* **Business impact**: interrupted processes, customers affected, financial or contractual consequences.
* **Downtime**: how long the affected services were unavailable, in hours and minutes.
* **Who was notified**: one line per party told about the incident (regulator or CSIRT, data protection authority, customers, insurer, law enforcement, other) with when and a note.

## Step 3: Lessons

![War Room Review Lessons](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_review_modal_lessons.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=d53bd7b1c262e93ea0261f4110257f28)

* **Root cause**: how the incident happened, the initial access, the weakness or the mistake behind it.
* **What went well?**: detection, containment, communication or tooling that worked as intended.
* **What could be improved?**: gaps, delays, missing playbooks, access or information that slowed the response.
* **Lessons learned**: what the team takes away and the follow-up actions to make it stick.

**Save review** (or **Resolve and save review** when you are resolving the room at the same time) records the review under your name. Saving it again later overwrites the fields you change and records an update in the Activity History.

## Review tab

![War Room Review Tab](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_review_tab.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=83d64324206b6cde06dfd94c6ea8045a)

The Review tab shows the recorded review: the summary, the impact cards and the lessons, with who recorded it and when. **Edit review** reopens the dialog. The review is also printed in the timeline PDF of the export.

## Turning the review into playbook changes

A review is only useful once the playbooks change. Ask Cymph AI about the room, for example "What should we learn from the ransomware war room?": the assistant finds the room, reads its review together with the improvement suggestions and final notes recorded on the executions run in it, and answers with proposed updates to the playbooks that were run or that cover this kind of incident. Each proposal opens as a review card, so you step through the changes and apply the ones you agree with. When the team had no playbook for what happened, the assistant recommends a new one and offers to draft it.

> [!TIP]
>
> Exercise rooms count too. The lessons of a drill are proposed the same way, marked as coming from an exercise.

> [!NOTE]
>
> Cymph AI must be enabled for your organisation. The assistant never sees a restricted room you are not seated in.

# Archiving and reopening

When the incident is over and the review is written, the Incident Commander closes the room with **Archive War Room** from the room menu. An archived room is read-only: nobody can add participants, upload files, start executions, send broadcasts or log activity, and the room thread becomes read-only too. Guests can still be revoked, and the room can still be exported.

![War Room Archived](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_archived.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=0afbc1dcffe0cd441d1cbe454f4585f3)

The room shows a banner saying it is archived, and the **Reopen** button on it (or **Reopen War Room** in the menu) restores the room to the state it was in when it was archived. Archiving and reopening are recorded in the Activity History and announced to the configured channels.

Archived rooms are listed under the **Archived** tab of the War Rooms page, with the state they were in when archived in the Status column.

# Exporting a war room

**Export War Room**, in the room menu or in the list, downloads a zip archive that is a self-contained record of the incident, suitable for the insurer, the regulator, auditors or a lessons-learned meeting. It contains:

* **The timeline report** (PDF): a cover with the room facts, severity, incident type, purpose and timings, then the participants and guests, the executions, the full activity history with every file's custody details, and the post-incident review.
* **The files**: every file uploaded to the room, together with an integrity list that gives, for each file, its labels, its fingerprint at upload and at export, whether the two still match, and its custody trail: who uploaded, downloaded, relabelled or deleted it, and when.
* **The executions**: a PDF report per execution started from the room, the same report you can download from an execution.
* **The room thread**: the chat as a PDF, with the files shared in it.

For an exercise room, the archive name starts with EXERCISE and every report carries the exercise mark.

# Notification settings

How your organisation is told about war rooms is set by an organisation admin in **Organisation → Settings → Notifications**, in the **War Room Notification Preferences** section, separately from execution and task notifications.

* **Channels**: **Email** (members who have email enabled in their own notification settings are emailed when they are added to a room, and broadcasts can go out by email), **SMS (Twilio)** (participants are texted on the mobile phone of their profile, if they have SMS enabled in their notification settings), **Slack** and **Microsoft Teams** (room moments are announced in the configured channels, threaded per room).
* **Announced in Slack and Microsoft Teams**: which moments are posted: war room opened, status updates sent, severity changed, phase changed, war room archived or reopened.
* **Texted to participants (SMS)**: which moments participants are texted about: added to a war room, severity changed, phase changed, archived or reopened. For status updates this only pre-selects SMS in the Send broadcast form; the sender can still change it.

Each person controls their own channels in **Account Settings → Notifications**, and adds the mobile phone number used for SMS next to their job title in their account settings. The participants list shows only whether a person has a number, never the number itself.

In-app notifications are always sent: when you are added to or removed from a room, named to a role, added as a guest, when a broadcast is sent, and to the lead of the room when a promised update is overdue. Each notification opens the room.

# Exercise rooms

An **Exercising & Testing** room is for drills and rehearsals. Inside Cymph it behaves exactly like an operational room, so the team trains on the real tool. The difference is in everything the room sends out: the subject and message of every broadcast, every in-app notification, every email, SMS, Slack and Teams announcement, the export archive and the reports all carry an **\[EXERCISE]** mark, so nobody outside the room can mistake the drill for a real incident. Executions started from an exercise room run as exercises and mark their own notifications the same way.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.