> For the complete documentation index, see [llms.txt](https://docs.primeur.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.primeur.com/panorama-2.0.1/operational-resilience/business-continuity-playbook/add-critical-flows.md).

# Add critical flows

When accessing the **Business Continuity Playbook** for the first time, no data is available by default.\
To populate the Playbook, you must import one or more modeled flows from **Data Watcher**.

To import flows:

1. Click **Add** on the **Business Continuity Playbook** page.
2. In the **Add critical flows** window, select one or more modeled flows using the checkboxes in the first column.\
   **Only modeled flows available in Data Watcher are displayed**. 
3. Confirm the import and add the selected flows to the Playbook with their current attributes. 

The **Add critical flows** window displays the list of available Data Watcher models that can be imported as critical flows into the playbook. Only models that have **not yet been imported** into Panorama are shown, ensuring that duplicate entries are avoided. Already imported flows are therefore excluded from the list, while [synchronization mechanisms](/panorama-2.0.1/operational-resilience/business-continuity-playbook/data-watcher-synchronization.md) can be used to update existing ones.

The **Add critical flows** window provides a tabular view of all available flows with filtering and selection capabilities. 

<figure><img src="/files/LVVQEk8VmWB3NT4dSxNq" alt="" width="563"><figcaption></figcaption></figure>

The following elements are available:

* **Selection checkboxes:** each row includes a checkbox to enable single or multiple selection. A header checkbox may be used to select all visible rows.
* **Search field (Model column):** a text input allows filtering flows by model name. The search applies dynamically to the list.
* **Criticality level dropdown:** each flow is assigned a default **Medium** criticality level, visible as a dropdown in the **Criticality level** column. The value can be modified after import.
* **Column-based layout:** the table includes the following columns:
  * **Model**: flow identifier/name. It includes a text filter field.
  * **Criticality level**: default classification (Medium). It includes a per-row dropdown selector.
  * **Source**: originating endpoint (if available). It includes a text filter field.
  * **Destination**: target endpoint (if available). It includes a text filter field.
  * **Protocol**: communication protocol (if defined).&#x20;
  * **Cut-offs**: indicates whether cut-off constraints are configured (e.g. YES). It includes a dropdown filter.&#x20;

After import, the selected flows are registered in the **Business Continuity Playbook**.

During this process, Panorama not only imports the basic structure of the flow but also enriches it with available metadata from **Data Watcher**. For example, if scheduling data such as cut-offs is defined in the source model, it is automatically included; if not, the corresponding fields remain empty.

<figure><img src="/files/0n8ZW405wLAQVyy7pLQC" alt="" width="563"><figcaption></figcaption></figure>

Once the import is completed, a summary window is displayed confirming the operation. This window shows the imported flows and indicates which types of information have been successfully retrieved (such as attributes, technical configuration, and planning data). From this confirmation view, you can directly navigate back to the **Business Continuity Playbook** page.

Once a critical flow is imported, it becomes available in the **Business Continuity Playbook** table as a new entry and can be:

* Enriched with business and operational attributes
* Updated in terms of criticality and metadata
* Extended with contingency procedures
* Monitored for completeness and resilience gaps

See the [Open a critical flow](/panorama-2.0.1/operational-resilience/business-continuity-playbook/open-a-critical-flow.md) page for details.&#x20;