---
title: Safely Dual Ship Workload Protection to Multiple Organizations
description: >-
  Requirements and considerations for dual shipping Workload Protection data to
  two Datadog organizations.
breadcrumbs: >-
  Docs > Datadog Security > Workload Protection > Workload Protection Guides >
  Safely Dual Ship Workload Protection to Multiple Organizations
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Safely Dual Ship Workload Protection to Multiple Organizations

This guide explains why and how to dual ship Workload Protection data to two Datadog organizations—for example, a primary organization used by platform teams and a second organization used only by security teams.

{% alert level="info" %}
Collecting events using Workload Protection will affect your billing. For more information, see [Datadog Pricing](https://www.datadoghq.com/pricing/?product=cloud-security-management#products).
{% /alert %}

## Why dual ship Workload Protection data?{% #why-dual-ship-workload-protection-data %}

[Dual shipping](https://docs.datadoghq.com/agent/configuration/dual-shipping.md) sends the same Workload Protection runtime events from a single Datadog Agent to two organizations. This is useful when different teams need access to different data in Datadog. For example, a security team needs Workload Protection signals, findings, and investigation workflows, while platform or application teams in the primary organization should not see security data.

In each destination organization, enable Workload Protection so Datadog can analyze the incoming runtime events and generate signals and findings.

## Infrastructure Monitoring requirement{% #infrastructure-monitoring-requirement %}

{% alert level="warning" %}
Datadog does not recommend running Workload Protection on an organization or sub-organization that does not have Infrastructure Monitoring enabled.
{% /alert %}

Workload Protection relies on [Infrastructure Monitoring](https://docs.datadoghq.com/infrastructure.md) to deliver a complete experience:

- Backend rules enrich Agent events with **infrastructure context** (cloud provider, host, Kubernetes cluster, container, and image), which powers detection, findings, and investigation workflows.
- **Host and container tags** scope policy deployment and rule filters across your environment.
- The [Coverage](https://docs.datadoghq.com/security/workload_protection/inventory.md) page and investigation workflows pivot to infrastructure views to identify unprotected hosts and reconstruct attack stories.

Without Infrastructure Monitoring, the Workload Protection experience is incomplete.

## Dual shipping and sub-organizations{% #dual-shipping-and-sub-organizations %}

To configure dual shipping, see the following documentation:

- [Dual Shipping](https://docs.datadoghq.com/agent/configuration/dual-shipping.md): Agent configuration for Workload Protection runtime events, infrastructure metrics, and other telemetry types. See the [Workload Protection](https://docs.datadoghq.com/agent/configuration/dual-shipping.md) section for `runtime_security_config.endpoints` settings.
- [Managing Multiple-Organization Accounts](https://docs.datadoghq.com/account_management/multi_organization.md): How sub-organizations work, including data isolation between organizations and usage tracking from a parent organization.

{% alert level="warning" %}
Dual shipping can impact billing if you send data to multiple Datadog organizations. For more information, contact [Datadog Support](https://docs.datadoghq.com/help/).
{% /alert %}

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Dual Shipping](https://docs.datadoghq.com/agent/configuration/dual-shipping.md)
- [Managing Multiple-Organization Accounts](https://docs.datadoghq.com/account_management/multi_organization.md)
- [Infrastructure Monitoring](https://docs.datadoghq.com/infrastructure.md)