---
title: Team Management
description: >-
  Customize team pages, manage membership, set up subteams, and configure team
  access through identity providers or SAML attribute mapping.
breadcrumbs: Docs > Account Management > Teams > Team Management
---

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

# Team Management

## Team detail{% #team-detail %}

Each team has a detail page that displays information about the team, its members, and its associated resources. Navigate to a team detail page by clicking on a team from the [Teams directory](https://app.datadoghq.com/organization-settings/teams).

The team detail page is organized into three tabs:

- **Info**: Core team details and membership.
- **Resources**: The Datadog resources associated with the team.
- **On-Call**: The team's [Datadog On-Call](https://docs.datadoghq.com/incident_response/on-call.md) configuration.

The team header displays the team's avatar, banner, name, and description. Customize the look of your team by choosing an emoji avatar and banner. The emoji avatar displays next to the team name in lists across Datadog.

### Info tab{% #info-tab %}

Core team details: notification channels, links, connections, hierarchy (parent team and subteams), and members.

### Resources tab{% #resources-tab %}

The Datadog resources the team owns, grouped by area such as productivity, software, performance, and cloud cost. If the team has subteams, use the **Include Subteams** toggle to show their resources alongside the team's own.

### On-Call tab{% #on-call-tab %}

The team's [Datadog On-Call](https://docs.datadoghq.com/incident_response/on-call.md) setup: members, schedules, escalation policies, routing, and handover automation.

### Customize settings{% #customize-settings %}

To modify a team's details, you must have the `user_access_manage` or `teams_manage` permission. Alternately, you can be a team member or team manager of a team that is configured to allow members and managers to edit team details.

Edit a team's details directly from its detail page:

- **Avatar, name, and description**: Mouse over the team name and click the edit (pencil) icon.
- **Banner**: Mouse over the banner and click the edit (pencil) icon.
- **Info tab sections**: Mouse over a section, such as Links, Members, or Notification Channels, and click its edit icon to update it in place.

Use the Settings (gear) menu in the team header for the following actions:

- **Configure Notifications**: Add or update the team's notification channels. Supported targets include Slack, Microsoft Teams, PagerDuty, email, and ServiceNow.
- **Edit Roles and Permissions**: Manage the roles and permissions associated with the team.
- **Edit Team Handle**: Change the team's handle.
- **Edit Connections**: Connect the team to external systems. Connect a **GitHub team** to associate the Datadog team with a GitHub team, or connect a **ServiceNow assignment group** to route incidents and change requests automatically.
- **Join Team** or **Leave Team**: Add yourself to or remove yourself from the team.

## Team membership{% #team-membership %}

### Team manager{% #team-manager %}

To differentiate members of your team, designate some of them as team managers. In the member list, a "TEAM MANAGER" badge appears next to team managers' names.

### Team modification permissions{% #team-modification-permissions %}

In the team's roles and permissions settings, specify which users can modify the team membership. The following options are available:

- Only users with the `user_access_manage` permission
- Team managers
- Team managers and members
- Anyone in the organization

The list is sorted in order of increasing permissiveness. Each option in the list includes the group in the entries above it. For example, selecting "team managers" means that both team managers and users with `user_access_manage` can modify membership.

The option that you select for which users can add and remove members determines whether you can add the team to access control lists. Two types of teams exist: invite only teams and open teams.

{% dl %}

{% dt %}
Invite only teams
{% /dt %}

{% dd %}
Teams with restricted membership. Can be set as access control recipients. Created when you restrict team membership modification to one of the first three options.
{% /dd %}

{% dt %}
Open teams
{% /dt %}

{% dd %}
Teams with unrestricted membership. Cannot be set as access control recipients. Created when you allow Anyone in the organization to modify team membership.
{% /dd %}

{% /dl %}

Users with the `user_access_manage` permission can set default rules on who can add or remove members, or edit team details. Set default rules with the Default Settings button on the team directory page. Override these policies for an individual team on the team details panel.

### Teams managed outside Datadog{% #teams-managed-outside-datadog %}

In some cases, a team's membership cannot be directly modified within Datadog by anyone (including a user with `user_access_manage`):

- If your org has selected SAML as the only team provisioning source, then the SAML team mappings control team membership. You cannot modify the team membership through Datadog.
- If a team is managed through an identity provider, then the identity provider controls team membership. You cannot modify the team membership through Datadog.

A team that is managed externally from an identity provider displays a **Managed** badge in its header.

## Team hierarchies{% #team-hierarchies %}

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="warning" %}
This feature is not supported for your selected Datadog site ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}

Build a Teams map to visualize team hierarchies, nesting teams within each other (subteams) to mirror your company's actual structure. The result is a more complete ownership model than a flat, disconnected list of teams. A team's related teams, parent teams, sister teams, and subteams appear on its team page, in the **Hierarchy** section of the **Info** tab. To explore the full map of all teams in your organization, see the [Teams map](https://app.datadoghq.com/software?selectedComponent=team) in the Datadog Internal Developer Portal.

{% image
   source="https://docs.dd-static.net/images/account_management/teams/github/manage/teams-map.9eca1f885823e8ab0459056cf799611d.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/account_management/teams/github/manage/teams-map.9eca1f885823e8ab0459056cf799611d.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Teams map showing a hierarchy of parent and child teams, with a selected team's details panel displaying its members and subteams" /%}

With hierarchies defined, you can:

- **Escalate issues**: When an issue needs to go beyond the owning team, hierarchy routes it up to the parent team for broader visibility and faster resolution, without manually tracking down who's next in the chain.
- **Roll-up filtering**: Select a parent team to see all data connected to any of its subteams, without selecting each one. Useful for director and VP-level views, where you care about an entire organization's footprint rather than one team's.
- **Simplify access control**: Grant access once at the parent team level to automatically apply consistent permissions to all subteams.

{% image
   source="https://docs.dd-static.net/images/account_management/teams/teams_filter_hierarchies2.aad8babe0fff9fef14c2da6c48085d3a.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/account_management/teams/teams_filter_hierarchies2.aad8babe0fff9fef14c2da6c48085d3a.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Team filter dropdown with a parent team expanded to show its subteams selected as checkboxes" /%}

### Set up team hierarchies{% #set-up-team-hierarchies %}

You can define hierarchical relationships between teams in four ways:

- **GitHub Teams**: If you used [GitHub](https://docs.datadoghq.com/account_management/teams/github.md) to set up your Datadog Teams and have GitHub team hierarchies configured, those team links sync to Datadog automatically during provisioning and appear in your Teams map.
- **Teams API**: See [Create a team hierarchy link](https://docs.datadoghq.com/api/latest/teams/create-a-team-hierarchy-link.md).
- **Terraform**: Use the [`datadog_team_hierarchy_links`](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/team_hierarchy_links) resource.
- **Datadog UI**: Define relationships directly on a team's page:
  1. On the [team directory page](https://app.datadoghq.com/organization-settings/teams), click the team you want to add a subteam or parent team relationship to.
  1. In the Info tab of the team page, click Edit in the Hierarchy section.
  1. Select the parent or child teams associated with the team, then click Save.

## Manage teams through an identity provider{% #manage-teams-through-an-identity-provider %}

When you set up a managed team, you configure the following properties of the team externally through an identity provider integration:

- Team name
- Team handle
- Team membership (synchronized from the corresponding identity provider group)

To keep managed teams consistent with their configuration in your identity provider, make changes to managed properties in the identity provider rather than through the Datadog site or API.

Datadog supports Okta and other SCIM-compliant identity providers for managed teams.

For more information on the capabilities of managed teams and how to set them up, see [SCIM](https://docs.datadoghq.com/account_management/scim.md).

## SAML attribute mapping{% #saml-attribute-mapping %}

To manage teams and team membership using SAML attributes, see [Map SAML attributes to Teams](https://docs.datadoghq.com/account_management/saml/mapping.md#map-saml-attributes-to-teams).

## Delegate team management{% #delegate-team-management %}

For an open membership model, configure your default team settings so Anyone in the organization can add or remove members. Assign the `teams_manage` permission to the appropriate roles to let anyone create teams or edit team details.

If you prefer a team-driven membership model, set your default team settings so Team Managers or Team Managers and Members can add or remove members. Assign the `teams_manage` permission to a role containing all of your team managers.

To enforce a strict membership model, configure your default team settings so Only users with user_access_manage can add or remove members. Assign the `teams_manage` permission only to organization administrators.