It is possible to manage multiple child-organizations from one parent-organization account. This is typically used by Managed Service Providers that have customers which should not have access to each others’ data. Users can be added to the parent-organization and/or multiple child-organizations and switch between them from the user account settings menu. The parent-organization can view the usage of individual child-organizations, allowing them to track trends in usage.
Account settings, such as whitelisted IP addresses, are not inherited by child-organizations from their parent-organization.
The Multi-organization Account feature is not enabled by default. Contact Datadog support to have it enabled.
Here’s a two-minute video walkthrough:
The new child-organization inherits the parent-organization’s plan and is added to the parent-organization’s billing account. If you want to update the child-organization’s billing, contact your sales representative.
Onboarding a new sub-organization with a set of baseline dashboards and monitors can be done programmatically with the Datadog API and tools such as Terraform, see Managing Datadog with Terraform. Additionally, scripts can be used to backup existing dashboards and monitors as code.
The custom sub-domain feature is not enabled by default. Contact Datadog support to have it enabled.
If you are a member of multiple organizations, custom sub-domains help you identify the source of an alert or notification. Also, they can immediately switch you to the organization associated with the sub-domain.
For example, the URL
https://app.datadoghq.com/event/event?id=1 is associated with an event in Organization A. If a user is a member of both Organization A and Organization B, but is currently viewing Datadog within the context of Organization B, then that URL returns a
404 Not Found error. The user must switch to Organization A using the user account settings menu, then revisit the URL. However, with custom sub-domains, the user could visit
https://org-a.datadoghq.com/event/event?id=1 which would automatically switch the user’s context to Organization A and display the correct page.
To configure SAML for multi-organizations, use the following procedure:
The parent-organization can view the total and billable usage of all their organizations (child and parent organizations) by hovering over their username at the bottom left and then navigating to:
Plan & Usage–>
The Multi-Org Usage tab shows the aggregate usage of the parent-organization and all its child-organizations. There are two sub-tabs on the Multi-Org Usage tab:
This view contains an Overall Usage section and an Individual Organization Usage section.
The Overall Usage section summarizes your month-to-date usage of hosts, containers, custom metrics, and any other part of the platform you’ve used during the month, across your parent-organization and all its child-organizations.
The Individual Organization Usage section contains two views that breaks down your month-to-date usage of products by organization. The “All” view is a table that lists by product the unadjusted, raw usage of your parent-organization and all child-organizations. To view the Usage Details of a child-organization, you can click on the child-organization’s name.
To view only the usage that will count toward your bill, you can switch to the “Billable” view. This removes organizations that are not billable such as trial organizations in addition to other adjustments that will provide a more accurate summary of what drives your bill.
The month-to-date usage and last month’s usage can be downloaded as a CSV file.
This tab shows the monthly aggregate usage across all organizations over the past 6 months. The usage shown here is “All” usage not “Billable” usage, which means it does not adjust for trial periods or other billing changes used to calculate your final bill.
This information can be downloaded as a CSV file.
The parent-organization can view the usage of child-organizations by existing tag keys in the Usage Attribution page. Admins can hover over their username at the bottom left, then navigate to:
Plan & Usage–>
When enabled at the parent-organization level, usage attribution will show usage aggregated across all organizations. This can be useful if you would like to attribute the usage of your child-organizations to certain projects, teams, or other groupings.
Usage attribution can also be enabled at the child-organization level. When enabled at this level, the tags are only applied to that specific child-organization and can only be viewed in that child-organization. Tags applied at the child-organization level do not rollup and cannot be viewed in the parent-organization.
Note: the following usage types are not supported in this tool:
Note: Indexed Spans were formerly known as Analyzed Spans and renamed with the launch of Tracing Without Limits on October 20th, 2020.
Usage Attribution is an advanced feature included in the Enterprise plan. For all other plans, contact your account representative or email@example.com.
Additional helpful documentation, links, and articles: