Skip to content

DASH updates for Cross Org Visibility #29816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 9, 2025
Merged

DASH updates for Cross Org Visibility #29816

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4bbd985
Add Log Management, clarify site requirement, fix wording
urseberry Jun 5, 2025
a6e3e43
Describe granular access controls on org connections
urseberry Jun 9, 2025
494ab02
Correct max number of connections
urseberry Jun 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 16 additions & 4 deletions content/en/account_management/org_settings/cross_org_visibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
---
title: Cross-Organization Visibility
description: Share data and perform queries between different organizations in the same account.
algolia:
tags: ["cross org", "cross-org", "cross organization"]
---

{{< callout url="#" btn_hidden="true">}}
Expand All @@ -22,23 +25,30 @@ This document explains:

### Organization connection

A _source_ organization exposes data to a _destination_ organization through an _organization connection_. The source and destination Datadog organizations must be in the same [account][1]. A source organization can have multiple destinations, and a destination organization can have multiple sources.
A _source_ organization exposes data to a _destination_ organization through an _organization connection_. A source organization can have multiple destinations, and a destination organization can have multiple sources.

The following limitations apply to organization connections:
- The source and destination organizations must be in the same [account][1]
- The source and destination organizations must be in the same [site][11].
- One organization can share with up to 5 other organizations.

Note that once the connection is established, the destination organization can query the source organization's data in the same ways it can query its own data. This means that the source organization's data—including sensitive data—may be queried and displayed as permitted by the destination organization's access-control and other settings. This may include, for example, the destination organization's ability to create [public Dashboards][10] using the source organization's data even if the source organization's own settings do not permit the creation of public Dashboards.

After you set up an organization connection, the exposed data is still stored in the source organization and does not move to the destination. Instead, the destination organization queries the data from the source. Connections do not duplicate the data, and do not incur extra charges. The destination organization can query source data from any time range supported by the source data, including prior to the date of the creation of the connection. If you remove the connection, the destination can no longer access any data from the source and any queries or Dashboards created from the source organization's data may no longer function.

### Scope

Cross-organization visibility supports Metrics telemetry in [Dashboard and Notebook widgets][2].
Cross-organization visibility supports Metrics and Log Management telemetry in [Dashboard and Notebook widgets][2].

All types of metrics are supported, including [custom metrics][3], [trace metrics][4], and [metrics generated from logs][5].

## Configure connections

### List connections

To browse connections, navigate to the [cross-organization visibility page][6] in Organization Settings. The table lists all of your cross-organization connections. Listing connections requires the _Org Connections Read_ permission.
To browse connections, navigate to the [cross-organization visibility page][6] in Organization Settings. The table lists all of your cross-organization connections.

Listing connections requires the _Org Connections Read_ permission. Additionally, you can use [granular access control][12] to restrict access to individual connections according to team, role, or user.

### Create a connection

Expand Down Expand Up @@ -84,7 +94,7 @@ The following screenshot shows an example of a cross-organization formula query.
### In the API

<div class="alert alert-info">
The <a href="https://registry.terraform.io/providers/DataDog/datadog/latest/docs">Datadog Terraform Provider</a> does not support creation of cross-organization connections. But a dashboard with widgets with cross-org queries may be Terraformed through proper JSON export.
The <a href="https://registry.terraform.io/providers/DataDog/datadog/latest/docs">Datadog Terraform Provider</a> does not support creation of cross-organization connections. However, you can manage a dashboard containing widgets with cross-org queries through Terraform by exporting the dashboard to JSON.
</div>

You can define cross-organization queries in the following endpoint:
Expand Down Expand Up @@ -147,3 +157,5 @@ Note the `cross_org_uuids` parameter in the JSON widget definition payload.
[8]: /api/latest/metrics/#query-timeseries-data-across-multiple-products
[9]: /api/latest/organizations/#list-your-managed-organizations
[10]: /dashboards/sharing/shared_dashboards/#public-shared-dashboards
[11]: /getting_started/site
[12]: /account_management/rbac/granular_access
Loading