Add section on team hierarchy #31436
Conversation
Preview links (active after the
|
There was a problem hiding this comment.
Thank you! This doesn't really sell the utility of the feature at all, but maybe we're waiting for this to come out of preview phase for that? I might suggest we include something like this:
With Team Hierarchy, you can nest teams within each other to mimic your company's structure in Datadog, allowing for a more complete and accurate ownership model. Team Hierarchy also provides an enhanced filtering experience; select a larger team (like a director-level group) to find all the data connected to any of its subteams.
Not sure how well that fits into this flow, or if maybe it's more appropriate as an addition to a different section at a later time.
| Teams Hierarchy is in Preview. Fill out this form to request access. | ||
| {{< /callout >}} | ||
|
|
||
| With subteams, you can nest teams within each other to mimic your company's structure in Datadog, allowing for a more complete and accurate ownership model. Subteams also provide an enhanced filtering experience; select a larger team (like a director-level group) to find all the data connected to any of its subteams. |
There was a problem hiding this comment.
Since we're not using "team hierarchy," can we change from "your company's structure" back to your original use of "your company hierarchy" here? I think it's important for the word "hierarchy" to be in here a bit as my impression is that this is what customers call this feature (Tom has had multiple customer calls where they call it "hierarchy" before we do).
What does this PR do? What is the motivation?
New small section on nesting teams in each other 🙂
Merge instructions
Please don't merge until we get PM approval!
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes